This content has been marked as final. Show 5 replies
Hmm the recovery process from loss of redo log vary on the status of the missing log file. I hope that you are simulating the loss of all the members of group otherwise you can just copy the available member to the missing location and no recovery is needed after that.
In your case first you need to check that what is the status of missing log group (active,inactive,current etc). Login to sqlplus mount the database and issue:
select group#,status from v$log;
Check the status of group2 bcz according to "ORA-00312: log online 2 thread 1" group 2 is missing.
I've rerun tested in the following situations:
- Simulate the lost of a non current (INACTIVE) redo log: in this case it was easy to recover from it. All i did was: alter database clear logfile <missing_logfile> and alter database open;
- Simulate the lost of a current redo log: According to Backup and Recovery Basics if the database was closed cleanly, all that's needed is to issue an alter database open resetlogs. Like i said, i did a clean shutdown, relocate the current logfile and tried to startup DB. However i can't issue an open resetlogs:
(Message after startup command)
ORA-00313: fallo de apertura para miembros del grupo log 2 del thread 1
ORA-00312: log online 2 thread 1:
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR en lÝnea 1:
ORA-01139: la opci¾n RESETLOGS s¾lo es vßlida despuÚs de una recuperaci¾n
incompleta de la base de datos
SQL> select group#,status from v$log;
(even tried to recover. get ora-00283).
SQL> recover database;
ORA-00283: sesi¾n de recuperaci¾n cancelada debido a errores
ORA-00264: no es necesaria la recuperaci¾n
Either this situation is not exactly as the Backup and Recovery Guide suggest or the only option is to do a point in time recovery.
Please provide feedback on this situation, and thanks very much for your backup.
Regards, Luis ...!