Identification attributes for class cmdb_ci_cluster are not populated (ID and Name) causing the Linux Server Pattern to fail - Known Error

Identification attributes for class cmdb_ci_cluster are not populated (ID and Name) causing the Linux Server Pattern to fail Description The Linux Server discovery pattern will fail when Oracle Clusterware is installed due to Oracle commands not being found.

Steps to Reproduce

Execute discovery against a Linux Server where Oracle Clusterware is installed. Ensure the Oracle Clusterware installation home is the Grid Home - different than the standard ORACLE_HOME . Navigate to the extension section "UNIX Cluster - ORACLE Clusterware" and observe remote Oracle commands are failing with " No such file or directory " or " command not found " when ORACLE_HOME is used instead of Grid Home . Observe that Identifier attributes for CI type "cmdb_ci_unix_cluster" - Cluster ID and Name are not collected, which leads to " Commit was not attempted due to other errors " during identification which causes the Linux Server pattern to fail. Example errors seen in the Horizontal Discover Log:

In the " Set Oracle CRS cluster name " section: 2022-09-12 15:47:08: Executing SSH command: /u01/app/oracle/product/18.0.0.0/dbhome_1/bin/olsnodes -c | egrep -vi 'error|return code|DIA|Additional' 2022-09-12 15:47:08: Command result: ksh: /u01/app/oracle/product/18.0.0.0/dbhome_1/bin/olsnodes: not found 2. In the " Populate ORACLE CRS Cluster ID " section: 2022-09-12 15:47:08: Executing SSH command: sudo /u01/app/oracle/product/18.0.0.0/dbhome_1/bin/ocrcheck | egrep -vi 'error|return code|DIA|Additional' 2022-09-12 15:47:08: Command result: ksh: /u01/app/oracle/product/18.0.0.0/dbhome_1/bin/ocrcheck: not found 2022-09-12 15:47:08: Command failed with status 1 Workaround Please import the attached XML file: sa_pattern_604aba37db1c1300b2c451035e9619ea.xml

Then open pattern UNIX Cluster - ORACLE Clusterware and click on the link " Synchronize with MID Servers ".