Error:
ORA-00313 open failed for members of log group of thread
Recovery is unrecoverable because 1 other slaves require space
found in data guard setup , ORA-00313 errors cause MRP process to apply the redo logs slowly on standby impacting the real time sync.
Solution:
for , Recovery is unrecoverable because 1 other slaves require space , consider increasing RAM on operating system so that SGA can be increased by at least 1 or 2 GB .
So that slave requires space should disappear from alert log.
for , ORA-00313 open failed for members of log group of thread
consider checking the redo log file member if any of the is showing status INVALID , which means the redo log member is inaccessible on disk
SQL>select group#,status,type,member from v$logfile;
GROUP# STATUS TYPE MEMBER
---------- ----------- --------- ---------------------------------------------
---------- ----------- --------- ---------------------------------------------
1 ONLINE /u01/oradata/db1/redo01_a.log
1 ONLINE /u02/oradata/db1/redo01_b.log
2 ONLINE /u01/oradata/db1/redo02_a.log
2 ONLINE /u02/oradata/db1/redo02_b.log
3 INVALID ONLINE /u01/oradata/db1/redo03_a.log
3 ONLINE /u02/oradata/db1/redo03_b.log
4 STANDBY /u02/oradata/db1/redo04_d.log
5 STANDBY /u02/oradata/db1/redo04_d.log
6 STANDBY /u02/oradata/db1/redo04_d.log
crosscheck if above redolog file is accessible on OS
irrespective of which , perform below to fix the issue.
SQL>alter database recover managed standby database cancel;
SQL>alter database clear logfile group 3;
SQL>alter database recover managed standby database disconnect from session;
INVALID log file group will be cleared or re-created automatically in case its unavailable and standby MRP process will start applying all pending archived logs on standby database.
No comments:
Post a Comment