This content has been marked as final. Show 6 replies
Might be a password issue. For Oracle 11 Copy the password file from Primary to the Standby and rename to the Standby SID.
As mentioned by "mseberg" you can validate the password file is same by using below command.
From primary database
Hello;1 person found this helpful
It's a good test but don't forget the as sysdba. Otherwise when you connect to a Standby from a Primary :
sqlplus sys/<password>@standby1 ERROR: ORA-01033: ORACLE initialization or shutdown in progress Process ID: 0 Session ID: 0 Serial number: 0
But I really like this test because you test Listener and Tnsnames with one test.
sqlplus sys/<password>@standby1 as sysdba SQL*Plus: Release 22.214.171.124.0 Production on Wed Apr 10 13:26:33 2013 Copyright (c) 1982, 2011, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 126.96.36.199.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options
Oh yeah i missed that somehow. Thanks for pointing out.
I did this testing before,see the below output :-
[oracle@primary ~]$ sqlplus sys/oracle@standby1 as sysdba
SQL*Plus: Release 188.8.131.52.0 Production on Thu Apr 11 08:07:06 2013
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Oracle Database 11g Enterprise Edition Release 184.108.40.206.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
I checked lot of other things, dgbroker log shows the below lines :-
2013-04-11 08:09:03.793 00000000 1207911714 for opcode = HEALTH_CHECK, phase = BEGIN, req_id = 1.1.1207911714
2013-04-11 08:09:48.669 00001000 1207911715 DMON: Entered rfm_get_chief_lock() for MON_VERIFY, reason 0
2013-04-11 08:09:48.670 00001000 1207911715 DMON: start task execution: client healthcheck
2013-04-11 08:09:48.670 INSV: Received message for inter-instance publication
2013-04-11 08:09:48.670 req ID 1.1.1207911715, opcode MON_VERIFY, phase BEGIN, flags 5
2013-04-11 08:09:48.888 INSV: Reply received for message with
2013-04-11 08:09:48.889 req ID 1.1.1207911715, opcode MON_VERIFY, phase BEGIN
2013-04-11 08:10:04.044 NSV1: Site standby1 returned ORA-16664.
2013-04-11 08:10:04.045 00000000 1207911715 DMON: Database standby1 returned ORA-16664
2013-04-11 08:10:04.045 00000000 1207911715 for opcode = MON_VERIFY, phase = BEGIN, req_id = 1.1.1207911715
2013-04-11 08:10:04.045 00000000 1207911715 DMON: Entered rfm_release_chief_lock() for MON_VERIFY
Any other further troubleshooting tips will be great.
Thanks in advance.
Well at least that rules that out. There's a couple of Oracle notes on this :1 person found this helpful
ORA-16664 ORA-16792 Data guard Broker [ID 1228797.1]
Dataguard Broker switchover fails with an ORA-16664 and the standby DRC log shows an ORA-604. [ID 1530881.1]
Information Center: Troubleshoot Oracle Data Guard Physical Standby Database [ID 1396731.2]