###################################################RESTORE CONTROLFILE FROM LATEST INCREMENTAL LEVEL BACKUP###################################################This step very important.

RMAN replicates the control file to all CONTROL_FILES locations automatically.

Example 20-3 Restoring a Database on a New Host. If you are performing a trial restore of the production database, then perform either of the following actions before restoring the database in the test environment: If the test database uses a fast recovery area that is physically different from the recovery area used by the production database, then set DB_RECOVERY_FILE_DEST in the test database instance to the new location. For example, run SET DBID to set the DBID, then run STARTUP NOMOUNT: RMAN fails to find the server parameter file, which has not yet been restored, but starts the instance with a "dummy" file. Make the source database initialization parameter file accessible on the new host. It will recover database upto level of incremental level 1 backup. The option OPEN RESETLOGS is always required after recovery with a backup control file, regardless of whether logs are available. The file name that you specify should be on a file system accessible from the host where the RMAN client is running. RMAN uses the autobackup format and DBID to determine where to hunt for the control file autobackup. If one is found, RMAN restores the control file to all control file locations listed in the CONTROL_FILES initialization parameter. The command file should do the following: Restore a control file autobackup (see "Performing Recovery with a Backup Control File and No Recovery Catalog").

restore controlfile from d:\oracle\backupHOQJ2VQ_1_1; 2> allocate channel c1 device type disk format D:\oracle\backup\%U; 3> backup incremental level 1 as compressed backupset database plus archivelog; restore controlfile from D:\oracle\backupROQJ719_1_1; Create a free website or blog at WordPress.com. The commands for restoring a control file are the same whether or not the database uses a fast recovery area. Example 20-2 Setting the DBID and Restoring the Control File from Autobackup. The RMAN metadata missing from the backup control file is available from the recovery catalog. Note the following considerations: If restoring from tape, then use ALLOCATE CHANNEL to allocate an SBT channel manually. RMAN uses the autobackup format and DBID to hunt for control file autobackups. connected to target database (not started)Oracle instance started. To learn how to determine the correct value for autobackup_format, see the description of CONFIGURE CONTROLFILE AUTOBACKUP FORMAT in the entry for the CONFIGURE command in Oracle Database Backup and Recovery Reference. Take incremental level 0 backup on source server. The default location is platform-specific, for example, ?/dbs/spfile.ora on Linux. This procedure assumes that you are not using a recovery catalog. This step depends on whether the online redo logs are available. When the server parameter file is not available, RMAN starts the instance with a dummy parameter file. The description of CONFIGURE CONTROLFILE AUTOBACKUP FORMAT in the entry for CONFIGURE in Oracle Database Backup and Recovery Reference to learn how to determine the correct value for the autobackup format. The following RMAN command creates an initialization parameter file named /tmp/initTEMP.ora on the system running the RMAN client: To restart the instance with the initialization parameter file, use the following command, again running RMAN on the same client host: This section explains what to do when all current control files are lost and you must restore a backup control file. Allocate a channel to the media manager and then restore the server parameter file from autobackup. The target database is located in /net/hosta/dev3/oracle/dbs, but you want to restore the database to /net/hostb/oracle/oradata/test. Execute the script created in the previous step. Example 20-1 sets the DBID and restores the server parameter file from a control file autobackup in a nondefault location. If volume names have changed, then run SET NEWNAME commands before the restore operation and perform a switch after the restore operation to update the control file with the new locations for the data files, as shown in the following example. This procedure uses the RESTORE and RECOVER commands. In the following example, the online redo log files have been lost, and the most recent archived redo log sequence number is 13243. RMAN displays the DBID whenever you connect to a target database. Appreciate you Farhat. All rights reserved. The main differences are: Only consistent backups can be used in restoring a database in NOARCHIVELOG mode. If you have set ORACLE_SID and ORACLE_HOME, then you can use operating system authentication to connect as SYSDBA. Run recovery process. It will skip files already restored. In this scenario, you have two networked Linux hosts, hosta and hostb.

