Database Logon Trigger Causing ORA-00604 ORA-16625 DGM-17017 (Doc ID 1963672.1)

Last updated on APRIL 18, 2017

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 9.2 to 12.1]
Information in this document applies to any platform.

Purpose is to point out that the FAL client (ARCn process) from a standby database logs on to the primary as username PUBLIC.
All sessions created by ARCn processes are username PUBLIC. Broker also uses PUBLIC.


Database Logon Trigger causing ORA-00604 ORA-16625 DGM-17017

Problem Description
Database Logon Trigger causing the following errors in Data Guard broker:-

Configuration Status:
ORA-00604: error occurred at recursive SQL level
ORA-16625: cannot reach database "CPRP_psin0p045"
DGM-17017: unable to determine configuration status

The standbys do not like the trigger and it is causing the communication problem.
CPRP_psin0p077 as an example

01/13/2015 09:25:23
>> Starting Data Guard Broker bootstrap <<
Broker Configuration File Locations:
  dg_broker_config_file1 = "+DATA01/cprp_psin0p077/drcprp1_psin4p788.dat"
  dg_broker_config_file2 = "+RECO01/cprp_psin0p077/drcprp2_psin4p788.dat"
01/13/2015 09:25:28
DMON Registering service CPRP_psin0p077_DGB with listener(s)
Broker Configuration: "cprp_dgb_config"
  Protection Mode: Maximum Performance
  Fast-Start Failover (FSFO): Disabled, flags=0x0, version=0
  Primary Database: CPRP_psin0p045 (0x01010000)
  Standby Database: CPRP_psin0p077, Enabled Physical Standby (0x02010000)
  Standby Database: CPRP_psin4p788, Enabled Physical Standby (0x03010000)
  Standby Database: CPRP_psin4p789, Enabled Physical Standby (0x04010000)
  Standby Database: CPRP_r2035192a141, Enabled Physical Standby (0x05010000)
01/13/2015 09:25:31
CPRP_psin0p077 version check successfully completed
CPRP_psin0p077 has current configuration metadata,
  completing bootstrap
Creating process RSM0
01/15/2015 10:10:24
Failed to connect to remote database CPRP_psin0p045. Error is ORA-00604
Failed to send message to site CPRP_psin0p045. Error code is ORA-00604.




 Added the trigger to allow listed users to log into the primary database


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms