Errors
in file
/u01/app/oracle/diag/rdbms/standby_db/standby_db/trace/standby_db_lgwr_393229.trc:
ORA-00313:
open failed for members of log group 12 of thread 2
ORA-00312:
online log 12 thread 2: '+FRA_DG/standby_db/redolog12_02.rdo'
ORA-15173:
entry 'redo12_02.rdo' does not exist in directory/standby_db '
ORA-00312:
online log 12 thread 2: '+FRA_DG/standby_db /redolog12_01.rdo'
ORA-17503:
ksfdopn:2 Failed to open file +FRA_DG/standby_db /redolog12_01.rdo
ORA-15173:
entry 'redo12_01.rdo' does not exist in directory 'standby_db '
|
If you want to
use real time redo log apply and you try starting MRP (Managed Recovery
Process) with “USING CURRENT LOGFILE” clause, and if these errors appear in the
alert log file of standby database, it would mean that redo log files don’t
physical exist in the standby database. These messages are normal and can be
ignored, and real time redo apply would still work. If you don’t want to see
these error messages, then drop redo logfiles on standby database one by one
and then recreate them. Once you are able to see physical redo log files, you
will no longer see these error messages.
It will be
pertinent to note that even if you don’t create redo log files in the standby
database, redo log files get created automatically upon failover or switchover.
If Standby redo log files do not exist
If you are using
real time recover, you must create standby redo logs files; and these errors
will also appear if standby redo logs don’t physical exists. In this case, you
would need to drop and then re-create standby redo log groups in the standby
database and this action would physically create standby redo log files and
these errors would disappear from alert log file.
If you have log_file_name_convert already set, then starting MRP process would automatically create redo logs files and standby log files, thus, there will be no errors in alert log files.
Related Articles
- ORA-12514 During Switchover to Standby
- Heartbeat failed to connect to standby. Error is 16009
- Error 12154 received logging on to the standby
- Error 1017 received logging on to the standby - Along with ORA-16191
- Error 1031 received logging on to the standby
- Error 1033 received logging on to the standby
No comments:
Post a Comment