6 Replies Latest reply: Apr 11, 2013 10:35 AM by mseberg RSS

    Issue with Dataguard Broker

    sandy121
      DB Version -Oracle Database 11g Enterprise Edition Release 11.2.0.2.0

      DGMGRL> show configuration;

      Configuration - testDG

      Protection Mode: MaxPerformance
      Databases:
      orcl - Primary database
      standby1 - Physical standby database
      Error: ORA-16664: unable to receive the result from a database

      Fast-Start Failover: DISABLED

      Configuration Status:
      ERROR

      I completed all basic checks i.e 1) Listerner on both standby and physical db's contains entry for DGMGRL 2) tnsping is working fine from both primary and physical dB’s, 3) I disabled configuration, removed the old broker configuration files and rebuild it, still the issue is not resolved4) All other issues like log shipping and sync is perfect in the configuration


      Any help here will be highly appreciated !!

      Thanks in advance .

      Edited by: 918868 on Apr 10, 2013 10:40 AM
        • 1. Re: Issue with Dataguard Broker
          mseberg
          Hello;

          Might be a password issue. For Oracle 11 Copy the password file from Primary to the Standby and rename to the Standby SID.

          Best Regards

          mseberg
          • 2. Re: Issue with Dataguard Broker
            NC
            As mentioned by "mseberg" you can validate the password file is same by using below command.

            From primary database
            sqlplus sys/<password>@standby1
            Regards,
            NC
            • 3. Re: Issue with Dataguard Broker
              mseberg
              Hello;

              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
              With :
              sqlplus sys/<password>@standby1 as sysdba
              
              
              SQL*Plus: Release 11.2.0.3.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 11.2.0.3.0 - 64bit Production
              With the Partitioning, OLAP, Data Mining and Real Application Testing options
              But I really like this test because you test Listener and Tnsnames with one test.

              Best Regards

              mseberg
              • 4. Re: Issue with Dataguard Broker
                NC
                Oh yeah i missed that somehow. Thanks for pointing out.

                Regards,
                NC
                • 5. Re: Issue with Dataguard Broker
                  sandy121
                  I did this testing before,see the below output :-

                  [oracle@primary ~]$ sqlplus sys/oracle@standby1 as sysdba

                  SQL*Plus: Release 11.2.0.2.0 Production on Thu Apr 11 08:07:06 2013

                  Copyright (c) 1982, 2010, Oracle. All rights reserved.


                  Connected to:
                  Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production
                  With the Partitioning, OLAP, Data Mining and Real Application Testing options

                  SQL>


                  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.
                  • 6. Re: Issue with Dataguard Broker
                    mseberg
                    Well at least that rules that out. There's a couple of Oracle notes on this :



                    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]

                    Best Regards

                    mseberg