No question at this time
DBA Top 10
1 A. Kavsek 8400
2 B. Vroman 5900
3 M. Cadot 5400
4 P. Wisse 4800
5 T. Boles 3700
6 J. Schnackenberg 2100
7 . Lauri 1500
8 R. Pattyn 700
9 T. P 600
9 J. PĂ©ran 600
About
DBA-Village
The DBA-Village forum
Forum as RSS
as RSS feed
Site Statistics
Ever registered users48407
Total active users1518
Act. users last 24h4
Act. users last hour1
Registered user hits last week254
Registered user hits last month927
Go up

Unable to get status of standby database using the broker
Next thread: Ora-1092 disconnection forced
Prev thread: Unable to get status of standby database using the broker

Message Score Author Date
Hi, I get the following errors when setting the...... Lauri Jul 30, 2019, 10:44
Hi, I have just found it. We use two ports for...... Lauri Jul 30, 2019, 11:41

Follow up by mail Click here


Subject: Unable to get status of standby database using the broker
Author: Lauri, Netherlands
Date: Jul 30, 2019, 10:44, 20 days ago
Os info: Linux x86-64
Oracle info: 12cR2
Error info: DGM-17016, ORA-16664
Message: Hi,

I get the following errors when setting the DataGuard broker, and chdecking the configuration of the standby database (for the primary database I do noet get an error):

Command:
show database verbose cen2pc1sby;

Error:
Databasestatus:
DGM-17016: Ophalen van status voor database "cen2pc1sby" is mislukt.
ORA-16664: Het resultaat van een lid kan niet worden ontvangen.


In the DataGuard broker log. I do not see more information than:

07/30/2019 09:15:39
Data Guard Broker Status Summary:
Type Name Severity Status
Configuration cen2pc1_dg_config Warning ORA-16607
Primary Database cen2pc1pri Success ORA-0
Physical Standby Database cen2pc1sby Error ORA-16664
07/30/2019 09:16:54
Data Guard Broker Status Summary:
...

Does someone know where I should investigate further?

Thanks by dvance for any tip.

Kind Regards
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here

Subject: Re-Unable to get status of standby database using the broker
Author: Lauri, Netherlands
Date: Jul 30, 2019, 11:41, 20 days ago
Message: Hi,

I have just found it.
We use two ports for the listener on both the primary and standby server.
One of the port is used through the application, the other one is used by the Broker
The port was wrong for the TNS name used to connect to the standby database through the Broker
After that, the apply redo logs didn't work correctly and I got these errors:
ORA-16766: 'Redo toepassen' is gestopt.
ORA-16854: De toe te passen vertraging kan niet worden vastgesteld.
ORA-16856: De transportvertraging kan niet worden vastgesteld.
I guess the Broker is able to handle it. But it didn't come put... I forced the recovery with recover managed standby database disconnect from session).
This it worked again.

Kind Regards
Your rating?: This reply is Good Excellent
Goto: Reply - Top of page 
If you think this item violates copyrights, please click here