For example, enter the following command: Execute a RUN command to restore the server parameter file. Sample output follows: Restore and edit the server parameter file. document.getElementById( "ak_js_1" ).setAttribute( "value", ( new Date() ).getTime() ); RESTORING INCREMENTAL RMAN BACKUP TO SAVE RESTORETIME. Unlike the loss of the control file, the loss of the server parameter file does not cause the instance to immediately stop. It will apply changes from Incremental level 1 backup. Run a LIST command to see a listing of backups of the data file and control file autobackups. If you know that RMAN never produces more than n autobackups each day, then you can set the RESTORE SPFILE FROM AUTOBACKUP MAXSEQ parameter to n to reduce the search time. If you changed the archiving destination or format during recovery, or if you added new online log members after the backup of the control file, then RMAN may not be able to automatically catalog a needed online or archived log. Start the target database instance without mounting the database. Any existing file named 'filename' is overwritten. If you are not using a recovery catalog, then you must restore your control file from an autobackup. Likewise, the control file of the trgta database is completely unaffected by the test. If you do not set the CONTROL_FILES initialization parameter, then the database uses the same rules to determine the destination for the restored control file that it uses when creating a control file if the CONTROL_FILES parameter is not set. Restore the control file from an autobackup and then mount the database. This article explains a method which can be used to restore oracle incremental level backup to restore rman backups on new server. You can also restore the server parameter file as a client-side initialization parameter file with the TO PFILE 'filename' clause. Otherwise, RMAN records metadata about the restored data files in the recovery catalog. If possible, restore or re-create all relevant network files such as tnsnames.ora and listener.ora and a password file. This chapter contains the following topics: Recovering a NOARCHIVELOG Database with Incremental Backups, Performing Recovery with a Backup Control File. Restore the data files to their original locations. For example, run: Write an RMAN command file to restore the autobackup control file and perform recovery. RMAN restores the control file to whatever locations you specified in the CONTROL_FILES initialization parameter. To recover the database with a control file autobackup in NOCATALOG mode: Start RMAN and connect to a target database. To move the database to a new host by using data file copies or backup sets on disk, you must transfer the files manually to the new host. As a result, the restored control file has a complete and accurate record of all backups in the recovery area and any other backups known to the control file at the time of the backup. It will just restore newly added datafile. When you perform DBPITR with a backup control file, before opening the database with RESETLOGS, you can open the database read-only using SQL*Plus and run queries as needed to verify that the effects of the logical corruption have been reversed. MAXSEQ is set to 255 by default, and RESTORE counts backward from MAXSEQ to find the last backup of the day. Copyright (c) 1982, 2011, Oracle. This scenario assumes that you want to test whether you can restore your database to a new host. Its backup information will be used while recovering database upto level of incremental level 1. After restoring the control file to a new location, you can then update the CONTROL_FILES initialization parameter to include the new location. Example 20-3 shows the RMAN script reco_test.rman that can perform the restore and recovery operation. Great and V Good explanation. For example: Set the database identifier for the target database with the SET DBID command. The scenarios in this chapter are less common or are more complicated than the basic scenarios. When preparing your disaster recovery strategy, ensure that the backups of the data files, control files, and server parameter file are restorable on hostb. Write a command file to perform the restore and recovery operation, and then execute the command file. Depending on the situation, you may need to execute multiple commands in the RUN command. Copy the file from the old host to a new host by using an operating system utility.

