Topics | How To | Full System Restore | Troubleshoot | Related Topics
Troubleshooting CommCell Console Errors
Troubleshooting Point-In-Time Recoveries
UDE-00008: operation generated ORACLE error 31623
ORA-31623: a job is not attached to this session via the specified handle
In such cases, set the sNODATAPUMPEXPORT registry key to Y on the client and re-submit the job.
Once you have identified the specific RMAN error, consult one of the following publications from Oracle Corporation for information on resolving the specific error, in conjunction with your on-site Oracle database administrator:
Oracle8i - Backup and Recovery Guide
Oracle8i - Recovery Manager User’s Guide and Reference
Oracle9i - Recovery Manager User’s Guide
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.1.0\db_1)
(PROGRAM = extproc)
)
(SID_DESC =
(SID_NAME = rman10g)
(ORACLE_HOME = C:\oracle\product\10.1.0\db_1)
(SID = rman10g)
)
)
DB_FILE_NAME_CONVERT='<primary_database_temp_datafile_old_location>','<standby_database_temp_datafile_new_location>'
If this parameter is not set, restore will fail with the following error message:
temporary file TEMP01.DBF conflicts with file used by target database
Comment out the option "db_recovery_file_dest" from the PFile, then re-create the SPFile using the new PFile. Afterwards, restoring the SPFile from the CommCell Console should work.
Restore the SPFile manually using RMAN with the script below:
RMAN> run {
2> ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
3> restore spfile from autobackup;
4> }
Caution on the Use of RESETLOGS
Sample Script for Resetting a Database After RESETLOGS
Sample Script for Resetting the Database to an Old Incarnation
Caution should be used when recovering an Oracle database to a point-in-time using the Point In Time option in the Recover tab of the Oracle Advanced Restore Options dialog box. The reasoning is that this action executes a powerful RMAN statement called "ALTER DATABASE OPEN RESETLOGS" which will reset the SCN (System Change Number) and time stamp on every object of the database (i.e., datafiles and control files).
Archived redo logs have these two values (SCN and time stamp) in their headers, and Oracle will not apply an archived redo log to a datafile unless the RESETLOGS SCN and time stamps match, to prevent you from corrupting your datafiles with old archived logs.
Execution of the "ALTER DATABASE OPEN RESETLOGS" statement has the effect of recovering the database to a time that is not current, hence being reset with old data (i.e., an old incarnation). This is a very useful operation if the point-in-time to which you are trying to recover is certain and known, but can be counterproductive if you are guessing at the point-in-time.
If the point-in-time is in question, it is recommended that you select the Restore Data option in the Advanced Restore Options (Restore) tab and/or the Restore Control File option in the Advanced Restore Options (Ctrl & SP Files) tab instead of the Point In Time option in the Recover tab. These options can either be used separately or together, depending on the situation (if used together with point-in-time, both must use the same point-in-time). This method will allow you to restore the database to a state that you can make the determination whether or not you have achieved the correct point-in-time, without invoking the "ALTER DATABASE OPEN RESETLOGS" statement that would reset SCNs and time stamps on the database objects.
After determining the correct point-in-time through this method, the Point In Time option in the Recover tab can be safely applied to reset your Oracle database to the desired incarnation.
Sample scripts are provided below for your Oracle database administrator to use as reference for developing custom scripts that you can run from the RMAN command line, to perform special operations apart from the CommCell Console.
The following example resets a database after performing an incomplete media recovery:
run {
allocate channel dev1 type disk;
set until logseq 1234 thread 1;
restore database skip tablespace readonly;
recover database;
sql "ALTER DATABASE OPEN RESETLOGS";
release channel dev1;
}
reset database;
The following command makes an old incarnation of database PROD1 current again:
# obtain primary key of old incarnation
list incarnation of database prod1;
List of Database Incarnations
DB Key
------Inc Key
-------DB Name
-------DB ID
-----CUR
---Reset SCN
---------Reset Time
----------
1
2
PROD1
1224038686
NO
1
02-JUL-98
1
582
PROD1
1224038686
YES
59727
10-JUL-98
shutdown immediate;
# reset database to old incarnation
reset database to incarnation 2;
# recover it
run {
allocate channel dev1 type disk;
restore controlfile;
startup mount;
restore database;
recover database;
sql "ALTER DATABASE OPEN RESETLOGS";
release channel dev1;
}