PowerProtect Data Manager | Oracle discover fails with error Unable to connect to the database to verify the SID for '+APX1'
Summary: PowerProtect Data Manager (PPDM) Oracle discover fails with error: Unable to connect to the database to verify the SID for '+APX1'.
Symptoms
The following error appears in the agentsvc logs:
[2023-03-09 01:30:13,397 GMT| 2023-03-09 09:30:13,398094 +08| DBGAPPSYSTEMSDISCOVERY| PID-340891| TID-140464142354240| ERROR] JobManager/JobManager.py-runProcess()-Line 1054-
[2023-03-09 01:30:13,425 GMT| 2023-03-09 09:30:13,426377 +08| DBGAPPSYSTEMSDISCOVERY| PID-340891| TID-140464142354240| INFO] DataStore/SessionManager.py-insertErrors()-Line 161- record is {'status': 'FAILURE', 'operationType': 'APPLICATION_SYSTEM_DISCOVERY', 'error': {'errorOccurredTime': 1678325412, 'errorCode': 'ASDS0028', 'errorMessage':
'', 'alertArguments': [{'argumentName': 'AddOnName', 'argumentValue': 'ORACLE_DATABASE_SYSTEM'}, {'argumentName': 'hostName', 'argumentValue': 'exadbsp1r1-mgt.rhbgroup.com'}, {'argumentName': 'errors', 'argumentValue': "Unable to connect to the Oracle database ''\n\nUnable to connect to the database to verify the SID for '+APX1'.\n"}], 'vendorSpecificErrorMessage': ''}}
Cause
The SID '+APX1' is the Application Security Manager (ASM) proxy. PPDM does not support the ASM proxy.
Resolution
In version 19.12 and earlier versions, an extra step is required:
Put the SID '+APX1' into the exclude SID list in the $RMAN_AGENT_HOME/config/rman_agent.cfg file and fix the discovery issue.
Like: EXCLUDE_SID=+APX1
In version 19.13, this issue has been fixed that RMAN Agent 19.13, and later versions exclude the SID "+APX1" automatically.
Additional Information
If other SID is reported, check the Agent Service to see what SID has the discovery failure.
"Unable to connect to the Oracle database ''\n\n Unable to connect to the database to verify the SID for '+APX1'.\n\n Unable to connect to the database to verify the SID for 'TEST'.\n"
Run the ps -ef | grep pmon command to see what processes had been listed.
For the third line, some SIDs exist in the /etc/oratab file, but the Oracle Instance does not exist or does not start. It is required to double check those SIDs. If those SIDs are not needed anymore, then check if they can be removed from the /etc/oratab file.
If they are needed, those SIDs should be added in the $RMAN_AGENT_HOME/config/rman_agent.cfg file to EXCLUDE_SID:
EXCLUDE_SID=+APX1,TEST