主库 orcl ， 副库：orcldg ,
datagurad 搭建成功，日志传输正常。
在 配置 datgurad broker 时，
DGMGRL> show configuration
Configuration - dgfxoptdb
Protection Mode: MaxPerformance
Databases:
orcl - Primary database
orcldg - Physical standby database
Error: ORA-16664: unable to receive the result from a database
Fast-Start Failover: DISABLED
Configuration Status:
ERROR
DGMGRL> show database orcl
Database - orcl
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
orcl
Database Status:
SUCCESS
DGMGRL> show database orcldg
Database - orcldg
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
orcl
Database Status:
DGM-17016: failed to retrieve status for database "orcldg"
ORA-16664: unable to receive the result from a database
查看主库的 drcorcl
报 ora - 16664
2017-02-28 02:49:32.727 01010000 1032426228 DMON: Entered rfm_get_chief_lock() for EDIT_RES_PROP, reason 0
2017-02-28 02:49:32.727 01010000 1032426228 DMON: chief lock convert for write op EDIT_RES_PROP
2017-02-28 02:49:32.728 01010000 1032426228 DMON: EDIT_RES_PROP: success
2017-02-28 02:49:32.728 01010000 1032426228 DMON: Evaluating critical status of standbys in configuration
2017-02-28 02:49:32.728 01010000 1032426228 DMON: Evaluating critical status of 0x02010000
2017-02-28 02:49:32.728 01010000 1032426228 ChangeCritical value is FALSE
2017-02-28 02:49:32.728 01010000 1032426228 IsCritical value is FALSE
2017-02-28 02:49:32.728 DMON: Updated Seq.MIV to 0.6, writing metadata to "/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/dr2orcl.dat"
2017-02-28 02:49:32.739 INSV: Received message for inter-instance publication
2017-02-28 02:49:32.740 req ID 1.1.1032426228, opcode EDIT_RES_PROP, phase RESYNCH, flags 8005
2017-02-28 02:49:32.740 INSV: Reply received for message with
2017-02-28 02:49:32.740 req ID 1.1.1032426228, opcode EDIT_RES_PROP, phase RESYNCH
2017-02-28 02:49:32.740 NSV1: (Seq.MIV = 0.6) Start sending metadata file: "/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/dr2orcl.dat"
2017-02-28 02:49:32.750 NSV1: Sending block #1 (containing Seq.MIV = 0.6), 3 blocks
2017-02-28 02:49:32.779 NSV1: (Seq.MIV = 0.6) End metadata file transmission: opcode EDIT_RES_PROP (1.1.1032426228)
2017-02-28 02:49:48.969 NSV1: Site orcldg returned ORA-16664.
2017-02-28 02:49:48.970 01010000 1032426228 DMON: Database orcldg returned ORA-16664
2017-02-28 02:49:48.970 01010000 1032426228 for opcode = EDIT_RES_PROP, phase = RESYNCH, req_id = 1.1.1032426228
2017-02-28 02:49:48.970 01010000 1032426228 DMON: Property dgconnectidentifier set to orcl for database orcl
2017-02-28 02:49:48.974 01010000 1032426228 DMON: Entered rfm_release_chief_lock() for EDIT_RES_PROP
2017-02-28 02:50:18.973 NSV1: Site orcldg returned ORA-16664.
2017-02-28 02:50:18.974 00000000 1032426229 DMON: Database orcldg returned ORA-16664
2017-02-28 02:50:18.974 00000000 1032426229 for opcode = HEALTH_CHECK, phase = BEGIN, req_id = 1.1.1032426229
_查看 副库的drcorcl:
一直报ORA-12514
"/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/dr2ORCLDG.dat"
2017-02-28 02:50:43.779 DRCX: Receiving block #1 (containing Seq.MIV = 0.6), 3 blocks
2017-02-28 02:50:43.806 DRCX: End receiving metadata file: opcode EDIT_RES_PROP (1.1.1032426228)
2017-02-28 02:50:43.819 DMON: Entered rfm_get_chief_lock() for EDIT_RES_PROP, reason 1
2017-02-28 02:50:43.820 00000000 1032426228 DMON: chief lock convert for metadata resynchronization
2017-02-28 02:50:43.820 INSV: Received message for inter-instance publication
2017-02-28 02:50:43.822 req ID 1.1.1032426228, opcode EDIT_RES_PROP, phase RESYNCH, flags 8005
2017-02-28 02:50:43.822 00000000 1032426228 DMON: status from posting standby instances for RESYNCH = ORA-00000
2017-02-28 02:50:43.822 DMON: Metadata available (1.1.1032426228), loading from "/oracle/app/oracle/product/11.2.0/dbhome_1/dbs/dr2ORCLDG.dat"
2017-02-28 02:50:43.823 Executing SQL [ALTER SYSTEM REGISTER]
2017-02-28 02:50:43.826 SQL [ALTER SYSTEM REGISTER] Executed successfully
2017-02-28 02:50:43.832 DMON: ...committing load to memory, Seq.MIV = 0.6
2017-02-28 02:50:43.843 Executing SQL [ALTER SYSTEM SET fal_server='orcl']
2017-02-28 02:50:43.854 SQL [ALTER SYSTEM SET fal_server='orcl'] Executed successfully
2017-02-28 02:50:43.854 DMON: Messaged RSM0 to reset FAL
2017-02-28 02:50:43.855 DMON: Checking critical status of this database.
2017-02-28 02:50:43.855 INSV: Reply received for message with
2017-02-28 02:50:43.855 req ID 1.1.1032426228, opcode EDIT_RES_PROP, phase RESYNCH
2017-02-28 02:50:43.856 00000000 1032426228 DMON: Entered rfm_release_chief_lock() for EDIT_RES_PROP
2017-02-28 02:50:43.914 NSV0: Failed to connect to remote database orcl. Error is ORA-12514
2017-02-28 02:50:43.914 NSV0: Failed to send message to site orcl. Error code is ORA-12514.
2017-02-28 02:50:43.914 DMON: Database orcl returned ORA-12514
2017-02-28 02:50:43.915 for opcode = EDIT_RES_PROP, phase = RESYNCH, req_id = 1.1.1032426228
2017-02-28 02:51:00.031 drcx: could not find task req_id=1.1.1032426228 for PROBE.
2017-02-28 02:51:00.145 NSV0: Failed to connect to remote database orcl. Error is ORA-12514
2017-02-28 02:51:00.145 NSV0: Failed to send message to site orcl. Error code is ORA-12514.
2017-02-28 02:51:00.145 DMON: Database orcl returned ORA-12514
2017-02-28 02:51:00.146 for opcode = HEALTH_CHECK, phase = BEGIN, req_id = 1.1.1032426229
2017-02-28 02:51:30.104 drcx: could not find task req_id=1.1.1032426229 for PROBE.
主库的 listener.ora
SID_LIST_LISTENER=
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = orcl)
(ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = orcl)
)
(SID_DESC =
(GLOBAL_DBNAME = orcl_DGMGRL)
(ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = orcl)
)
)
副库的 listener.ora
SID_LIST_LISTENER=
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = orcldg)
(ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = orcl)
)
(SID_DESC =
(GLOBAL_DBNAME = orcldg_DGMGRL)
(ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = orcl)
)
)
主库监听的状态：
Services Summary...
Service "orcl" has 2 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orclXDB" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orcl_DGB" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orcl_DGMGRL" has 1 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
副库的监听状态：
Services Summary...
Service "ORCLDG_DGB" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orcldg" has 2 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orcldg_DGMGRL" has 1 instance(s).
Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