RMAN> restore controlfile from D:\oracle\backupROQJ719_1_1; Starting restore at 03-DEC-13allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=128 device type=DISK, Starting restore at 03-DEC-13Starting implicit crosscheck backup at 03-DEC-13allocated channel: ORA_DISK_1channel ORA_DISK_1: SID=128 device type=DISKCrosschecked 12 objectsFinished implicit crosscheck backup at 03-DEC-13, skipping datafile 1; already restored to file D:\ORACLE\ORADATA\SYSTEM01.DBFskipping datafile 2; already restored to file D:\ORACLE\ORADATA\SYSAUX01.DBFskipping datafile 3; already restored to file D:\ORACLE\ORADATA\UNDOTBS01.DBFskipping datafile 4; already restored to file D:\ORACLE\ORADATA\USERS01.DBFskipping datafile 5; already restored to file D:\ORACLE\ORADATA\SDE.DBFskipping datafile 6; already restored to file D:\ORACLE\ORADATA\FLASHBACK.DBFchannel ORA_DISK_1: starting datafile backup set restorechannel ORA_DISK_1: specifying datafile(s) to restore from backup setchannel ORA_DISK_1: restoring datafile 00007 to D:\ORACLE\ORADATA\INCTEST.DBFchannel ORA_DISK_1: reading from backup piece D:\ORACLE\BACKUPQOQJ6U8_1_1channel ORA_DISK_1: piece handle=D:\ORACLE\BACKUPQOQJ6U8_1_1 tag=TAG20131203T121048channel ORA_DISK_1: restored backup piece 1channel ORA_DISK_1: restore complete, elapsed time: 00:00:15Finished restore at 03-DEC-13, Starting recover at 03-DEC-13using channel ORA_DISK_1channel ORA_DISK_1: starting incremental datafile backup set restorechannel ORA_DISK_1: specifying datafile(s) to restore from backup setdestination for restore of datafile 00001: D:\ORACLE\ORADATA\SYSTEM01.DBFdestination for restore of datafile 00002: D:\ORACLE\ORADATA\SYSAUX01.DBFdestination for restore of datafile 00003: D:\ORACLE\ORADATA\UNDOTBS01.DBFdestination for restore of datafile 00004: D:\ORACLE\ORADATA\USERS01.DBFdestination for restore of datafile 00005: D:\ORACLE\ORADATA\SDE.DBFdestination for restore of datafile 00006: D:\ORACLE\ORADATA\FLASHBACK.DBFchannel ORA_DISK_1: reading from backup piece D:\ORACLE\BACKUPKOQJ5TC_1_1channel ORA_DISK_1: piece handle=D:\ORACLE\BACKUPKOQJ5TC_1_1 tag=TAG20131203T115315channel ORA_DISK_1: restored backup piece 1channel ORA_DISK_1: restore complete, elapsed time: 00:00:01channel ORA_DISK_1: starting incremental datafile backup set restorechannel ORA_DISK_1: specifying datafile(s) to restore from backup setdestination for restore of datafile 00001: D:\ORACLE\ORADATA\SYSTEM01.DBFdestination for restore of datafile 00002: D:\ORACLE\ORADATA\SYSAUX01.DBFdestination for restore of datafile 00003: D:\ORACLE\ORADATA\UNDOTBS01.DBFdestination for restore of datafile 00004: D:\ORACLE\ORADATA\USERS01.DBFdestination for restore of datafile 00005: D:\ORACLE\ORADATA\SDE.DBFdestination for restore of datafile 00006: D:\ORACLE\ORADATA\FLASHBACK.DBFchannel ORA_DISK_1: reading from backup piece D:\ORACLE\BACKUPQOQJ6U8_1_1channel ORA_DISK_1: piece handle=D:\ORACLE\BACKUPQOQJ6U8_1_1 tag=TAG20131203T121048channel ORA_DISK_1: restored backup piece 1channel ORA_DISK_1: restore complete, elapsed time: 00:00:01, unable to find archived logarchived log thread=1 sequence=9RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03002: failure of recover command at 12/03/2013 12:22:49RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 9 and starting SCN of 3165567379. See "Determining the DBID of the Database" for details on determining the DBID. If you are using tape backups, then you can restore and mount the control file, and optionally crosscheck the backups on tape, as shown in the following example: This section assumes that you have RMAN backups of the control file, but do not use a recovery catalog. If recovery was successful, then open the database and reset the online logs: Disaster recovery includes the restoration and recovery of the target database after the loss of the entire target database, the recovery catalog database, all current control files, all online redo log files, and all parameter files. For example, start RMAN as follows: Specify the DBID for the target database with the SET DBID command, as described in "Restoring the Server Parameter File". You do not use a recovery catalog with the database. The instance may continue operating, although you must shut it down and restart it after restoring the server parameter file. You can restore the autobackup to the default or a new location. Otherwise, RMAN returns an error. For example, create a file /tmp/init.ora which contains the single line: You can use the following RMAN command to restart the instance with the restored server parameter file: If you have configured control file autobackups, then the server parameter file is backed up with the control file whenever an autobackup is taken. You can query V$ views to obtain this information. Perform a complete restore and recovery as described in "Performing Complete Database Recovery". To terminate the restore operation if you do not find the autobackup in the current day (or specified day), set MAXDAYS 1 on the RESTORE command. Change), You are commenting using your Facebook account. If the autobackup is in a nondefault format, then first use the SET CONTROLFILE AUTOBACKUP FORMAT command to specify the format. After logging in to hostb with administrator privileges, edit the /etc/group file so that you are included in the DBA group: Set the ORACLE_SID environment variable on hostb to the same value used on hosta: Start RMAN on hostb and connect to the target database without connecting to the recovery catalog. Because no recovery catalog is available, you cannot use preconfigured channels. We will delete old controlfile from oradata folder and restore controlfile included in level 1 backup. RMAN catalogs any backups in the recovery area that are not recorded. You can perform limited recovery of changes to a database running in NOARCHIVELOG mode by applying incremental backups. Restore database. Perform a SET UNTIL operation to limit recovery to the end of the archived redo logs.

