Skip to main content

Oracle DTC Database discovery failure alerts received after Oracle server upgrade

Updated over a week ago

Problem description

Oracle Database discovery failure alerts are received post Oracle server upgrade

Cause

During discovery Oracle agent scans all OracleHome locations. After Oracle upgrade there will be multiple OracleHome directories on the server

Traceback

/var/log/PhoenixOracle/main_oracle_service.log shows 
level=info ts=2023-07-18T03:00:36.782654824-05:00 filename=shallowdiscovery.go:45 message="Instance Info" InstanceSID=TestDB OracleHome=/sw/19.0.0/dbhome_1 OracleUser=oracle DBName=Test IsRac=false
level=warn ts=2023-07-18T03:00:41.651124726-05:00 filename=deepdiscovery.go:200 message="Failed to do DEEP discovery of database." OracleSid=TestDB OracleHome=/sw/12201/db DbExists=true

Resolution

  1. As can be seen in above traceback database TestDB is listed under two OracleHome directories

  2. Where /sw/12201/db is the old OracleHome path for version 12c and /sw/19.0.0/dbhome_1 is the new OracleHome path for version 19

To exclude the old OracleHome path from discovery, follow below steps:

For the agent version prior to 7.0.0
a. Stop Oracle DTC agent service:
service PhoenixOracle stop

b. Edit the file '/etc/PhoenixOracle/Phoenix.yml' and add the below entry:
EXCLUDE_ORACLE_HOME_FROM_DISCOVERY: ["/sw/12201/db"]

c. Start Oracle DTC agent service:
service PhoenixOracle start

For agent version 7.0.0 and later
a. Stop Oracle DTC agent service:
service Druva-EnterpriseWorkloads stop

b. Edit the file '/etc/Druva/EnterpriseWorkloads/oracle/OraclePlugin.yml' and add the below entry:
exclude_oracle_home_from_discovery: ["/sw/12201/db"]

c. Start Oracle DTC agent service:
service Druva-EnterpriseWorkloads start

Note: The Parameter is case sensitive; please use the exact format according to the agent version.

Did this answer your question?