About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Troubleshooting
Problem
To restore the Oracle database there must be a control file, but if the control file does not exist is there a way to restore the control file from a Data Protection backup so that the Oracle database can be recovered.
Symptom
The Data Protection for Oracle is unable to restore the database because there is no control file available to complete the task.
Cause
There could be many reasons the control file is missing, the hard drive containing the file crashed, an administrator accidentally deleted the file or there was a disaster such as a fire or flood that destroyed the system.
Resolving The Problem
When the Oracle backup is performed the control file is included with one of the pieces that is backed up. This allows for several different scenarios to attempt to restore the control file. Since these scenarios can be quite complex, it is suggested that Oracle Support be contacted for assistance as a first step in the process.
1. The easiest means to restore the control file is when the RMAN Catalog exists and is viable for the restore. Look in the RMAN Catalog for the control file backup piece. Using the RMAN Catalog, Oracle support should be able to assist in restoring the control file.
2. If method one is not possible because there is no RMAN Catalog or it has been destroyed in addition to the control file not being available, then method two is the last resort, but not a guaranteed resolution.
Without an existing control file (and no RMAN catalog), there is no means to identify which backuppiece contains the control file.
If an autobackup of the control file was performed, then the restore of the control file can be accomplished by directly calling the autobackup process for the control file restore, for example:
RESTORE CONTROLFILE FROM AUTOBACKUP
If there is no RMAN catalog and the control file was not backed up using autobackup, then the trick is to try to locate the control file within the backuppieces from the last Oracle backup. Oracle technote ID 403883.1
How To Restore Controlfile From A Backupset Without A Catalog Or Autobackup
outlines how to proceed. The pieces needed to perform the restore, can be identified on the Tivoli Storage Manager server using the following select statement with the Tivoli Storage Manager Administrative client:
SELECT * FROM BACKUPS WHERE NODE_NAME='ORACLE_NODENAME'
The ORACLE_NODENAME must be uppercase and surrounded by single quotes.
There are additional details and considerations for this type of disaster recovery restore of the control file outlined in Oracle Technote 372996.1,
"RMAN Restore and Recover of a Database When the Repository and spfile/init.ora Files are Lost".
Using this technote, with the assistance of Oracle support, it should be possible to recreate the control file.
[{"Product":{"code":"SSTFZR","label":"Tivoli Storage Manager for Databases"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Data Protection for Oracle","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Product Synonym
TSM
Was this topic helpful?
Document Information
More support for:
Tivoli Storage Manager for Databases
Software version:
All Versions
Document number:
461225
Modified date:
17 June 2018
UID
swg21568847