I got ” ORA-00322: log string of thread string is not current copy. ” error in Oracle database.
ORA-00322: log string of thread string is not current copy
Details of error are as follows.
ORA-00322: log string of thread string is not current copy. Cause: Check of log file header at database open found that an online log appears to be an incorrectly restored backup. Action: Restore correct file or reset logs
log string of thread string is not current copy
This ORA-00322 is related with the Check of log file header at database open found that an online log appears to be an incorrectly restored backup.
Restore correct file or reset logs.
When attempting to start an Oracle XE database where P6 is located, P6 cannot connect to the database and the database alias configuration alias fails with:
ORA-12514 TNS:listener does not currently know of service requested in connect
Looking in the Oracle alert_<sid>.log file, the following errors are generated:
ORA-00322: log 2 of thread 1 is not current copy ORA-00312: online log 2 of thread 1 is: 'x'
– x is the location and name of the online redo log in question
This issue is caused due to a corrupted online redo log that would not allow the database to open.
When an Oracle database is started, one of the startup checks is that all of the critical files for the database are online and are consistent. If there’s a corrupted online redo log file, this file will not be consistent with the rest of the database and cause these errors at startup.
To resolve this issue, follow one of the two following steps:
1 – If you have a current/recent backup of the Oracle database, restore the database to a point in time prior to the redo log being corrupted. You can check the alert_<sid>.log file for the first occurrence of the ORA-322 and ORA-312 errors to give you a time frame that you need to restore to.
Consult your DBA that backed up your database to have them restore the database to that point in time. By default, Oracle databases are not set up to backup. If you do not have the option of restoring the database, then follow option 2:
2 – Clear the corrupted online redo log from the database.
– Find the earliest occurrence of the following errors in the alert_<sid>.log
ORA-00322: log 2 of thread 1 is not current copy ORA-00312: online log 2 of thread 1 is: 'x' - 'x' is the location and name of the corrupted redo log
– Go to a command prompt and type the following:
- sqlplus / as sysdba - startup mount; - alter database clear logfile 'x'; - replace 'x' with the information from the ORA-312 error above. For example: alter database clear logfile 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORASID\redo02.log'; - alter database open;
At this point the database should open and you can connect to it via the P6 client.
161 views last month, 3 views today