Oracle 10g rman restore how to#
Oracle 10g rman restore update#

RMAN> RESTORE SPFILE TO '/tmp/spfileTEMP.ora' FROM AUTOBACKUP If restoring to a nondefault location, then you could run commands as in the following example: If restoring to the default location, then run: When the SPFILE is not available, RMAN starts the instance with a dummy parameter file. Shut down the instance and restart it without mounting. See 'Determining your DBID' for details on determining your DBID. If the database is not up when the SPFILE is lost, and you are not using a recovery catalog, then you must set the DBID of the target database. If the database is up at the time of the loss of the SPFILE, connect to the target database. RMAN can also create a client-side initialization parameter file based on a backup of an SPFILE. This procedure assumes that you are not using a recovery catalog. Restoring the SPFILE is one situation in which a recovery catalog can simplify your recovery procedure, because you can avoid the step of having to record and remember your DBID. The default location is platform-specific (for example, ? /dbs/spfile.ora on Linux). When the instance is started with a client-side initialization parameter file, RMAN restores the SPFILE to the default SPFILE location if the TO clause is not used. If the instance is already started with the server parameter file, then you cannot overwrite the existing server parameter file. Note the following when restoring the SPFILE: Your instance may continue operating, although you will have to shut it down and restart it after restoring the SPFILE. Unlike the loss of the control file, the loss of your SPFILE does not cause your instance to immediately stop. If you lose your server parameter file (SPFILE), RMAN can restore it to its default location or to a location of your choice.

Oracle 10g rman restore update#

After restoring the control file to a new location, you can then update the CONTROL_FILES initialization parameter to include the new location.Д¦.4.2 Restoring the Server Parameter File (SPFILE) from Backup Any existing file named ' filename ' is overwritten. You can perform this operation with the database in NOMOUNT, MOUNT or OPEN states, because you are not overwriting any of the control files currently in use. RESTORE CONTROLFILE TO '/tmp/my_controlfile' You can also restore the control file to any location you choose other than the CONTROL_FILES locations, by using the form RESTORE CONTROLFILE TO ' filename ' : For example, if you are restoring your control file after a disk failure made some but not all CONTROL_FILES locations unusable, you can change CONTROL_FILES to replace references to the failed disk with pathnames pointing to another disk, and then run RESTORE CONTROLFILE with no arguments. One way to restore the control file to one or more new locations is to change the CONTROL_FILES initialization parameter, and then use the RESTORE CONTROLFILE command with no arguments to restore the control file to the default locations. If you are using tape backups, then after restoring the control file and mounting the database you must crosscheck the backups on tape, as shown in this example:Д¦.4.1.6 Restore of the Control File to a New Location Tape backups are not automatically crosschecked after the restore of a control file. This improves the usefulness of the restored control file in the restoration of the rest of your database. As a result the restored control file has a complete and accurate record of all backups in your flash recovery area and any other backups that were known to the control file at the time of the backup. However, if you are using a flash recovery area, RMAN updates a control file restored from backup, by performing an implicit crosscheck of all disk-based backups and image copies listed in the control file, and cataloging any backups in the flash recovery area that are not recorded in the restored control file.

The commands used for restoring your control file are the same, whether or not you are using a flash recovery area.

Oracle 10g rman restore how to#

See 'Determining your DBID' for details on how to determine your DBID.Д¦.4.1.3 Restore of the Control File When Using a Flash Recovery Area If one is found, RMAN restores the control file from that backup to all of the control file locations listed in the CONTROL_FILES initialization parameter.ДЇor information on how to determine the correct value for autobackup_format, see the description of CONFIGURE CONTROLFILE AUTOBACKUP FORMAT in the entry for CONFIGURE in Oracle Database Backup and Recovery Reference RMAN uses the autobackup format and DBID to determine where to hunt for the control file autobackup. You must first set the DBID for your database, and then use the RESTORE CONTROLFILE FROM AUTOBACKUP command:ДЇOR DEVICE TYPE DISK TO ' autobackup_format' If you want to restore the control file from autobackup, the database must be in a NOMOUNT state.

If you are not using a recovery catalog, you must restore your control file from an autobackup. 6.4.1.2 Restore of the Control File from Control File Autobackup