Oracle Database, DB Instance and Server Relationship is not setting via discovery - Support and Troubleshooting

Oracle Database, DB Instance and Server Relationship is not setting via discovery Issue The relationship between Database, DB Instance and Server is not setting via Discovery for Oracle

As per below documentation following relationships should be created between Oracle DB, Instance and the related servers

Oracle Listener HD discovery

https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/service-mapping/reference/oracle-listener-hd-discovery.html

cmdb_ci_db_ora_instance “Uses :: Used by” cmdb_ci_db_oracle_database cmdb_ci_db_ora_instance “Runs on :: Runs” Linux, AIX, HPUS or Solaris Server Cause Cause 1:

We could see below error in Oracle discovery of server for pattern 'Oracle Listener HD'

"Failed Exploring CI Pattern, Pattern name: Oracle Listener HD" for 'Oracle Listener HD' pattern against 'xxxx/xxxx'

Following errors can be seen in pattern 'Oracle Listener HD' log;

{ "className": "cmdb_ci_db_ora_instance", "operation": "INSERT_AS_INCOMPLETE", "sysId": "Unknown", "identifierEntrySysId": "Unknown", "errors": [ { " error": "MISSING_MATCHING_ATTRIBUTES", "message": "In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_db_ora_instance]. Add these input values in payload item

The reason for this could be following identifier 'Oracle DB' is customised.

https://instance-name.service-now.com/nav_to.do?uri=cmdb_identifier.do?sys_id=90ec6ab3ff100200ab8fffffffffffa9

Cause 2:

'Oracle Listener HD' pattern failing to run command 'lsnrctl status LISTENER_NAME' on steps ''Run listener command' or 'Run listener command failover'

**Please note in 'lsnrctl status LISTENER_NAME' the 'LISTENER_NAME' would vary according to the processes 'Process ID' in each launched pattern in the discovery.

Resolution Solution for cause-1 :

Make sure following 'Oracle DB' identifier is OOB as per below screenshot. https://instance-name.service-now.com/nav_to.do?uri=cmdb_identifier.do?sys_id=90ec6ab3ff100200ab8fffffffffffa9

OOB configuration for identifier 'Oracle DB' should be as below:

Solution for cause-2 :

So, in above steps 'lsnrctl' command failing to get status for listener. You should copy whole failed command from above pattern logs and give it to your Oracle admin team and check with them see why it is failing. Example command should be given to oracle admin team (Note it will vary for your case, you should copy it from the pattern logs as shown in above screenshot):

"export XXX_ADMIN=/grid/app/19.3.0.0/grid/network/admin;export ORACLE_BASE=/grid/app/19.3.0.0/grid;export ORACLE_HOME=/grid/app/19.3.0.0/grid;/grid/app/19.3.0.0/grid/bin/lsnrctl status LISTENER_NAME"

Also check 'Prerequisites' section of 'Oracle Listener HD discovery' document, where all required commands are given for successful discovery. ***note: Also its mentioned in below doc that "Ensure that the Discovery User is in the Oracle DBA group or has the correct Permissions." https://docs.servicenow.com/bundle/vancouver-it-operations-management/page/product/service-mapping/reference/oracle-listener-hd-discovery.html