Hi All ,
For some still unknown reason "prbbly some1 messing around" i am facing the following issue :
Stby alertlog is filled with the following message(s) :
Thu Oct 2 00:41:26 2014
Errors in file /usr/mvf/data/logs/oracle/udump/mvf_rfs_4024.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 10 thread 0: '/usr/mvf/data/dbase/redo/redo_stdby010.log'
Clearing online log 10 of thread 0 sequence number 0
Thu Oct 2 00:41:27 2014
Media Recovery Waiting for thread 1 sequence 235313 (in transit)
Thu Oct 2 00:41:27 2014
Errors in file /usr/mvf/data/logs/oracle/udump/mvf_rfs_4024.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 10 thread 0: '/usr/mvf/data/dbase/redo/redo_stdby010.log'
Thu Oct 2 00:41:29 2014
Clearing online log 10 of thread 0 sequence number 0
Thu Oct 2 00:41:29 2014
Errors in file /usr/mvf/data/logs/oracle/udump/mvf_rfs_4024.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 10 thread 0: '/usr/mvf/data/dbase/redo/redo_stdby010.log'
So when looking on the STBY i see following :
DB_UNIQUE_NAME DATABASE_ROLE Control Files
------------------------------ ---------------- ------------------------------------------------------------
MVF2 PHYSICAL STANDBY MVF
GROUP# THREAD# SEQUENCE# ARC Sta REDOLOG_FILE_NAME SIZE_MB
---------- ---------- ---------- --- --- -------------------------------------------------- ----------
1 1 235371 YES CLEARING CURRENT /usr/mvf/data/dbase/redo/redo07.log 50
2 1 235365 YES CLEARING /usr/mvf/data/dbase/redo/redo_stdby11.log 50
3 1 235366 YES CLEARING /usr/mvf/data/dbase/redo/redo_stdby12.log 50
4 1 235369 YES CLEARING /usr/mvf/data/dbase/redo/redo04.log 50
5 1 235370 YES CLEARING /usr/mvf/data/dbase/redo/redo05.log 50
6 1 235368 YES CLEARING /usr/mvf/data/dbase/redo/redo06.log 50
11 1 235367 YES CLEARING /usr/mvf/data/dbase/redo/redo_stdby13.log 50
As seen above all redo groups are "hung"on the clearing status and group /usr/mvf/data/dbase/redo/redo_stdby010.log does not even seem to exist physically.
[oracle@dg1somc:/usr/mvf/data/dbase/redo] $ lrt
total 1282824
-rwxrwxrwx 1 mvf dba 26214912 Oct 15 2010 redo03.log
-rwxrwxrwx 1 mvf dba 26214912 Oct 15 2010 redo01.log
-rwxrwxrwx 1 mvf dba 26214912 Oct 16 2010 redo02.log
-rwxrwxrwx 1 mvf dba 52429312 Oct 16 2010 redo04.log
-rwxrwxrwx 1 mvf dba 52429312 Oct 16 2010 redo05.log
-rwxrwxrwx 1 mvf dba 52429312 Oct 16 2010 redo06.log
-rw-r----- 1 oracle dba 52429312 May 2 2012 redo07.log
-rw-r----- 1 oracle dba 52429312 May 2 2012 redo_stdby11.log
-rw-r----- 1 oracle dba 52429312 May 2 2012 redo_stdby12.log
-rw-r----- 1 oracle dba 52429312 May 2 2012 redo_stdby13.log
-rwxrwxrwx 1 mvf dba 52429312 Jul 9 02:18 redo_stdby010.log
-rwxrwxrwx 1 mvf dba 52429312 Jul 9 12:22 redo_stdby09.log
-rwxrwxrwx 1 mvf dba 52429312 Oct 2 03:45 redo_stdby08.log
-rwxrwxrwx 1 mvf dba 52429312 Oct 2 03:50 redo_stdby07.log
[oracle@dg1somc:/usr/mvf/data/dbase/redo] $
Would it be enough to issue a drop redo group command ? or should i go ahead and add the group which it seems to look for.
==========================================================================================================================================================
Status on the Primary :
DB_UNIQUE_NAME DATABASE_ROLE NAME
------------------------------ ---------------- ---------
MVF1 PRIMARY MVF
GROUP# THREAD# SEQUENCE# ARC STATUS REDOLOG_FILE_NAME SIZE_MB
---------- ---------- ---------- --- ---------------- -------------------------------------------------- ----------
1 1 235364 YES INACTIVE /usr/mvf/data/dbase/redo/redo07.log 50
2 1 235365 YES INACTIVE /usr/mvf/data/dbase/redo/redo_stdby11.log 50
3 1 235366 YES INACTIVE /usr/mvf/data/dbase/redo/redo_stdby12.log 50
4 1 235369 YES INACTIVE /usr/mvf/data/dbase/redo/redo04.log 50
5 1 235370 NO CURRENT /usr/mvf/data/dbase/redo/redo05.log 50
6 1 235368 YES INACTIVE /usr/mvf/data/dbase/redo/redo06.log 50
11 1 235367 YES INACTIVE /usr/mvf/data/dbase/redo/redo_stdby13.log 50
[oracle@os1somc:/usr/mvf/data/dbase/redo] $ lrt
total 1190472
-rw-r----- 1 oracle dba 10486272 Jun 22 2005 redo03.log
-rw-r----- 1 oracle dba 10486272 Jun 22 2005 redo01.log
-rw-r----- 1 oracle dba 10486272 Jun 22 2005 redo02.log
-rw-r----- 1 oracle dba 52429312 Aug 21 11:46 redo_stdby07.log
-rw-r----- 1 oracle dba 52429312 Aug 21 11:46 redo_stdby08.log
-rw-r----- 1 oracle dba 52429312 Aug 21 11:46 redo_stdby09.log
-rw-r----- 1 oracle dba 52429312 Aug 21 11:46 redo_stdby010.log
-rw-r----- 1 oracle dba 52429312 Oct 2 02:19 redo_stdby11.log
-rw-r----- 1 oracle dba 52429312 Oct 2 02:21 redo_stdby12.log
-rw-r----- 1 oracle dba 52429312 Oct 2 02:23 redo_stdby13.log
-rw-r----- 1 oracle dba 52429312 Oct 2 02:46 redo06.log
-rw-r----- 1 oracle dba 52429312 Oct 2 03:13 redo04.log
-rw-r----- 1 oracle dba 52429312 Oct 2 03:45 redo05.log
-rw-r----- 1 oracle dba 52429312 Oct 2 03:50 redo07.log
[oracle@os1somc:/usr/mvf/data/dbase/redo] $
Any idea on how to fix this issue once and for all anyone ?
thanks for all the input in advance !