My Oracle Support Banner

ORA-03170 While Running Queries On Active Data Guard Database (Doc ID 2548509.1)

Last updated on DECEMBER 09, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the
Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material. Any similarity to actual
environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Primary Database: dgx121
Standby Database: dgx121b

**********

DGMGRL> show configuration

Configuration - The SUPER cluster

Protection Mode: MaxPerformance
Members:
dgx121 - Primary database
dgx121b - Physical standby database
Error: ORA-16662: network timeout when contacting a database

Fast-Start Failover: DISABLED

Configuration Status:
ERROR (status updated 428 seconds ago)

Primary DRC log,

2019-05-14 22:01:20.754 RSM0: Received Get Status Request: rid=0x01041001, sid=1
2019-05-14 22:01:20.755 00001000 721722595 DMON: Primary Instance completed health check
2019-05-14 22:01:20.755 INSV: Reply received for message with
2019-05-14 22:01:20.755 req ID 1.1.721722595, opcode HEALTH_CHECK, phase BEGIN
2019-05-14 22:01:20.756 DMON: After H/C aggregation, db 0x01001000 has severity=0, status=0
2019-05-14 22:01:21.466 NSV1: Failed to connect to remote database dgx121b. Error is ORA-12514. Connect descriptor used is (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)
(HOST=<host name>)(PORT=<port id>)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=dgx121b_DGB.<host name>))).
2019-05-14 22:01:21.467 NSV1: Try to connect to database dgx121b alternatively using its initial connect descriptor dg2tns
2019-05-14 22:01:22.001 NSV1: New connection to site 2, timeout=0 secs
2019-05-14 22:01:46.446 DMON: publishing message #13, site=2, target=NSV1, cmd=6 <1/1>
2019-05-14 22:11:46.846 00001000 721722595 DMON: Data Guard Broker terminating NSV1, timed out waiting for a response from database dgx121b
2019-05-14 22:11:46.846 DMON: Kill NSVs for site=2
2019-05-14 22:11:46.846 DMON: Dumping NSV1 stack trace, pid=120050.
2019-05-14 22:11:47.846 00001000 721722595 DMON: Database dgx121b returned ORA-16662
2019-05-14 22:11:47.846 00001000 721722595 for opcode = HEALTH_CHECK, phase = BEGIN, req_id = 1.1.721722595
2019-05-14 22:11:47.846 00001000 721722595 DMON: Primary completed health check
2019-05-14 22:11:47.846 00001000 721722595 DMON: Entered rfm_release_chief_lock() for HEALTH_CHECK
2019-05-14 22:11:47.846 DMON: Data Guard Broker Status Summary:
2019-05-14 22:11:47.847 DMON: Type Name Severity Status
2019-05-14 22:11:47.847 DMON: Configuration The SUPER cluster Warning ORA-16607
2019-05-14 22:11:47.847 DMON: Primary Database dgx121 Success ORA-00000
2019-05-14 22:11:47.847 DMON: Physical Standby Database dgx121b Error ORA-16662

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.