Applies to:

Oracle Server - Enterprise Edition - Version 10.2.0.1 to 11.2.0.2 [Release 10.2 to 11.2]
Information in this document applies to any platform.
Checked for relevance on 21-Sep-2012

Symptoms

ORA-16014 and ORA-00312 Messages in Alert.log of physical standby.

Alert.log shows: 
========== 
ORA-16014: log 8 sequence# 2386 not archived, no available destinations 
ORA-00312: online log 8 thread 2: '+DATADG/phpprd/onlinelog/group_8.271.636653821' 
ORA-00312: online log 8 thread 2: '+FLASHDG/phpprd/onlinelog/group_8.317.636653821' 

OR 

ORA-16014: log 6 sequence# 2393 not archived, no available destinations 
ORA-00312: online log 6 thread 2: '+FLASHDG/phpprd/onlinelog/group_6.645.684556605'

Cause

Issue occurs when both of following conditions fulfills:

++ There is no log_archive_dest_n parameter defined for standby redo log files archival
++ valid_for in log_archive_dest_1 is (ONLINE_LOGFILE,ALL_ROLES)

log_archive_dest_1 = location="+FLASHDG/phpprd/", valid_for=(ONLINE_LOGFILE,ALL_ROLES) 

Solution

++ Make sure we define log_archive_dest_n with correct valid_for attribute that enables standby redo logs archival.

ALTER SYSTEM SET log_archive_dest_2 = 'location=+FLASHDG/phpprd/ valid_for=(standby_logfile, standby_role) db_unique_name= boston';

Note:- boston is the standby db_unique_name here

OR

++ Remove valid_for from the log_Archive_dest_1, this assumes default valid_for attribute i.e., all_logfile, all_roles:

SQL>ALTER SYSTEM SET log_archive_dest_1 = 'location="+FLASHDG/phpprd/"';

ITPub博客

ORA-16014 and ORA-00312 Messages in Alert.log of Physical Standby. [ID 834771.1]

Applies to:

Symptoms

Cause

Solution

最新文章