Dataguard Confusion

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.

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

Similar Messages

  • How to Configure  Oracle Management Server (OMS) with  Dataguard Broker

    Dear Experts,
    i have a production DB (192.168.200.9) 9.2.0.1.0 on Server 2003
    i have a standby DB (192.168.200.19) 9.2.0.1.0 on Server 2003
    Archive logs are shipped to standby database and applied there. *(Datagauard is configured).*
    Now i want that Graphically i want to see that archivelogs are shipping to standby database and applied there ( i want to configure Dataguard Broker in graphical mode (*dataguard manager*) isnt it ( bcz i anm bit confused with this).............?
    *1.* For this purpose to achieve i take some seperate machine install on it Server 2003.
    *2.* and then Install oracle db 9.2.0.1.0 ( here i will install FULL DATABASE, CUSTOM installation ( then createsome repository).
    *3*. can i configure this repository for OMS on my already running production or standby DB............?
    *4.* After this OMS is configured or not..........?
    *5.* how i will configure datagauard broker
    what i know regarding this is on primary and standby db *( DG_BROKER_START = TRUE)* and after
    this we have to create some configuration wizards but how
    i think i have to go with this sequence if somebody has different sequence tellm e
    wait for replies
    thanks in advance
    regards rehan
    faisalabad pakistan

    Does anybody dont know anything about this.................?

  • Buffer busy waits on UNDO data in Active Dataguard

    Oracle Version: 11.1.0.7.0
    Active Dataguard
    Statspack has been configured for Active Dataguard on Primary database.
    We got an spike of Buffer busy waits for about 5 min in Active Dataguard, this was causing worse Application SQL's response time during this 5 min window.
    Below is what i got from statspack report for one hour
    Snapshot       Snap Id     Snap Time      Sessions Curs/Sess Comment
    ~~~~~~~~    ---------- ------------------ -------- --------- -------------------
    Begin Snap:      18611 21-Feb-13 22:00:02      236       2.2
      End Snap:      18613 21-Feb-13 23:00:02      237       2.1
       Elapsed:               60.00 (mins)
    Top 5 Timed Events                                                    Avg %Total
    ~~~~~~~~~~~~~~~~~~                                                   wait   Call
    Event                                            Waits    Time (s)   (ms)   Time
    buffer busy waits                                2,359       2,133    904   76.2
    reliable message                                 7,210         179     25    6.4
    parallel recovery control message reply          8,831         109     12    3.9
    CPU time                                                       100           3.6
    latch free                                          13          85   6574    3.1
    Host CPU  (CPUs: 16)
    ~~~~~~~~              Load Average
                          Begin     End      User  System    Idle     WIO     WCPU
                           1.07    0.82      0.68    0.39   98.88    0.00Since this is 11g version I was able to drill down on the segment on which buffer busy waits were occurring by using v$active_session_history on Active Dataguard.
    SQL> select count(*),p1,p2 from v$active_session_history where event='buffer busy waits' and sample_time between to_date('21-FEB-2013 21:55:00','DD-MON-YYYY HH24:MI:SS') and to_date('21-FEB-2013 22:09:00','DD-MON-YYYY HH24:MI:SS') group by p1,p2
      COUNT(*)         P1         P2
          2136          3      99405
            17          3       7293
    SQL> select owner,segment_name,segment_type from dba_extents where file_id = 3 and 99405 between block_id AND block_id + blocks - 1
    OWNER                          SEGMENT_NAME              SEGMENT_TYPE
    SYS                            _SYSSMU14_1303827994$     TYPE2 UNDO
    SQL> select owner,segment_name,segment_type from dba_extents where file_id = 3 and 7293 between block_id AND block_id + blocks - 1;
    OWNER                          SEGMENT_NAME              SEGMENT_TYPE
    SYS                            _SYSSMU11_1303827994$     TYPE2 UNDOThought to check the SQL_ID which were waiting on this buffer busy waits.
    SQL> select count(*),sql_id,session_state from v$active_session_history where event='buffer busy waits' and sample_time between to_date('21-FEB-2013 21:55:00','DD-MON-YYYY HH24:MI:SS') and to_date('21-FEB-2013 22:09:00','DD-MON-YYYY HH24:MI:SS') group by sql_id,session_state order by 1;
      COUNT(*) SQL_ID        SESSION_STATE
             1 cvypjyh0mm56x WAITING
             1 02dtz82as4y42 WAITING
             1 80gz2r4hx1wrj WAITING
             2 6tfk1t4mwt7hu WAITING
             9 0q63qhsbqmpf0 WAITING
            12 0jgnx96ur0bmb WAITING
            12 7pguapqcc6372 WAITING
            14 4t6hqk5r2zbqs WAITING
            18 1qwt0qkd59xj3 WAITING
            23 5phgg8btvhh6p WAITING
            23 banp2v6yttym7 WAITING
            30 a1kdmb1x084yh WAITING
            30 8hxuagk22f8jz WAITING
            30 9r0nysyp360hn WAITING
            31 cackx62yu477k WAITING
            32 40zxqg1qrdvuh WAITING
            32 0jqrd56ds1rbm WAITING
            32 7009zmuhvac54 WAITING
            38 1jb37ryn1c871 WAITING
            60 aum74caa623rs WAITING
            63 cr8mv0wawhak9 WAITING
            63 3xgk3vsh3nm08 WAITING
            86 3k9cq3jv0c3rg WAITING
            95 0sy9vjuutgwqu WAITING
           122 bhn2kk76wpg12 WAITING
           134 4pkfqgyt7rh34 WAITING
           139 1sbzsw7y88c7t WAITING
           146 92y0ha2nqd6zj WAITING
           163 djjqcp1sg2twb WAITING
           173 arxq6au12zazw WAITING
           256 fa0gzxmgyyxj2 WAITING
           282 2f17qywcgu751 WAITINGSo top 10 sql_id's were on tables TAB1 and TAB2 under schemas SCHEMA1 to SCHEMA8.
    Checked DML's occurred on Primary using dba_tab_modifications view since last stats job ran on these was about 10 hours ago from when the issue occurred on Active Dataguard.
    SQL> select TABLE_OWNER,TABLE_NAME,INSERTS,UPDATES,DELETES from dba_tab_modifications where TABLE_NAME='TAB1' order by 3;
    TABLE_OWNER               TABLE_NAME              INSERTS    UPDATES    DELETES
    SCHEMA1                    TAB1                     4448          0       3728
    SCHEMA2                    TAB1                     4547          0       4022
    SCHEMA3                    TAB1                     4612          0       4152
    SCHEMA4                    TAB1                     4628          0       3940
    SCHEMA5                    TAB1                     4719          0       4258
    SCHEMA6                    TAB1                     4809          0       4292
    SCHEMA7                    TAB1                     4853          0       4356
    SCHEMA8                    TAB1                     5049          0       4536
    SQL> select TABLE_OWNER,TABLE_NAME,INSERTS,UPDATES,DELETES from dba_tab_modifications where TABLE_NAME='TAB2' order by 3;
    TABLE_OWNER               TABLE_NAME                  INSERTS    UPDATES    DELETES
    SCHEMA1                    TAB2                        25546          0      26360
    SCHEMA2                    TAB2                        26728          0      27565
    SCHEMA3                    TAB2                        27403          0      27763
    SCHEMA4                    TAB2                        27500          0      28149
    SCHEMA5                    TAB2                        28408          0      30440
    SCHEMA6                    TAB2                        30453          0      31906
    SCHEMA7                    TAB2                        31469          0      31988
    SCHEMA8                    TAB2                        32875          0      34670 But confused about Why there could sudden spike of demand on UNDO data in Active Data Guard ? Could any one please shed some lights on finding the reason for this issue ?

    But confused about Why there could sudden spike of demand on UNDO data in Active Data Guard ? Could any one please shed some lights on finding the reason for this issue ?It's been interesting, The job runs only on ADG?
    Even it is only reporting purposes, Which runs only select statements. Are you sure that issue is only because of this job?
    Moreover am interested to know, How you able to monitor at the same time? Using EM?
    What all are the jobs ran on primary at the same time?
    Then, is it possible to run the job on primary and see whats the response?
    I suggest you to run the same job again on standby and see the ET of the job and also gather the statspack to check whether you got same buffer busy waits or not.
    What storage you are using for primary and standby? In terms of I/O and performance all are same?
    You got chance to take statspack even on primary database?
    What are the parameters differ in primary and standby?
    Also check this note, Heresome work around provided.
    *Resolving Intense and "Random" Buffer Busy Wait Performance Problems [ID 155971.1]*

  • Dataguard Config - Primary ASM - Standby Non ASM

    Hi,
    I'm having an issue with a new configuration of dataguard.
    Primary Standby
    OS Win2008 R2 Win2008 R2
    DB 11.2.0.2 11.2.0.2
    Storage ASM NTFS
    I have created standby logs on the standby and on the primary. I have configured real time apply(maximum availibility) but when I look in the rfs.trc files on standby I receive the following error:
    primary database is in maximum protection or maximum availability mode and the standby database does not contain and viable standby redo logs.
    I dropped all standby logs on the standby and recreated them, the real time apply then worked until all the standby redo logs filled. Now I'm receiving the error again.
    For some reason the standby logs are not clearing and this is the issue. I have looked at metalink notes Error At Standby Database Ora-16086: Standby Database Does Not Contain Available Standby Log Files [ID 1155773.1] and Primary Database Stops with ORA-16098 When Standby Put in Protected Mode [ID 187235.1].
    I think the issue may be that the primary databases online redo logs are on asm disks and the standby are on ntfs disks. I can't find any clear documentation that says that this config is unsupported. Any ideas would be greatly appreciated.
    Keith
    SQL> select group#, thread#, sequence#, used, archived, status, first_change#, n
    ext_change#, last_change# from v$standby_log;
    GROUP# THREAD# SEQUENCE# USED ARC STATUS FIRST_CHANGE#
    NEXT_CHANGE# LAST_CHANGE#
    5 2 255 30208 NO ACTIVE 196829409
    196829442 196829442
    6 2 254 3308032 NO ACTIVE 196826945
    196829409 196829409
    7 2 256 5200896 NO ACTIVE 196829442
    196838727 196838727
    8 2 257 6098944 NO ACTIVE 196838727
    196849666 196849666
    9 2 258 9165312 NO ACTIVE 196849666
    196862607 196862607
    SQL> SELECT GROUP#, BYTES FROM V$LOG;
    GROUP# BYTES
    1 52428800
    2 52428800
    3 52428800
    4 52428800
    SQL> SELECT GROUP#, BYTES FROM V$STANDBY_LOG;
    GROUP# BYTES
    5 52428800
    6 52428800
    7 52428800
    8 52428800
    9 52428800
    Primary Errors:
    TO_CHAR(TIMESTAMP,'YYYY-MON-DDHH24:MI:SS')||''||MESSAGE
    2011-DEC-08 12:00:12 LGWR: Destination LOG_ARCHIVE_DEST_2 network reconnect ab
    andoned
    2011-DEC-08 12:00:12 Error 16086 for archive log file 3 to 'PBONDSDR'
    2011-DEC-08 12:00:13 LGWR: Failed to archive log 3 thread 2 sequence 503 (1608
    6)
    2011-DEC-08 12:00:13 ARC3: Beginning to archive thread 2 sequence 502 (1971278
    31-197131866)
    TO_CHAR(TIMESTAMP,'YYYY-MON-DDHH24:MI:SS')||''||MESSAGE
    2011-DEC-08 12:00:13 ARC3: Completed archiving thread 2 sequence 502 (19712783
    1-197131866)
    standby Errors:
    2011-DEC-08 11:54:09 Media Recovery Waiting for thread 2 sequence 501
    2011-DEC-08 11:54:09 Primary database is in MAXIMUM AVAILABILITY mode
    2011-DEC-08 11:54:09 Standby controlfile consistent with primary
    2011-DEC-08 11:54:10 Standby controlfile consistent with primary
    2011-DEC-08 11:54:10 RFS[46]: Assigned to RFS process 3956
    2011-DEC-08 11:54:10 RFS[46]: No standby redo logfiles available for thread 2
    2011-DEC-08 11:54:10 RFS[46]: No standby redo logfiles selected (reason:7)
    2011-DEC-08 12:00:09 RFS[47]: Assigned to RFS process 2080
    2011-DEC-08 12:00:10 Media Recovery Log C:\ORACLE\FAST_RECOVERY_AREA\PBONDSDR\

    Standby database
    QL> select group#, thread#, status from v$standby_log;
    GROUP# THREAD# STATUS
    5 2 ACTIVE
    6 2 ACTIVE
    7 2 ACTIVE
    8 2 ACTIVE
    9 2 ACTIVE
    Primary DB
    SQL> select group#, thread#, members, status from v$log;
    GROUP# THREAD# MEMBERS STATUS
    1 1 2 INACTIVE
    2 1 2 INACTIVE
    3 2 2 CURRENT
    4 2 2 ACTIVE
    Minimally, the configuration should have one more standby redo log file group than the number of online redo log file groups on the primary database. However, the recommended number of standby redo log file groups is dependent on the number of threads on the primary database. Use the following equation to determine an appropriate number of standby redo log file groups:
    (maximum number of logfiles for each thread + 1) * maximum number of threads
    Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database.
    I'm a bit confused by above note does that mean I should create (2+1)*2 =6 standby logs?
    Thanks,
    keith

  • Cannot login oim after restore db from other server using dataguard

    Hi all,
    i find a problem,
    I installed OIM 11g R1 application and database both DC and DRC server, and all application and database is already running normally. i used dataguard for set up both database.so, i restore database DRC to DC, and database DC already restored and weblogic,oim server,soa already up. but when i try to login into oim application i cannot login because wrong password, and i go to forgot password i get the popup error "cant find resource for bundle java.util.PropertyResourceBundle". i think this problem about keystore, but when i copy keystore in server DRC to DR, this problem can't be solve.
    any idea to solve this problem? or i set up dataguard using different way with oracle best practice?
    env :
    OIM 11.1.1.5 patch 7
    wl 10.3.5
    db 11.2.0

    Hi San Xu,
    Thanks for the reply.
    I cannot remove add-on with this database, when I click button update there is same message "Continue working without this Add-on"
    I already try to remove the add-on in Test Server with another database in same server (I can remove the add-on used another database) and then I try to clear up entries in registration file and then try to run SAP B1 as administrator to register and install again with the database which infected, with result cannot install with same message "Continue working without this Add-on", but I can install again the add-on with another database with no problem and the add-on run well in another database.
    I'm very confused, why any add-on cannot installed in this database only and also cannot remove use this database but run well (can installed, can remove and also can used) in another database in same server.
    I also already try such your suggestions to create a new test company in Test Server and try remove and installing the add-on with the new database, there is no problem with this new database (the add-on can remove, installed and then can run well in the new database). But still the add-on cannot run in the database which I backup from Production Server.
    Best Regards,
    Silvy

  • Flashback in dataguard environment

    Hi,
    We have dataguard environment with Sun OS & Oracle 10g, 11g. Now we want to enable flashback for the primary database as well as standby database (physical standby). NO RMAN. I did manage to configure the flashback for the primary database but confusion is:
    -- Do I need to configure flashback at standby or recreate standby after enabling flashback at primary site?
    -- Suppose if I use flashback database to restore point and open database with resetlogs, what would be the situation at standby site? Will it be in sync with primary or after resetlogs I need to make new standby database??
    -- Is there any space requirement ratio for flashback recovery partition?
    Thanks,
    Amit.

    If you only enabled flashback on your Primary, your Standby is not affected. If you did actually a flashback database on your Primary, you need to address that on the Standby. See an example here:
    http://uhesse.wordpress.com/oracle-database-ha-architecture/2010/08/06/using-flashback-in-a-data-guard-environment/
    Kind regards
    Uwe Hesse
    http://uhesse.wordpress.com

  • Standby database Archive log destination confusion

    Hi All,
    I need your help here..
    This is the first time that this situation is arising. We had sync issues in the oracle 10g standby database prior to this archive log destination confusion.So we rebuilt the standby to overcome this sync issue. But ever since then the archive logs in the standby database are moving to two different locations.
    The spfile entries are provided below:
    *.log_archive_dest_1='LOCATION=/m99/oradata/MARDB/archive/'
    *.standby_archive_dest='/m99/oradata/MARDB/standby'
    Prior to rebuilding the standby databases the archive logs were moving to /m99/oradata/MARDB/archive/ location which is the correct location. But now the archive logs are moving to both /m99/oradata/MARDB/archive/ and /m99/oradata/MARDB/standby location, with the majority of them moving to /m99/oradata/MARDB/standby location. This is pretty unusual.
    The archives in the production are moving to /m99/oradata/MARDB/archive/ location itself.
    Could you kindly help me overcome this issue.
    Regards,
    Dan

    Hi Anurag,
    Thank you for update.
    Prior to rebuilding the standby database the standby_archive_dest was set as it is. No modifications were made to the archive destination locations.
    The primary and standby databases are on different servers and dataguard is used to transfer the files.
    I wanted to highlight one more point here, The archive locations are similar to the ones i mentioned for the other stndby databases. But the archive logs are moving only to /archive location and not to the /standby location.

  • Dataguard broker

    Hi ,
    I have confusion about standby database in oracle 10g ,bcoz dataguard and physical standby database is same or not ?
    if same what is Dataguard Broker in standby?
    what is the difference between enable dg_broker_start = true and false / also what is the nature of job?
    Regards,
    S.Mugunthan

    I have confusion about standby database in oracle 10g ,bcoz dataguard and physical standby database is same or not ?Data Guard is again priced product & Standby Database is a standard feature. You only may need another database license for the instance.
    But you have to do all your own scripting to move archived redo logs to the standby to be applied, including any error checking.
    Dataguard is the process to mirroring your Production/primary database. Dataguard manage your database primary and your database standby.
    Even you can perform Switchovers & also failovers.
    With Data Guard Oracle provides all that as part of the package, plus some management tools. The core still remains a Standby Database, either physical or logical.
    if same what is Dataguard Broker in standby? You can say Datagaurd broker instead of standby broker, Broker will be enabled when it is configured in both primary & also standby database.
    is again a utility where you can manage all Monitoring, Drilling (switching/faliver) via DGMGRL
    In detail for this utility please do refer http://docs.oracle.com/cd/B28359_01/server.111/b28295/concepts.htm
    what is the difference between enable dg_broker_start = true and false / also what is the nature of job?DG_BROKER_START enables Oracle to determine whether or not the Data Guard broker (DMON) process should be started. DMON is a non-fatal Oracle background process and exists as long as the instance exists, whenever this parameter is set to true.
    In detail refer http://docs.oracle.com/cd/B19306_01/server.102/b14237/initparams060.htm
    HTH.

  • Regarding dataguard

    Dear all,
    Please help me regarding this i am very much confused.....
    I had couple of doubts in dataguard concepts.
    1)When archive log is transferred from primary to standby ,
    a.Whether DBWR will be in active state or not in standby server.To write the contents in the archived redo log files which came from the primary to the datafiles of the standby server.
    b.I am using online redo logs in the standby server not standby redo logs , whether online redologs in the standby server will have any effect in shipping of redologs from the primary database,
    c. In my standby database online redo logs state is changing between CLEARING AND CLEARING CURRENT.How standby server redologs will change it state,
    Regards,
    Vamsi.

    Hi Vamsi,
    In a case you use standby redo logs on standby;
    RFS process reads redo stream and writes to standby redo logs.
    ARCH process on the standby archives standby redologs into archivedlogs.
    MRP process reads standby redo logs or archived log (depending on configuration) into the buffer cache. (shortly!)
    DBWR writes modified blocks from buffer cache to disk.
    You cannot say "I am using online redo logs in the standby server not standby redo logs" You can choose using or not using SRLs. If you don't use SRL on the standby, redo stream will be directly written to archived logs. Online redologs are out of this scope.
    Online redo logs are not used in a physical standby database. They exist in order to be used in a case of opening the standby database read-write (failover/snapshot standby). Here what documentation says:
    Online redo logs
    Every instance of an Oracle primary database and logical standby database has an associated online redo log to protect the database in case of an instance failure. Physical standby databases do not have an associated online redo log, because physical standby databases are never opened for read/write I/O; changes are not made to the database and redo data is not generated.
    +...+
    Create an Online Redo Log on the Standby Database
    Although this step is optional, Oracle recommends that an online redo log be created when a standby database is created. By following this best practice, a standby database will be ready to quickly transition to the primary database role.
    +...+

  • Doubt in Dataguard concept

    Dear all,
    Please help me regarding this i am very much confused.....
    I had couple of doubts in dataguard concepts.
    1)When archive log is transferred from primary to standby ,
    a.Whether DBWR will be in active state or not in standby server.To write the contents in the archived redo log files which came from the primary to the datafiles of the standby server.
    b.I am using online redo logs in the standby server not standby redo logs , whether online redologs in the standby server will have any effect in shipping of redologs from the primary database,
    c. In my standby database online redo logs state is changing between CLEARING AND CLEARING CURRENT.How standby server redologs will change it state,
    Regards,
    Vamsi.

    Hi again,
    They are not used in a physical standby database. They exist in order to be used in a case of opening the standby database read-write (failover/snapshot standby). Here what documentation says:
    Online redo logs
    Every instance of an Oracle primary database and logical standby database has an associated online redo log to protect the database in case of an instance failure. Physical standby databases do not have an associated online redo log, because physical standby databases are never opened for read/write I/O; changes are not made to the database and redo data is not generated.
    Create an Online Redo Log on the Standby Database
    Although this step is optional, Oracle recommends that an online redo log be created when a standby database is created. By following this best practice, a standby database will be ready to quickly transition to the primary database role.
    ...

  • DataGuard... SYNC/ASYNC

    I m studying dataguard, but I m having confusion in parameter SYNC, ASYNC, AFFIRM, NOAFFIRM. Please explain how these parameters affect the Primary/Standby Databases.

    HI,
    SYNC, ASYNC,AFFIRM, NOAFFIRMthese are basically used in which mode your standby is running.
    In maximum protection & availibilty mode the logs from Primary DB are shipped synchronously and shipped to standby.
    lgwr writes it synchronously .
    In Maximum performance mode asynchronously logs ar shipped by archiver or lgwr.(asynch. only if lgwr).
    HTH.
    Message was edited by:
    Ora-Lad

  • DataGuard question - overcoming network latency problem

    Hi
    Dataguard for 10.2.0.4
    Assuming we have a latency problem with the network between the primary and secondary databases in a dataguard configuration.
    That means that my bottleneck is currently the network that cannot accommodate the amount of redo that is generated per second by the primary, and archive logs are accumulating on the primary site
    Is there a way to configure the redo transport on the primary to transfer the archive logs in parallel – in case there is an accumulation of archive logs waiting to be shipped
    I am talking parallel transfer to the same site , not to different sites – just to overcome the network bottleneck
    Thanks in advance
    Orna

    Hi Sybrand,
    Quoting from the doc
    'Oracle Database 10g Release 2 introduces the ability to have multiple ARCn processes sending redo for a single archived-redo log over the network, reducing the time required to ship a single archive log to a remote destination. In previous Oracle Database releases, only one ARCn process at a time could archive redo from a given log file. The maximum number of network connections that will be used in parallel to perform archival to a destination is controlled using the MAX_CONNECTIONS attribute of the LOG_ARCHIVE_DEST_n initialization parameter. The LOG_ARCHIVE_MAX_PROCESSES initialization parameter can be set as high as 30, (the previous maximum was 10)'
    My 'back of a cigarette packet' calculation was not meant to be exact just meant to illustrate a point :-)
    I still think your confusing bandwidth with latency but I don't want to poke an angry response :-)
    Cheers,
    Harry
    Edited by: Harry on Jul 10, 2009 3:33 PM - seems the language filter doesn;t like my British slang. Changed to cigarette......

  • Oracle 10g dataguard Connect-time failover Parameter 15 minutes

    Hello,
    we running a system with DataGuard in Maximum Availability protection mode and one physical Standby Database. There are two connections between primary and standby. I configured listener and tnsnames to perform a Connect-time failover in case one connection is down. In first place it seemed to work fine but since it has happened that the primary always hangs for exactly 15 minutes until the failover is performed. (ALL redologs need archiving)
    I think this must be the default value of a Parameter but reading docs for hours I can't find it.
    Can anybody help me?
    Best regards
    Fritz

    It's like this. The connection failover I'm talking about is only between the primary database and standby database. I have two connections between them. That makes two addresses for the service (servicetostandby) specified in the log_archive_dest used by dataguard. In my case the log_archive_dest Paramater looks like this:
    log_archive_dest_3 = 'SERVICE servicetostandby OPTIONAL LGWR SY
    NC AFFIRM VALID_FOR=(ONLINE_LO
    GFILES,PRIMARY_ROLE) DB_UNIQUE
    NAME=standby REOPEN=10 NETTIME
    OUT=9'
    The tnsnames.ora entry looks like this:
    servicetostandby =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = address1)(PORT = 1521))
    (ADDRESS = (PROTOCOL = TCP)(HOST = address2)(PORT = 1521))
    (FAILOVER=true)
    (LOAD_BALANCE=false)
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = standby)
    So if either address1 or address2 is down dataguard should use the other address to connect to the standby database.
    Maybe because of the Maximum Availability protection mode the primary database does not perform if the standby database is not available. I'm not sure about that. But fact is that if I power off the standby database, the primary database hangs only for 9 seconds. That's specified in the net_time_out attribut of the log_archive_dest Parameter. So I'm quite sure that something in the oracle net service causes the problem.
    With the "primary hangs" I mean: After the used connection (say address1) went down the redologfiles of the primary database get filled and then it stops for 15 minutes. The messages in the alert.log:
    Thread 1 cannot allocate new log, sequence 1304
    All online logs needed archiving
    After 15 minutes the connection via address2 is established and everything works fine.
    I hope I made myself clear this time and didn't confuse you totally.
    Edited by: user633694 on Apr 14, 2009 8:13 AM

  • Choosing protection mode for Active dataguard

    Hi Gurus,
    I'm confused with Active dataguard configuration-What mode do i need to configure physical standby to make use of actice dataguard.I know i can even use maximum performance with standby redolog for real time query.But what is the minimum protection mode to run active dataguard.
    How can i setup a delay of 1 hour for active dataguard in 11gr2?
    Thanks

    You said:
    >
    By default Dataguard is in Maximum performance mode..we can set delay of 1 hour by setting the
    log_archive_dest_2="service=to_standby lgwr async affirm reopen=60"
    or
    log_archive_dest_2="service=to_standby lgwr async delay=60"
    >
    I am sorry, but your first log_archive_dest_2 value is not correct:
    The combination of ASYNC & AFFIRM is not supported and not sensible; REOPEN=60 will not delay the Redo Apply
    See here for a proper explanation of log_archive_dest_n:
    http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/initparams121.htm
    Kind regards
    Uwe Hesse
    http://uhesse.wordpress.com

  • 10g , dataguard, em starts database ok but then cant read status

    I am attempting to get dataguard up and running. The problem I am stuck at is that the Enterprose manage starts up the database with no problem but them the following message appears :-
    #The database status is currently unavailable. It is possible that the database is in mount or nomount state#
    I can however access the database perfectly and read tables using sqlplus !!
    I am very confused about how to configure the listener.ora file . I suspect this may be the problem.
    Here is some further info thanks !!
    SQL> sho parameters name
    NAME TYPE VALUE
    db_file_name_convert string
    db_name string MVM
    db_unique_name string MVM1
    global_names boolean FALSE
    instance_name string MVM
    lock_name_space string
    log_file_name_convert string
    service_names string MVM1
    sp_name string MVM
    SQL>
    The following is the contents of the listener.ora file :-
    SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = /export/home/oracle/product/10.1)
    (PROGRAM = extproc)
    LISTENER =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = mvm1)(PORT = 1521))
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
    The database is definately not in the nomount or mount state
    SQL> select OPEN_MODE from v$database;
    OPEN_MODE
    READ WRITE
    SQL>

    No, I'm just working through the procedure for configuring the master server first , the next step is to configure the standby database .
    George

