Oracle database Discovery will exclude oratab configuration file lines that have comments on the end of the line - Known Error

Oracle database Discovery will exclude oratab configuration file lines that have comments on the end of the line Description When parsing the oratab configuration file, the "check ora home from oratab" and "failover check ora home from oratab for Solaris OS" steps of the "Oracle DB On Unix" Discovery and Service Mapping pattern removes any lines that have a number/hash/pound symbol (or hashtag if you are Gen Z): #

The steps' design assumes that the whole line is commented out. e.g.

# sales:/u01/app/oracle/sales:N But also wrongly removes active lines with comments on the end of the line. e.g.

sales:/u01/app/oracle/sales:N # line added by Agent This means the home folder is not correctly collected by the pattern, and everything after that goes wrong. We start relying on fallback steps to get the SID, which are not guaranteed to work either, and often divert attention away from this issue when investigating failed discoveries.

To be seeing that specific "# line added by Agent" text suggests "You are most likely using an ASM or 11.2 CRS-managed database (using the 11.2 Grid Infrastructure)" according to: https://support.oracle.com/knowledge/Oracle%20Database%20Products/1397813_1.html

Steps to Reproduce

Install 'Discovery and Service Mapping Patterns' 1.27.0 and 'Visibility Content' 6.23.0 Confirm the pattern contains the 'exclude_lines_pattern = "#"' code as part of step 'check ora home from oratab' and 'failover check ora home from oratab for Solaris OS' Run discovery on Linux or Solaris Server which has Oracle DB. Actual behaviour:

In the scenario where you can see on step 22 of the 'Oracle DB on Unix' pattern that it returns a line with '# line added by Agent' included, confirm the result is not included in the remaining steps on the pattern.

e.g. this would not be included in the result:

sales:/u01/app/oracle/sales:N # line added by Agent Expected behaviour:

Only if the whole line is commented out should the line be excluded.

Workaround This problem has no workaround, is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.

Manually removing the comments from the end of the lines in all the oratab files would avoid this problem. That might not be feasible, or might not work for long if management tools add the comments back again.

Customising the pattern to not exclude lines with # at all would cause deliberately commented out entries that should not be included to be included. Old/duplicate SIDs and Home folders that are wrong may then get used, and break the pattern and your data.