Ensure that backups used for the restore operation are accessible on the restore host. Afterward, use the copied recovery catalog for the test restore. It also assumes that you enabled the control file autobackup feature for the target database and can restore an autobackup of the control file. RMAN attempts to find a valid archived redo log in any current archiving destination with the current log format. If the file systems on the destination system are set up to have the same paths as the source host, then do not use SET NEWNAME for those files restored to the same path as on the source host. See "Determining the DBID of the Database" to learn how to determine your DBID. You have one tape drive containing backups of all the data files and archived redo logs through log 1124, and autobackups of the control file and server parameter file. Then, restart the instance with the client-side initialization parameter file. If you do not know the DBID for your database, then see "Determining the DBID of the Database" to learn how to determine the DBID. If you use the procedure in this section, then the DBID for the restored database equals the DBID for the original database. Fill in your details below or click an icon to log in: You are commenting using your WordPress.com account. To restore the control file from autobackup, the database must be in a NOMOUNT state. This scenario assumes that you want to start the RMAN client on hostb and authenticate yourself through the operating system. You can also obtain it by inspecting saved RMAN log files, querying the catalog, or looking at the file names of control file autobackup. You have tape backups of data files, control files, archived redo logs, and the server parameter file on a media manager accessible by both hosts. Change), You are commenting using your Twitter account. Catalog the data file copies that you copied in "Restoring Disk Backups to a New Host", using their new file names or CATALOG START WITH (if you know all the files are in directories with a common prefix easily addressed with a CATALOG START WITH command). If you know that a different control file autobackup format was in effect when the control file autobackup was created, then specify a nondefault format for the restore of the control file. If you know that the control file contained information about configured channels that are useful in the rest of the restore process, then you can exit RMAN to clear manually allocated channels from Step c. If you restart the RMAN client and mount the database, then these configured channels are available for your use. Shut down the database instance and restart it without mounting the database. If the test database uses a fast recovery area that is physically the same as the recovery area used by the production database, then set DB_UNIQUE_NAME in the test database instance to a different name from the production database. Start RMAN and connect to the target database instance. To recover a NOARCHIVELOG database with incremental backups: After connecting to the target database and the recovery catalog, place the database in a mounted state: For example, you can perform incomplete recovery with the following commands: Open the database with the RESETLOGS option. ############################################################RESTORE INCREMENTAL LEVEL 1 BACKUP ON DESTINATION SERVER############################################################Copy newly taken level 1 backup to destination server.Start database in nomount state. Enter a command such as the following to copy all data file copies to the ?/oradata/trgt directory on the new host: Enter a command such as the following to copy the autobackup backup piece to the /tmp directory on the new host: As explained in "Restoring the Server Parameter File from a Control File Autobackup", you must use the SET CONTROLFILE AUTOBACKUP FORMAT command when restoring an autobackup from a nondefault location.

The script must include the following steps: For each data file on the destination host that is restored to a different path than it had on the source host, use a SET NEWNAME command to specify the new path on the destination host.

During recovery, RMAN automatically searches for online and archived logs that are not recorded in the RMAN repository and catalogs any that it finds. For example, if the backups were made with a media manager, then verify that the tape device is connected to the new host. You must then run the RECOVER command, even if no data files have been restored, and open the database with the RESETLOGS option. The following example deletes the database files: Because you did not perform the restore and recovery operation when connected to the recovery catalog, the recovery catalog contains no records for any of the restored files or the procedures performed during the test. Media recovery is not possible because no archived redo logs exist. A target database named trgta is on hosta and is registered in recovery catalog catdb. RMAN does not automatically crosscheck tape backups after restoring a control file. If you must use a recovery catalog because the control file is not large enough to contain the RMAN repository data on all of the backups that you must restore, then use Oracle Data Pump to export the catalog and import it into a different schema or database.