Maybe you are looking for

  • SAP Business One  8.8Client throughs a .Dmp file

    Hi Experts, When we click Set Authorize Button  in Report & Layout Manager  ,SAP Business One  8.8Client throughs a .Dmp file Error and Closes Itself Immediately. Then Also When we try To Open Reports Some times It Throughs The .Dmp File Error And Cl

  • PO output with XML and PDF format

    Hi All, I need PO output with XML and PDF format. when I give print it shld go to vendor with xml and pdf format through mail. please kindly guide me on this . Thanks in advance JK

  • Powerbook AC/battery issue

    Hi there wondered if anyone could give advice to this issue. I recently acquired a used Powerbook G4 Aluminum 15" widescreen which I bought knowing it had a dead battery which I'm due to replace, however as I have to leave it plugged in with the ac a

  • Adding new rows after displaying subtotals in an ALV report by using OOABAP

    Dear All, I am creating an ALV report, displaying subtotals and total by using Classes. I have used classes CL_SALV_AGGREGATIONS (Method : add_aggregation) and CL_SALV_AGGREGATIONS (Method : add_sort) for sorting and doing subtotals. Output of my rep

  • Pendrive Not Working

    Sir, I have Purchased  16Gb Pendrive But It is not working right now So please Help me Through it Thank you