10 Replies Latest reply: Jan 8, 2014 2:13 PM by teits RSS

    Dataguard Confusion

    fb767351-a660-4b18-9a9f-73bc141f6a0c

      Hi Gurus,

       

      I have implemented datagurad set up. Where my primary database is mydb and standby database is orcl. Now I am implementing dataguard broker and while after the configuration of broker I am seeing the disabled keyword is coming in front of physical standby database. Please check below.

       

      Before enabling the configuration:

       

      DGMGRL> show configuration;

       

      Configuration - PACKT


        Protection Mode: MaxPerformance

        Databases:

          mydb_un - Primary database

          orcl_un - Physical standby database

       

      Fast-Start Failover: DISABLED


      Configuration Status:

      DISABLED

       

      Enabling the configuration:

       

      DGMGRL> enable configuration;

      Enabled.

       

      After enbaling the configuration:

       

      DGMGRL> show configuration;


      Configuration - PACKT

       

        Protection Mode: MaxPerformance

        Databases:

          mydb_un - Primary database

          orcl_un - Physical standby database (disabled)

       

      Fast-Start Failover: DISABLED

       

      Configuration Status:

      SUCCESS

       

      Please check the red color font and kindly let me know what is the meaning of it and why it is coming as disabled.

       

       

      Regards,

      Michel.

        • 1. Re: Dataguard Confusion
          Pradeepcmst

          Hi Michel,

           

          The flashback feature has to be turned on , on both primary and standby database. Please check flashback is turned on both sites. If not , disable the broker configuration, enable flashback on both primary and standby sites and then enable broker configuration.

           

           

          Regards

          • 2. Re: Dataguard Confusion
            teits

            hi Pradeepcmst,

             

            the flashback feature is not a compulsory feature for data guard broker!!!

            please note!

             

            Tobi

            • 3. Re: Dataguard Confusion
              teits

              Hi Michel,


              there are a lot of reason for "(disabled)"


              check to see if your orcl_un database is in mount state or open. result?


              let see the latest output of your alert log file on orcl_un server.

               

              Tobi

              • 4. Re: Dataguard Confusion
                Pradeepcmst

                Hi Tobi, Thanks

                 

                Hi Michel ,

                Also try to restart the standby database in mount state

                • 5. Re: Dataguard Confusion
                  fb767351-a660-4b18-9a9f-73bc141f6a0c

                  Hi Tobi,

                   

                  Please check the below status for my orcl_un state:

                   

                  SQL> select db_unique_name, database_role, open_mode from v$database;

                   

                   

                  DB_UNIQUE_NAME                 DATABASE_ROLE    OPEN_MODE

                  ------------------------------ ---------------- --------------------

                  orcl_un                        PHYSICAL STANDBY READ ONLY WITH APPLY

                   

                  and below is last 70 lines of alert logs for orcl_un database:

                   

                  [oracle@localhost trace]$ tail -70f alert_orcl.log

                  Tue Jan 07 17:22:54 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 17:23:44 2014

                  RFS[20]: Assigned to RFS process 4768

                  RFS[20]: Identified database type as 'physical standby': Client is ARCH pid 32547

                  Tue Jan 07 17:28:56 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 17:29:44 2014

                  RFS[21]: Assigned to RFS process 4890

                  RFS[21]: Identified database type as 'physical standby': Client is ARCH pid 32547

                  Tue Jan 07 17:34:57 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 17:35:45 2014

                  RFS[22]: Assigned to RFS process 5042

                  RFS[22]: Identified database type as 'physical standby': Client is ARCH pid 32547

                  Tue Jan 07 17:39:58 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 17:41:45 2014

                  RFS[23]: Assigned to RFS process 5168

                  RFS[23]: Identified database type as 'physical standby': Client is ARCH pid 32547

                  Tue Jan 07 17:45:59 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 17:47:45 2014

                  RFS[24]: Assigned to RFS process 5323

                  RFS[24]: Identified database type as 'physical standby': Client is ARCH pid 32547

                  Tue Jan 07 18:24:34 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 18:24:54 2014

                  RFS[25]: Assigned to RFS process 5369

                  RFS[25]: Identified database type as 'physical standby': Client is ARCH pid 32547

                  Tue Jan 07 18:29:38 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 18:30:06 2014

                  RFS[26]: Assigned to RFS process 5492

                  RFS[26]: Identified database type as 'physical standby': Client is ARCH pid 32547

                  Tue Jan 07 18:35:38 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 18:36:06 2014

                  RFS[27]: Assigned to RFS process 5733

                  RFS[27]: Identified database type as 'physical standby': Client is ARCH pid 32547

                  Tue Jan 07 18:40:39 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 18:42:06 2014

                  RFS[28]: Assigned to RFS process 5845

                  RFS[28]: Identified database type as 'physical standby': Client is ARCH pid 32547

                  Tue Jan 07 18:46:40 2014

                  Errors in file /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc:

                  ORA-16057: server not in Data Guard configuration

                  PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                  Tue Jan 07 18:48:07 2014

                  RFS[29]: Assigned to RFS process 6054

                  RFS[29]: Identified database type as 'physical standby': Client is ARCH pid 32547

                   

                  Kindly check and let me know what's wrong here.

                   

                   

                  Regards,

                  Michel

                  • 6. Re: Dataguard Confusion
                    teits

                    hello,

                     

                    firstly,are you sure redo are being apply to orcl_un (your standby db). prove pls. http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm#i77231

                     

                    let see:

                    show parameter  LOG_ARCHIVE_CONFIG  ###on standby

                    show parameter fal_server ###on standby

                     

                    output of /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc (exclude repetition)

                     

                    Tobi

                    • 7. Re: Dataguard Confusion
                      fb767351-a660-4b18-9a9f-73bc141f6a0c

                      Hi Tobi,

                       

                      No, redo are not appling to orcl_un database now. I don't know what happened Suddenly. Please check below:

                       

                      On standby database:

                       

                      SQL> select sequence#, first_time, next_time from v$archived_log order by sequence#;

                       

                       

                      SEQUENCE# FIRST_TIM NEXT_TIME

                      ---------- --------- ---------

                              35 05-JAN-14 05-JAN-14

                              36 05-JAN-14 05-JAN-14

                              37 05-JAN-14 07-JAN-14

                              38 07-JAN-14 07-JAN-14

                              39 07-JAN-14 07-JAN-14

                              40 07-JAN-14 07-JAN-14

                              41 07-JAN-14 07-JAN-14

                              42 07-JAN-14 07-JAN-14

                              43 07-JAN-14 07-JAN-14

                              44 07-JAN-14 07-JAN-14

                              45 07-JAN-14 07-JAN-14

                       

                       

                      SEQUENCE# FIRST_TIM NEXT_TIME

                      ---------- --------- ---------

                              46 07-JAN-14 07-JAN-14

                              47 07-JAN-14 07-JAN-14

                              48 07-JAN-14 07-JAN-14

                              49 07-JAN-14 07-JAN-14

                              50 07-JAN-14 07-JAN-14

                              51 07-JAN-14 07-JAN-14

                              52 07-JAN-14 07-JAN-14

                              53 07-JAN-14 07-JAN-14

                       

                       

                      19 rows selected.

                       

                      Now switch logfile on primary database:

                       

                      SQL> alter system switch logfile;

                       

                       

                      System altered.

                       

                      Again now I checked standby database:

                       

                      SQL> select sequence#, first_time, next_time from v$archived_log order by sequence#;

                       

                       

                      SEQUENCE# FIRST_TIM NEXT_TIME

                      ---------- --------- ---------

                              35 05-JAN-14 05-JAN-14

                              36 05-JAN-14 05-JAN-14

                              37 05-JAN-14 07-JAN-14

                              38 07-JAN-14 07-JAN-14

                              39 07-JAN-14 07-JAN-14

                              40 07-JAN-14 07-JAN-14

                              41 07-JAN-14 07-JAN-14

                              42 07-JAN-14 07-JAN-14

                              43 07-JAN-14 07-JAN-14

                              44 07-JAN-14 07-JAN-14

                              45 07-JAN-14 07-JAN-14

                       

                       

                      SEQUENCE# FIRST_TIM NEXT_TIME

                      ---------- --------- ---------

                              46 07-JAN-14 07-JAN-14

                              47 07-JAN-14 07-JAN-14

                              48 07-JAN-14 07-JAN-14

                              49 07-JAN-14 07-JAN-14

                              50 07-JAN-14 07-JAN-14

                              51 07-JAN-14 07-JAN-14

                              52 07-JAN-14 07-JAN-14

                              53 07-JAN-14 07-JAN-14

                       

                       

                      19 rows selected.

                       

                       

                      On standby database:

                       

                      SQL> select db_unique_name, database_role, open_mode from v$database;

                       

                       

                      DB_UNIQUE_NAME                 DATABASE_ROLE    OPEN_MODE

                      ------------------------------ ---------------- --------------------

                      orcl_un                        PHYSICAL STANDBY MOUNTED

                       

                       

                      SQL> show parameter log_archive_config

                       

                       

                      NAME                                 TYPE        VALUE

                      ------------------------------------ ----------- ------------------------------

                      log_archive_config                   string      nodg_config

                      SQL> show parameter fal_server

                       

                       

                      NAME                                 TYPE        VALUE

                      ------------------------------------ ----------- ------------------------------

                      fal_server                           string

                       

                      # output of /u01/app/oracle/diag/rdbms/orcl_un/orcl/trace/orcl_arc2_32019.trc

                       

                       

                      *** 2014-01-07 15:03:50.728

                      *** 2014-01-07 15:03:50.728 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      Error 16009 attaching RFS server to standby instance at host 'mydb'

                      Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16009: invalid redo transport destination

                      *** 2014-01-07 15:03:50.761 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.

                      *** 2014-01-07 15:03:50.762 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16009 force:0 blast:1

                       

                       

                      *** 2014-01-07 15:09:50.836

                      Redo shipping client performing standby login

                      *** 2014-01-07 15:09:51.325 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      Error 16009 attaching RFS server to standby instance at host 'mydb'

                      Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16009: invalid redo transport destination

                      *** 2014-01-07 15:09:51.330 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.

                      *** 2014-01-07 15:09:51.330 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16009 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 15:15:51.592

                      *** 2014-01-07 15:15:51.592 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      Error 16009 attaching RFS server to standby instance at host 'mydb'

                      Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16009: invalid redo transport destination

                      *** 2014-01-07 15:15:51.654 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.

                      *** 2014-01-07 15:15:51.654 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16009 force:0 blast:1

                       

                       

                      *** 2014-01-07 15:21:51.743

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 15:21:51.919

                      *** 2014-01-07 15:21:51.919 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      Error 16009 attaching RFS server to standby instance at host 'mydb'

                      Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16009: invalid redo transport destination

                      *** 2014-01-07 15:21:51.937 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.

                      *** 2014-01-07 15:21:51.938 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16009 force:0 blast:1

                       

                       

                      *** 2014-01-07 15:27:52.000

                      Redo shipping client performing standby login

                      *** 2014-01-07 15:27:52.734 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      Error 16009 attaching RFS server to standby instance at host 'mydb'

                       

                       

                      *** 2014-01-07 15:27:52.880

                      Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16009: invalid redo transport destination

                      *** 2014-01-07 15:27:52.881 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.

                      *** 2014-01-07 15:27:52.881 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16009 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 15:32:55.707

                      *** 2014-01-07 15:32:55.707 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      Error 16009 attaching RFS server to standby instance at host 'mydb'

                      Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16009: invalid redo transport destination

                      *** 2014-01-07 15:32:55.778 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.

                      *** 2014-01-07 15:32:55.778 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16009 force:0 blast:1

                       

                       

                      *** 2014-01-07 15:38:55.925

                      Redo shipping client performing standby login

                      *** 2014-01-07 15:38:56.353 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      Error 16009 attaching RFS server to standby instance at host 'mydb'

                      Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16009: invalid redo transport destination

                      *** 2014-01-07 15:38:56.488 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.

                      *** 2014-01-07 15:38:56.488 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16009 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 15:44:56.778

                      *** 2014-01-07 15:44:56.778 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      Error 16009 attaching RFS server to standby instance at host 'mydb'

                      Error 16009 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16009: invalid redo transport destination

                      *** 2014-01-07 15:44:56.793 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16009.

                      *** 2014-01-07 15:44:56.793 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16009 force:0 blast:1

                       

                       

                      *** 2014-01-07 15:50:56.908

                      Redo shipping client performing standby login

                      *** 2014-01-07 15:50:57.167 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 15:50:57.241 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 15:50:57.241 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 15:56:57.425

                      Redo shipping client performing standby login

                      *** 2014-01-07 15:56:57.729 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 15:56:57.743 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 15:56:57.743 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 16:02:58.145

                      *** 2014-01-07 16:02:58.145 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 16:02:58.157 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 16:02:58.157 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 16:08:58.250

                      Redo shipping client performing standby login

                      *** 2014-01-07 16:08:58.386 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 16:08:58.397 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 16:08:58.397 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 16:14:59.007

                      *** 2014-01-07 16:14:59.007 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 16:14:59.018 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 16:14:59.018 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 16:20:59.086

                      Redo shipping client performing standby login

                      *** 2014-01-07 16:20:59.246 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 16:20:59.295 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 16:20:59.296 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 16:26:59.377

                      Redo shipping client performing standby login

                      *** 2014-01-07 16:26:59.505 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 16:26:59.514 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 16:26:59.514 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 16:32:59.873

                      *** 2014-01-07 16:32:59.873 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 16:32:59.884 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 16:32:59.884 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 17:05:52.903

                      *** 2014-01-07 17:05:52.903 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 17:05:52.908 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 17:05:52.908 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 17:10:53.827

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 17:10:54.214

                      *** 2014-01-07 17:10:54.214 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 17:10:54.352 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 17:10:54.352 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 17:16:54.439

                      Redo shipping client performing standby login

                      *** 2014-01-07 17:16:54.586 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 17:16:54.599 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 17:16:54.599 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 17:22:54.863

                      *** 2014-01-07 17:22:54.863 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 17:22:54.874 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 17:22:54.874 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 17:28:54.943

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 17:28:56.629

                      *** 2014-01-07 17:28:56.629 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 17:28:56.668 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 17:28:56.668 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 17:34:57.155

                      *** 2014-01-07 17:34:57.155 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                       

                       

                      *** 2014-01-07 17:34:57.344

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 17:34:57.362 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 17:34:57.362 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 17:39:58.619

                      Redo shipping client performing standby login

                      *** 2014-01-07 17:39:58.760 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 17:39:58.785 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 17:39:58.785 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 17:45:58.868

                      Redo shipping client performing standby login

                      *** 2014-01-07 17:45:59.198 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 17:45:59.203 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 17:45:59.203 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 18:24:33.861

                      *** 2014-01-07 18:24:33.861 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 18:24:34.152 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 18:24:34.152 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 18:29:37.942

                      Redo shipping client performing standby login

                      *** 2014-01-07 18:29:38.394 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 18:29:38.473 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 18:29:38.473 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 18:35:38.554

                      Redo shipping client performing standby login

                      *** 2014-01-07 18:35:38.912 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 18:35:38.938 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 18:35:38.938 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 18:40:39.370

                      *** 2014-01-07 18:40:39.370 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 18:40:39.397 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 18:40:39.397 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 18:46:39.475

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 18:46:40.213

                      *** 2014-01-07 18:46:40.213 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 18:46:40.717 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 18:46:40.718 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 18:52:40.787

                      Redo shipping client performing standby login

                      *** 2014-01-07 18:52:41.059 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 18:52:41.448 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 18:52:41.448 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 18:58:43.444

                      *** 2014-01-07 18:58:43.444 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 18:58:43.500 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 18:58:43.500 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      *** 2014-01-07 19:04:43.584

                      Redo shipping client performing standby login

                      *** 2014-01-07 19:04:44.210 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 19:04:44.278 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 19:04:44.278 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                      Redo shipping client performing standby login

                       

                       

                      *** 2014-01-07 19:10:44.750

                      *** 2014-01-07 19:10:44.750 4539 krsu.c

                      Logged on to standby successfully

                      Client logon and security negotiation successful!

                      This database DGID not in Data Guard configuration at 'mydb'

                      Error 16057 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'mydb'

                      ORA-16057: server not in Data Guard configuration

                      *** 2014-01-07 19:10:44.807 4132 krsh.c

                      PING[ARC2]: Heartbeat failed to connect to standby 'mydb'. Error is 16057.

                      *** 2014-01-07 19:10:44.808 2747 krsi.c

                      krsi_dst_fail: dest:2 err:16057 force:0 blast:1

                       

                       

                      I would like to let you know I was working fine before 7-8 hours. Please let me know how should I resolve it.

                       

                       

                      Regards,

                      Michel

                      • 8. Re: Dataguard Confusion
                        teits

                        Hi,

                         

                        ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(MYDB_UN,ORCL_UN)';  ##BOTH ON PRI AND STANDBY DB. i am assuming you have two db in your data guard config

                        ALTER SYSTEM SET FAL_SERVER= MYDB_UN; ## only on standby

                         

                        restart the redo apply services on standby.(broker should do this for you automatically. worst case restart standby db or manually execute the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE..... )

                         

                         

                        ALSO

                         

                        show parameter LOG_ARCHIVE_CONFIG  ##BOTH ON PRI AND STANDBY DB

                        SHOW PARAMETER LOG_ARCHIVE_DEST_2

                        SHOW PARAMETER LOG_ARCHIVE_DEST_STATE_2


                         

                        HTH

                        Tobi

                         

                        i like to believe some of the earlier post are helpful...if so mark accordingly.

                        • 9. Re: Dataguard Confusion
                          fb767351-a660-4b18-9a9f-73bc141f6a0c

                          Hi Tobi,

                           

                          I apologies for late reply. As per your suggestion please find below details:

                           

                          On Primary database:


                          SQL> select db_unique_name, database_role, name, open_mode from v$database;

                           

                           

                          DB_UNIQUE_NAME                 DATABASE_ROLE    NAME      OPEN_MODE

                          ------------------------------ ---------------- --------- --------------------

                          mydb_un                        PRIMARY          MYDB      READ WRITE

                           

                           

                           

                          SQL> show parameter log_archive_config

                           

                           

                          NAME                                 TYPE        VALUE

                          ------------------------------------ ----------- ------------------------------

                          log_archive_config                   string      dg_config=(mydb_un,orcl_un)

                           

                           

                          SQL> show parameter log_archive_dest_2

                           

                           

                          NAME                                 TYPE        VALUE

                          ------------------------------------ ----------- ------------------------------

                          log_archive_dest_2                   string      service="orcl", LGWR ASYNC NOA

                                                                           FFIRM delay=0 optional compres

                                                                           sion=disable max_failure=0 max

                                                                           _connections=1 reopen=300 db_u

                                                                           nique_name="orcl_un" net_timeo

                                                                           ut=30, valid_for=(all_logfiles

                                                                           ,primary_role)

                           

                          SQL> show parameter log_archive_dest_state_2

                           

                           

                          NAME                                 TYPE        VALUE

                          ------------------------------------ ----------- ------------------------------

                          log_archive_dest_state_2             string      ENABLE

                           

                           

                          On Standby Database:

                           

                          SQL> select db_unique_name, database_role, name, open_mode from v$database;

                           

                           

                          DB_UNIQUE_NAME                 DATABASE_ROLE    NAME      OPEN_MODE

                          ------------------------------ ---------------- --------- --------------------

                          orcl_un                        PHYSICAL STANDBY MYDB      MOUNTED

                           

                          SQL> show parameter fal_server

                           

                           

                          NAME                                 TYPE        VALUE

                          ------------------------------------ ----------- ------------------------------

                          fal_server                           string      MYDB_UN

                           

                          SQL> show parameter log_archive_config

                           

                           

                          NAME                                 TYPE        VALUE

                          ------------------------------------ ----------- ------------------------------

                          log_archive_config                   string      dg_config=(mydb_un,orcl_un)

                           

                          SQL> show parameter log_archive_dest_2

                           

                           

                          NAME                                 TYPE        VALUE

                          ------------------------------------ ----------- ------------------------------

                          log_archive_dest_2                   string      SERVICE=mydb delay=10 db_uniqu

                                                                           e_name=mydb_un

                           

                          SQL> show parameter log_archive_dest_state_2

                           

                           

                          NAME                                 TYPE        VALUE

                          ------------------------------------ ----------- ------------------------------

                          log_archive_dest_state_2             string      enable

                           



                          And please please check below my tns ans listener entries:

                           

                          [oracle@localhost admin]$ more listener.ora

                          # listener.ora Network Configuration File: /u01/home/oracle/product/11.2.0/db_1/network/admin/listener.ora

                          # Generated by Oracle configuration tools.

                           

                           

                          LISTENER =

                            (DESCRIPTION_LIST =

                              (DESCRIPTION =

                                (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))

                                (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))

                              )

                            )

                          SID_LIST_LISTENER =

                            (SID_LIST =

                              (SID_DESC =

                                (GLOBAL_DBNAME = mydb_un)

                                (ORACLE_HOME = /u01/home/oracle/product/11.2.0/db_1)

                                (SID_NAME=mydb)

                             )

                              (SID_DESC =

                                (GLOBAL_DBNAME = orcl_un)

                                (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)

                                (SID_NAME = orcl)

                           

                           

                              )

                          )

                          ADR_BASE_LISTENER = /u01/app/oracle

                           

                          [oracle@localhost admin]$ more tnsnames.ora

                          # tnsnames.ora Network Configuration File: /u01/home/oracle/product/11.2.0/db_1/network/admin/tnsnames.ora

                          # Generated by Oracle configuration tools.

                           

                           

                          MYDB =

                            (DESCRIPTION =

                              (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))

                              (CONNECT_DATA =

                                (SERVER = DEDICATED)

                                (SERVICE_NAME = mydb_un)

                              )

                            )

                          ORCL =

                            (DESCRIPTION =

                              (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))

                              (CONNECT_DATA =

                                (SERVER = DEDICATED)

                                (SERVICE_NAME = orcl_un)

                              )

                            )

                           

                          Looking forward for your response.

                           

                           

                          Regards,

                          Michel

                          • 10. Re: Dataguard Confusion
                            teits

                            Hello

                             

                            on both DBs, your listerner.ora should look like this:

                             

                            SID_LIST_LISTENER =

                              (SID_LIST =

                                (SID_DESC =

                                  (GLOBAL_DBNAME = stby_DGMGRL.teits.net)     ### this section is specifically for broker. stby  is the db_unique_name. teits.net is the domain name

                                  (ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1)

                                  (SID_NAME = stby)   ###stby here stand for sid_name

                                )

                                (SID_DESC =

                                  (GLOBAL_DBNAME = stby.teits.net)  ###stby is the for db_unique_name

                                  (ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1)

                                  (SID_NAME = stby)

                                )

                              )

                            ...##other section including dynamic listener section

                             

                            use tnsping utility and logon using sqlplus with tnsnames from primary to standby and vice versa.

                             

                            read : Data Guard Setup on Oracle 11 Step by Step

                            ORACLE-BASE - Data Guard Physical Standby Setup in Oracle Database 11g Release 2

                             

                            HTH

                            Tobi