Take another incremental level 1 backup on source DB.

When the server parameter file is not available, RMAN attempts to start the instance with a dummy server parameter file. For example, edit the following parameters: Restart the instance with the edited initialization parameter file. connected to target database: TEST (DBID=2114642825), RMAN> run {2> allocate channel c1 device type disk format D:\oracle\backup\%U;3> backup incremental level 0 as compressed backupset database plus archivelog;4> }, using target database control file instead of recovery catalogallocated channel: c1channel c1: SID=130 device type=DISK, Starting backup at 03-DEC-13current log archivedchannel c1: starting compressed archived log backup setchannel c1: specifying archived log(s) in backup setinput archived log thread=1 sequence=254 RECID=178 STAMP=833188289input archived log thread=1 sequence=255 RECID=179 STAMP=833188289channel c1: starting piece 1 at 03-DEC-13channel c1: finished piece 1 at 03-DEC-13piece handle=D:\ORACLE\BACKUPEOQJ2TM_1_1 tag=TAG20131203T110213 comment=NONEchannel c1: backup set complete, elapsed time: 00:00:07channel c1: starting compressed archived log backup setchannel c1: specifying archived log(s) in backup setinput archived log thread=1 sequence=3 RECID=188 STAMP=833194933channel c1: starting piece 1 at 03-DEC-13channel c1: finished piece 1 at 03-DEC-13piece handle=D:\ORACLE\BACKUPFOQJ2TT_1_1 tag=TAG20131203T110213 comment=NONEchannel c1: backup set complete, elapsed time: 00:00:04Finished backup at 03-DEC-13, Starting backup at 03-DEC-13channel c1: starting compressed incremental level 0 datafile backup setchannel c1: specifying datafile(s) in backup setinput datafile file number=00003 name=D:\ORACLE\ORADATA\UNDOTBS01.DBFinput datafile file number=00006 name=D:\ORACLE\ORADATA\FLASHBACK.DBFinput datafile file number=00002 name=D:\ORACLE\ORADATA\SYSAUX01.DBFinput datafile file number=00001 name=D:\ORACLE\ORADATA\SYSTEM01.DBFinput datafile file number=00005 name=D:\ORACLE\ORADATA\SDE.DBFinput datafile file number=00004 name=D:\ORACLE\ORADATA\USERS01.DBFchannel c1: starting piece 1 at 03-DEC-13channel c1: finished piece 1 at 03-DEC-13piece handle=D:\ORACLE\BACKUPGOQJ2U1_1_1 tag=TAG20131203T110225 comment=NONEchannel c1: backup set complete, elapsed time: 00:00:55channel c1: starting compressed incremental level 0 datafile backup setchannel c1: specifying datafile(s) in backup setincluding current control file in backup setincluding current SPFILE in backup setchannel c1: starting piece 1 at 03-DEC-13channel c1: finished piece 1 at 03-DEC-13piece handle=D:\ORACLE\BACKUPHOQJ2VQ_1_1 tag=TAG20131203T110225 comment=NONEchannel c1: backup set complete, elapsed time: 00:00:01Finished backup at 03-DEC-13, Starting backup at 03-DEC-13current log archivedchannel c1: starting compressed archived log backup setchannel c1: specifying archived log(s) in backup setinput archived log thread=1 sequence=4 RECID=189 STAMP=833195007channel c1: starting piece 1 at 03-DEC-13channel c1: finished piece 1 at 03-DEC-13piece handle=D:\ORACLE\BACKUPIOQJ2VV_1_1 tag=TAG20131203T110327 comment=NONEchannel c1: backup set complete, elapsed time: 00:00:01Finished backup at 03-DEC-13released channel: c1#######################################################RESTORE INCREMENTAL LEVEL 0 BACKUP ON DESTINATION SERVER#######################################################, Recovery Manager: Release 11.2.0.3.0 Production on Tue Dec 3 12:10:49 2013, connected to target database (not started), Total System Global Area 730714112 bytes, Fixed Size 2258792 bytesVariable Size 411043992 bytesDatabase Buffers 310378496 bytesRedo Buffers 7032832 bytes.