Database is not Opening. Errors are coming due to Copy Mismatch of Log file

Question

Hello Friends,
I did some mistakes and deleted all log files after closing SAP QAS System.
I was trying to Resizing the Redo Log files, as per as SNOTE 309526.
All control files are consistent. Only due to Log File mismatch, Database is not Opening.
Here, is the error.
ERROR at line 1:
ORA-00322: log 14 of thread 1 is not current copy
ORA-00312: online log 14 thread 1: '/oracle/RQ1/mirrlogB/log_g14m2.dbf'
ORA-00322: log 14 of thread 1 is not current copy
ORA-00312: online log 14 thread 1: '/oracle/RQ1/origlogB/log_g14m1.dbf'
In working condition, Previously the file was with this name log_g11m1.dbf......
I had replaced all the files, which i had backedup ,before deleting those Log files. But, still this kind of error is coming.
I tried to "reset log", but it failed.
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
I did all the activities after Closing SAP System.
I want your Quick help, as its critical for me.
Regards
Bhavik Shroff
Edited by: Bhavik G. Shroff on Nov 8, 2008 3:49 PM

Answer 1

Hello Bhavik,
with your given information (the query from above and the posted ORA-errors) - unfortunately i have to say .. you are almost lost, i really advise you to get professional support on your system for that.  Let me explain why.
The information from the query
SQL> SELECT * FROM V$LOG;
GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM
    11          1      22292  104857600          2 NO  INVALIDATED      156909413     08-NOV-08
    13          1          0  104857600          2 YES UNUSED           0             08-NOV-08
    14          1      22291   20971520          2 YES ACTIVE           156909138     08-NOV-08
SQL> SELECT * FROM V$LOGFILE;
GROUP# STATUS  TYPE    MEMBER
11         ONLINE  /oracle/RQ1/origlogA/log_g11_m1.dbf
11         ONLINE  /oracle/RQ1/mirrlogA/log_g11_m2.dbf
13         ONLINE  /oracle/RQ1/origlogA/log_g13_m1.dbf
13         ONLINE  /oracle/RQ1/mirrlogA/log_g13_m2.dbf
14         ONLINE  /oracle/RQ1/origlogB/log_g14m1.dbf
14         ONLINE  /oracle/RQ1/mirrlogB/log_g14m2.dbf
and the ORA-00322 error:
ORA-00322: log 14 of thread 1 is not current copy
ORA-00312: online log 14 thread 1: '/oracle/RQ1/mirrlogB/log_g14m2.dbf'
ORA-00322: log 14 of thread 1 is not current copy
As you can see your online redo log group 14 has the status ACTIVE, that means that this online redolog files are needed for a crash recovery (not all needed data was already flushed to the data files), but the files from the online redo log group 14 are lost (deleted accidentally). But you have really luck that this online redologfile is already archived (see query ARC = YES) so you must have a archivelog file with the sequence number 22291.
The problem in your case is that the recover is performed through the online redolog files (normally done by a complete recovery), but the online redolog files are already deleted. To fix this issue you have to restore an older backup and make a recover trough the archive log files (including the sequence 22291 which was already archived) and not through the online redolog groups.
At this point this is the only way to get a running database again (but maybe with data lost).
The other serious problem is the redolog group 11, it seems like this group was the CURRENT redolog (take a look at the sequence and the SCNs) and you will lose this data.
I can imagine that the database was not shutdown clearly at the moment of the redolog file deletion - the most indications are pointing to this.
Sorry that i have no better news for you.. please get professional support who can execute the necessary steps for you.
Regards
Stefan