RMAN configuration parameters for database with db_unique_name DUMMY are:ĬONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F' # defaultīelow we will set the location for the control file autobackup and restore the SPFILE to a PFILE and then we shutdown the database.
RMAN> show controlfile autobackup format All of the RMAN configuration parameters values are at their defaults so we will need to set the location for the control file autobackup. The SPFILE is stored in the control file autobackup. We are going to need to make some changes to the SPFILE so we will restore SPFILE to a PFILE. Now with the database in mount mode we need to restore the SPFILE. Starting Oracle instance without parameter file for retrieval of spfile LRM-00109: could not open parameter file '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/initorcl.ora' Startup failed: ORA-01078: failure in processing system parameters Oracle will use a “dummy” parameter file for the time being.
This is to be expected as we are restoring to a new host. When we bring the database up in mount mode we will receive errors because the parameter file is not found. We now need to set the DBID and bring the database in mount mode. Recovery Manager: Release 11.2.0.1.0 - Production on Tue Apr 27 11:27:23 2010Ĭonnected to target database (not started) Set the ORACLE_SID to the SID of the database that made the backup and start up RMAN and connect to the backup]$ export backup]$ rman Uploading 22lc5nqv_1_1 to /u01/app/oracle/oradata/orcl/backup/22lc5nqv_1_1 Uploading 21lc5nqv_1_1 to /u01/app/oracle/oradata/orcl/backup/21lc5nqv_1_1 Uploading 20lc5nqr_1_1 to /u01/app/oracle/oradata/orcl/backup/20lc5nqr_1_1 Uploading 1vlc5nqn_1_1 to /u01/app/oracle/oradata/orcl/backup/1vlc5nqn_1_1 Sftp> cd /u01/app/oracle/oradata/orcl/backup If the backups are on local storage we will need to transfer the backups to the new backup]$ sftp to password: If the backups reside on a shared file system that the new host has access to then there is nothing more to do. Next we need to make the backup available to the new host. Looking through the output above we see that highest Next SCN is 1375117 which is part of backup set 60.
Piece Name: /u03/app/oracle/oradata/orcl/backup/24lc5o0c_1_1 Piece Name: /u03/app/oracle/oradata/orcl/backup/20lc5nqr_1_1īP Key: 60 Status: AVAILABLE Compressed: NO Tag: TAG20100427T094652 Thrd Seq Low SCN Low Time Next SCN Next TimeīP Key: 55 Status: AVAILABLE Compressed: NO Tag: TAG20100427T094350 Piece Name: /u03/app/oracle/oradata/orcl/backup/1vlc5nqn_1_1
#Cutlist for sketchup 2015 archive
We can also find the last SCN in our archive logs through RMAN using LIST BACKUP OF ARCHIVELOG ALL.īS Key Size Device Type Elapsed Time Completion TimeīP Key: 54 Status: AVAILABLE Compressed: NO Tag: TAG20100427T094350 Here we see that the archive logs contain log information up to SCN 1375117. We can find the last SCN by querying V$ARCHIVED_LOG.
When we restore the database we are not going to have the active redo logs from the original database so we want to stop the recovery at the last SCN in the archive logs. The first group of numbers appearing after the c-, 123915029, is the DBID. If you are unable to connect to the database you can also find the DBID by inspecting the file name of the control file autobackup. All rights reserved.Ĭonnected to target database: ORCL (DBID=1239150297) You can find the DBID by connecting to the database with RMAN as shown ~]$ rman One of the first things we want to do is get the Database ID ( DBID) from the database in which we will be restoring its backup. For this demonstration we will be using Oracle Database 11gR2 on Linux and disk based backup. This document will detail the steps to restore a database on a new host using RMAN.