March 23, 2020
ORACLE
When querying the status of the configuration from broker, errors like below were seen.
Warning: ORA-16664: unable to receive the result from a database
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 |
DGMGRL> show configuration Configuration — DRSolution Protection Mode: MaxPerformance Members: physical — Primary database physclFS — Far sync instance Warning: ORA—16664: unable to receive the result from a database primary — Logical standby database Error: ORA—16664: unable to receive the result from a database snapshot — Physical standby database Error: ORA—16664: unable to receive the result from a database logical — Logical standby database Error: ORA—16664: unable to receive the result from a database logical2 — Physical standby database Error: ORA—16664: unable to receive the result from a database Members Not Receiving Redo: prmyFS — Far sync instance Warning: ORA—16664: unable to receive the result from a database Fast—Start Failover: DISABLED Configuration Status: ERROR (status updated 38 seconds ago) |
Standby databases also receive connection errors as below.
Fatal NI connect error 12526, connecting to:
Fatal NI connect error 12526, connecting to: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=172.20.42.62)(PORT=1521)(SEND_BUF_SIZE=10485760)(RECV_BUF_SIZE=10485760)))(SDU=65535)(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=physical_DGB)(INSTANCE_NAME=physical)(CID=(PROGRAM=oracle)(HOST=physclFS.tivibulab.local)(USER=oracle)))) VERSION INFORMATION: TNS for Linux: Version 12.1.0.2.0 — Production TCP/IP NT Protocol Adapter for Linux: Version 12.1.0.2.0 — Production Time: 18—APR—2017 08:51:11 Tracing not turned on. Tns error struct: ns main err code: 12564 TNS—12564: TNS:connection refused ns secondary err code: 0 nt main err code: 0 nt secondary err code: 0 nt OS err code: 0 |
SOLUTION
We can fix the problem by following the steps below.
Step1:
Since the TNS problem appears, it is first checked whether the TNSNAMES.ora and Listener.ora files are working. Test access to Standby from Physical database with sqlplus. As you can see below, only one database connection is seen.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
[oracle@physical ~]$ sqlplus sys/Passw0rd4@logical2 as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Tue Apr 18 08:33:19 2017 Copyright (c) 1982, 2014, Oracle. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 — 64bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options Session altered. [Physical — 18—04—2017 08:33:19] SQL> show parameter name NAME TYPE VALUE —————————————————— —————— ——————————————— cell_offloadgroup_name string db_file_name_convert string primary, logical2 db_name string LOGICAL2 db_unique_name string logical2 global_names boolean FALSE instance_name string logical2 lock_name_space string log_file_name_convert string primary, logical2 pdb_file_name_convert string processor_group_name string service_names string logical2 |
Step2:
Try tnsping. As you can see below, only one database connection is seen.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 |
[oracle@physclFS ~]$ tnsping logical2 5 TNS Ping Utility for Linux: Version 12.1.0.2.0 — Production on 18—APR—2017 08:35:19 Copyright (c) 1997, 2014, Oracle. All rights reserved. Used parameter files: /u01/app/oracle/product/12.1.0/db_1/network/admin/sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = 172.20.42.42)(PORT = 1521)(SEND_BUF_SIZE = 10485760)(RECV_BUF_SIZE = 10485760))) (SDU = 65535) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = logical2))) OK (20 msec) OK (0 msec) OK (0 msec) OK (0 msec) OK (0 msec) |
Step3:
Check Listener on all DBs in configurations. We have seen that there is something odd only in the Primary database “Physical”.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 |
[oracle@physical ~]$ lsnrctl LSNRCTL for Linux: Version 12.1.0.2.0 — Production on 18—APR—2017 08:36:31 Copyright (c) 1991, 2014, Oracle. All rights reserved. Welcome to LSNRCTL, type «help» for information. LSNRCTL> status Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=physical.tivibulab.local)(PORT=1521)(SEND_BUF_SIZE=10485760)(RECV_BUF_SIZE=10485760))) STATUS of the LISTENER ———————————— Alias LISTENER Version TNSLSNR for Linux: Version 12.1.0.2.0 — Production Start Date 03—MAR—2017 08:31:16 Uptime 45 days 23 hr. 5 min. 17 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Listener Parameter File /u01/app/oracle/product/12.1.0/db_1/network/admin/listener.ora Listener Log File /u01/app/oracle/diag/tnslsnr/physical/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=physical.tivibulab.local)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=physical.tivibulab.local)(PORT=5500))(Security=(my_wallet_directory=/u01/app/oracle/admin/physical/xdb_wallet))(Presentation=HTTP)(Session=RAW)) Services Summary... Service «physical» has 2 instance(s). Instance «physical», status UNKNOWN, has 1 handler(s) for this service... Instance «physical», status RESTRICTED, has 1 handler(s) for this service... Service «physicalXDB» has 1 instance(s). Instance «physical», status RESTRICTED, has 1 handler(s) for this service... Service «physical_DGB» has 1 instance(s). Instance «physical», status RESTRICTED, has 1 handler(s) for this service... Service «physical_DGMGRL» has 1 instance(s). Instance «physical», status UNKNOWN, has 1 handler(s) for this service... The command completed successfully |
Step4:
In this case, I suspect that the Primary database was opened in RESTRICT mode. We do the necessary checks.
[Physical — 18—04—2017 08:49:54] SQL> select logins from v$instance; LOGINS ————— RESTRICTED |
Step5:
Disable RESTRICT mode.
[Physical — 18—04—2017 08:43:34] SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION; System altered. |
Step6:
Check listener again.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 |
[oracle@physical ~]$ lsnrctl LSNRCTL for Linux: Version 12.1.0.2.0 — Production on 18—APR—2017 08:45:44 Copyright (c) 1991, 2014, Oracle. All rights reserved. Welcome to LSNRCTL, type «help» for information. LSNRCTL> status Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=physical.tivibulab.local)(PORT=1521)(SEND_BUF_SIZE=10485760)(RECV_BUF_SIZE=10485760))) STATUS of the LISTENER ———————————— Alias LISTENER Version TNSLSNR for Linux: Version 12.1.0.2.0 — Production Start Date 03—MAR—2017 08:31:16 Uptime 45 days 23 hr. 14 min. 30 sec Trace Level off Security ON: Local OS Authentication SNMP OFF Listener Parameter File /u01/app/oracle/product/12.1.0/db_1/network/admin/listener.ora Listener Log File /u01/app/oracle/diag/tnslsnr/physical/listener/alert/log.xml Listening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=physical.tivibulab.local)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=physical.tivibulab.local)(PORT=5500))(Security=(my_wallet_directory=/u01/app/oracle/admin/physical/xdb_wallet))(Presentation=HTTP)(Session=RAW)) Services Summary... Service «physical» has 2 instance(s). Instance «physical», status UNKNOWN, has 1 handler(s) for this service... Instance «physical», status READY, has 1 handler(s) for this service... Service «physicalXDB» has 1 instance(s). Instance «physical», status READY, has 1 handler(s) for this service... Service «physical_DGB» has 1 instance(s). Instance «physical», status READY, has 1 handler(s) for this service... Service «physical_DGMGRL» has 1 instance(s). Instance «physical», status UNKNOWN, has 1 handler(s) for this service... The command completed successfully |
Step7:
Check the configuration status.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
DGMGRL> show configuration Configuration — DRSolution Protection Mode: MaxPerformance Members: physical — Primary database physclFS — Far sync instance primary — Logical standby database snapshot — Physical standby database logical — Logical standby database logical2 — Physical standby database Members Not Receiving Redo: prmyFS — Far sync instance Fast—Start Failover: DISABLED Configuration Status: SUCCESS (status updated 36 seconds ago) |
May 24, 2021
I got ” ORA-16664: unable to receive the result from a database ” error in Oracle database.
ORA-16664: unable to receive the result from a database
Details of error are as follows.
ORA-16664: unable to receive the result from a database Cause: During execution of a command, a database in the Data Guard broker configuration failed to return a result. Action: Check the Data Guard broker logs for the details of the failure. Ensure network communication is working properly amongst the members of the configuration. Fix any possible network problems and reissue the command.
unable to receive the result from a database
This ORA-16664 error is related to the execution of a command, a database in the Data Guard broker configuration
failed to return a result.
Check the Data Guard broker logs for the details of the failure. Ensure network communication is working properly amongst the members of the configuration. Fix any possible network problems and reissue the command.
<< Primary DRC log >>
DG 2010-09-28-13:44:56 0 2 809851344 for opcode = CTL_GET_STATUS, phase = BEGIN, req_id = 1.1.809851344 DG 2010-09-28-13:46:11 0 2 0 NSV1: Received error ORA-16664 from target remote site hrstdby. <<<<<<<<<<<<<<< ORA-16664 DG 2010-09-28-13:46:11 0 2 809851345 DMON: Database hrstdby returned ORA-16664 << Standby DRC log >>
DG 2010-09-15-19:44:49 0 2 809835872 Operation CTL_GET_STATUS continuing with warning, status = ORA-16792 DG 2010-09-15-19:44:49 0 2 809835872 Operation CTL_GET_STATUS continuing with warning, status = ORA-16792 DG 2010-09-15-19:44:49 0 2 0 NSV0: Failed to connect to remote database hrprod. Error is ORA-12514 <<<<<<<<<<<<<<< ORA-12514 DG 2010-09-15-19:44:49 0 2 0 NSV0: Failed to send message to site hrprod. Error code is ORA-12514. DG 2010-09-15-19:44:49 0 2 0 DMON: Database hrprod returned ORA-12514 <strong>CAUSE</strong>
DGMGRL>show database 'standby' InconsistentProperties;
Check the non default port used in connect string of both primary and standby(tnsnames.ora).
<strong>SOLUTION</strong>
CASE: 1
1. Changes on database level,
If non default port is used for DG transport then make sure we have a local_listener or LISTENER_NETWORKS setting to reflect the correct listener.
SQL> alter system set local_listener='<value which is LocalListenerAddress>'; Ex, SQL> alter system set local_listener='(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=North_Sales)(PORT=<port#>)))';
2. Changes on DG Broker Configuration,
Check the listener services mentioned in the DG broker configuration exisit on the lsnrctl status. If service mismatch either modify the listener.ora or the DG broker configuration as expplained below
In 10G,
DGMGRL> edit database <standby> set property LocalListenerAddress='<Listener address>'; In 11G, DGMGRL> edit database <standby> set property StaticConnectIdentifier='<Static Address>'; For example,
DGMGRL> edit database <standby> set property StaticConnectIdentifier='(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=North_Sales)(PORT=<port#>))(CONNECT_DATA=(SERVICE_NAME=North_Sales_DGMGRL.example.com)(INSTANCE_NAME=north_sales1)(SERVER=DEDICATED)))';
CASE: 1
1. Issue explained on DG Admin guide,
Refer to http://docs.oracle.com/cd/B28359_01/server.111/b28294/create_ps.htm#i66205 , it contains the complete steps to manually create the standby when the Primary is using database encryption wallet
2. If wallet is used then Copy the primary database encryption wallet to the standby database system.If the primary database has a database encryption wallet, copy it to the standby database system and configure the standby database to use this wallet.
Note: The database encryption wallet must be copied from the primary database system to each standby database system whenever the master encryption key is updated.
Encrypted data in a standby database cannot be accessed unless the standby database is configured to point to a database encryption wallet or hardware security module that contains the current master encryption key from the primary database.
II. ORA-16664 along with ORA-00604
Data Guard Broker switchover fails with an ORA-16664 and the standby DRC log shows an ORA-604.
DGMGRL> switchover to '<stdby>'; Performing switchover NOW, please wait... Error: ORA-16664: unable to receive the result from a database Failed. Unable to switchover, primary database is still "MYDB_021
DRC log : Data Guard Broker log:
2013-02-12 19:55:23.107 SQL [ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WAIT WITH SESSION SHUTDOWN] Executed successfully 2013-02-12 19:55:23.107 Database Resource SetState succeeded 2013-02-12 19:55:23.108 INSV: Reply received for message with 2013-02-12 19:55:23.108 req ID 1.1.1457631131, opcode CTL_SWITCH, phase TEARDOWN 2013-02-12 19:55:23.108 02001000 1457631131 DMON: Entered rfm_release_chief_lock() for CTL_SWITCH 2013-02-12 19:55:26.591 NSV0: Failed to connect to remote database MFXPRD_xstmc021. Error is ORA-00604 2013-02-12 19:55:26.592 NSV0: Failed to send message to site MYDB_021. Error code is ORA-00604. 2013-02-12 19:55:26.592 02001000 1457631131 DMON: Database MYDB_021 returned ORA-00604 2013-02-12 19:55:26.592 02001000 1457631131 for opcode = CTL_SWITCH, phase = TEARDOWN, req_id = 1.1.1457631131
CAUSE
Check for the logon trigger
SQL> select owner, trigger_name, trigger_type, triggering_event from all_triggers where triggering_event like '%LOGON%' or triggering_event like '%STARTUP%' or triggering_event like '%SHUTDOWN%';
A logon trigger was created in the primary database.
SOLUTION
Disable the logon trigger and then perform a switchover.
III. ORA-16664 with ORA-01031 passwordfile issue
ORA-16664 will report, even for passwordfile issue on standby.
DGMGRL> show configuration; Configuration - DG Protection Mode: MaxPerformance Databases: BOSTON - Primary database stdby - Physical standby database logstdby - Logical standby database Error: ORA-16664: unable to receive the result from a database Fast-Start Failover: DISABLED Configuration Status: ERROR
— —Primary DRC log—-
2012-01-02 13:46:06.850 req ID 1.1.973032160, opcode DEL_RES, phase NULL 2012-01-02 13:46:15.798 NSV2: Initialization of connection failed. 2012-01-02 13:46:15.801 NSV2: expected destination db_unique_name is chicago 2012-01-02 13:46:15.802 NSV2: database actually reached LOGSTDBY 2012-01-02 13:46:15.803 NSV2: Failed to send message to site chicago. Error code is ORA-16642. 2012-01-02 13:46:15.804 03000000 973032160 DMON: Database chicago returned ORA-16642 2012-01-02 13:46:15.805 03000000 973032160 for opcode = DEL_RES, phase = NULL, req_id = 1.1.973032160 2012-01-02 13:46:23.670 NSV2: Initialization of connection failed. 2012-01-02 13:46:23.673 NSV2: expected destination db_unique_name is chicago 2012-01-02 13:46:23.675 NSV2: database actually reached LOGSTDBY 2012-01-02 13:46:23.677 NSV2: Failed to send message to site chicago. Error code is ORA-16642. 2012-01-02 13:46:23.678 03000000 973032160 DMON: Database chicago returned ORA-16642
——-Standby DRC log —————-
2012-01-03 13:51:24.902 Connection to database BOSTON returns ORA-01031. 2012-01-03 13:51:24.903 Please check database BOSTON is using a remote password file, 2012-01-03 13:51:24.904 its remote_login_passwordfile is set to SHARED or EXCLUSIVE, 2012-01-03 13:51:24.905 and the SYS password is the same as this database. 2012-01-03 13:51:24.905 NSV0: Failed to connect to remote database BOSTON. Error is ORA-01031 2012-01-03 13:51:24.906 NSV0: Failed to send message to site BOSTON. Error code is ORA-01031.
CAUSE
Passwordfile mismatch
SOLUTION
1. Verify primary tnsnames.ora whether the connect identifier for standby database is correct and you are able to tnsping and connect using sqlplus as sysdba.
2. Make sure passwordfile is present on all nodes of rimary and all nodes of standby database.
ref : Troubleshooting ORA-16191 and ORA-1017/ORA-1031 in Data Guard Log Transport Services or Data Guard Broker (Doc ID 1368170.1)
3. Verify configuration using DGMGRL>show configuration
IV. ORA-16664 and ORA-16501
In 12.1.0.2, Broker commands are failing with the Error ORA-16664.
Broker logs reports the below Errors:
Primary Broker logs:
NSV1: Unable to obtain a connect descriptor to member <standby db_unique_name>, ORA-16501) NSV1: Failed to connect to member <standby db_unique_name> NSV1: Failed to send message to site <standby db_unique_name>. Error code is ORA-16501. DMON: Database <standby db_unique_name> returned ORA-16501
Standby Broker logs:
NSV0: Unable to obtain a connect descriptor to member <Primary db_unique_name>, ORA-16501) NSV0: Failed to connect to member <Primary db_unique_name> NSV0: Failed to send message to site <Primary db_unique_name>. Error code is ORA-16501. DMON: Database <Primary db_unique_name> returned ORA-16501
SQLPLUS connectivity from Primary to Standby and Standby to Primary using the ‘DGConnectIdentifier’ does Not report Any Errors
CAUSE
Unpublished Bug 21756401 – BROKER DOES NOT HANDLE DESCRIPTION_LIST and it is fixed in 12.2
Broker cannot connect to other databases when a connect description to which theDGConnectIdentifier property points contains “DESCRIPTION_LIST”.
SOLUTION
Workaround: Change the connect identifier that DGConnectIdentifier points to to a connect descriptor that contains only 1 DESCRIPTION without DESCRIPTION_LIST.
If the Workaround is Not feasible get the Patch for the Bug 21756401
NOTE : If the above mentioned scenarios didn’t help, please enable trace on standby (restart standby) and check with Support,
event = "16664 trace name errorstack forever, level 3"
Do you want to learn Oracle Database for Beginners, then read the following articles.
Oracle Tutorial | Oracle Database Tutorials for Beginners ( Junior Oracle DBA )
2,112 views last month, 1 views today
About Mehmet Salih Deveci
I am Founder of SysDBASoft IT and IT Tutorial and Certified Expert about Oracle & SQL Server database, Goldengate, Exadata Machine, Oracle Database Appliance administrator with 10+years experience.I have OCA, OCP, OCE RAC Expert Certificates I have worked 100+ Banking, Insurance, Finance, Telco and etc. clients as a Consultant, Insource or Outsource.I have done 200+ Operations in this clients such as Exadata Installation & PoC & Migration & Upgrade, Oracle & SQL Server Database Upgrade, Oracle RAC Installation, SQL Server AlwaysOn Installation, Database Migration, Disaster Recovery, Backup Restore, Performance Tuning, Periodic Healthchecks.I have done 2000+ Table replication with Goldengate or SQL Server Replication tool for DWH Databases in many clients.If you need Oracle DBA, SQL Server DBA, APPS DBA, Exadata, Goldengate, EBS Consultancy and Training you can send my email adress [email protected].- -Oracle DBA, SQL Server DBA, APPS DBA, Exadata, Goldengate, EBS ve linux Danışmanlık ve Eğitim için [email protected] a mail atabilirsiniz.
setup
during switchover it didn’t show any error
DGMGRL> switchover to 'TROY_DR'
Performing switchover NOW, please wait...
New primary database "TROY_DR" is opening...
Operation requires shutdown of instance "TROY1" on database "TROY"
Shutting down instance "TROY1"...
ORACLE instance shut down.
Operation requires startup of instance "TROY1" on database "TROY"
Starting instance "TROY1"...
ORACLE instance started.
Database mounted.
Database opened.
Switchover succeeded, new primary is "TROY_DR"
but when i checked configuration again it shows below error
DGMGRL> show configuration
Configuration - broker_config
Protection Mode: MaxPerformance
Databases:
TROY_DR - Primary database
Error: ORA-16810: multiple errors or warnings detected for the database
TROY - Physical standby database
Error: ORA-16664: unable to receive the result from a database
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
when i checked new standby database i found that one instance on standby was not started
[oracle@ol6-112-rac2 trace]$ /u01/app/11.2.0.3/grid/bin/crsctl stat res -t
.............
ora.troy.db
1 ONLINE ONLINE ol6-112-rac1 Open,Readonly
2 OFFLINE OFFLINE Instance Shutdown
so started it manually
[oracle@ol6-112-rac2 trace]$ srvctl start instance -d troy -i TROY2
[oracle@ol6-112-rac2 trace]$ /u01/app/11.2.0.3/grid/bin/crsctl stat res -t
.......
ora.troy.db
1 ONLINE ONLINE ol6-112-rac1 Open,Readonly
2 ONLINE ONLINE ol6-112-rac2 Open,Readonly
but after that issue still persist
DGMGRL> show configuration
Configuration - broker_config
Protection Mode: MaxPerformance
Databases:
TROY_DR - Primary database
TROY - Physical standby database
Error: ORA-16664: unable to receive the result from a database
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
But atleast now i can see it is working from standby side
[oracle@ol6-112-rac1 trace]$ dgmgrl
DGMGRL for Linux: Version 11.2.0.3.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/oracle@TROY
Connected.
DGMGRL> show configuration
Configuration - broker_config
Protection Mode: MaxPerformance
Databases:
TROY_DR - Primary database
TROY - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
drcSID.log shows
Data Guard Broker Status Summary:
Type Name Severity Status
Configuration broker_config Warning ORA-16607
Primary Database TROY_DR Success ORA-00000
Physical Standby Database TROY Error ORA-16664
so stop and start standby database (mrp starts automatically)
[oracle@ol6-112-rac1 trace]$ srvctl stop database -d TROY -o immediate
[oracle@ol6-112-rac1 trace]$ srvctl start database -d TROY
[oracle@ol6-112-rac1 trace]$ ps -ef|grep mrp
oracle 31112 1 0 20:58 ? 00:00:00 ora_mrp0_TROY1
oracle 31188 19562 0 20:58 pts/0 00:00:00 grep mrp
now its working fine from both sides
[oracle@ol6-112-dr-rac1 admin]$ dgmgrl
DGMGRL for Linux: Version 11.2.0.3.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/oracle@TROY_DR
Connected.
DGMGRL> show configuration
Configuration - broker_config
Protection Mode: MaxPerformance
Databases:
TROY_DR - Primary database
TROY - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
[oracle@ol6-112-rac1 trace]$ dgmgrl
DGMGRL for Linux: Version 11.2.0.3.0 - 64bit Production
Copyright (c) 2000, 2009, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/oracle@TROY
Connected.
DGMGRL> show configuration
Configuration - broker_config
Protection Mode: MaxPerformance
Databases:
TROY_DR - Primary database
TROY - Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS