• Loading...

Oracle Database Installed Options

Oracle Database Installed Options via Query

The pattern executes an SQL Query against the Database, unless this option has been disabled in the pattern configuration which returns a list of all Options and their Installed/Uninstalled status.

SQL Query executed to retrieve Installed Options: select parameter, value from v$option order by 1

If the SQL query is successful, the pattern compares the results against a user configured list of installed options to search for.

Note:The database query to Oracle Database Server will only run if the extended_sql_discovery option is enabled in the Oracle Database pattern configuration section. It is enabled by default

The installed options searched for by default are:

  • OLAP
  • Partitioning
  • Real Application Clusters
  • Parallel Server
  • Advanced replication
  • Data Mining

Finally, the pattern models a Detail Node for each installed options, and links it to the Oracle RDBMS SI.

The result is an easy-to-read Table, visible directly from the Software Instance.

Note: The list of options to search for is customizable from the Configuration section of the Pattern Module

Oracle Database Installed Options via File

If the above SQL Query fails or is unable to be executed for any reason, the pattern attempts to get the installed options from the comps.xml file.

On the Windows platform, the following active commands will extract the information from %ora_home%\inventory\ContentsXML\comps.xml:

  • CMD /C "FINDSTR /n /b /r ^.COMP.NAME=.oracle\. '+comps_xml_path+'"
  • CMD /C "FINDSTR /n /r EXT_NAME.*/EXT_NAME '+comps_xml_path+'"

The first FINDSTR command will match a line such as '<COMP NAME="oracle.rdbms" ...>'. As we are unable to retrieve two adjacent lines at once using FINDSTR, we ask for the line number to be returned to us as well.

The second FINDSTR command will match a line such as '<EXT_NAME>Oracle Partitioning</EXT_NAME>'. Like the first FINDSTR command, we ask for the line number to be returned to us as well. Such lines should be the very next line to each of those retrieved in the first FINDSTR command.

The pattern then goes through the second list whilst also going through the first list. If two adjacent lines are discovered, comp_name is extracted from the first and ext_name from the second.

On the UNIX platform, the following active command will extract the information from %ora_home%/inventory/ContentsXML/comps.xml:

  • 'cat ' + comps_xml_path + ' | sed -n \'/^<COMP NAME="oracle\..*"/{N;p;}\'
Note: For Atrium Discovery 8.2 and higher the pattern will try to read the file with privileged execution.

Having extracted certain matching adjacent lines from the comps.xml file, comp_name and ext_name are isolated using the following regular expression:

  • (?s)<COMP.*?NAME="(.+?)".*?<EXT_NAME>(.+?)</EXT_NAME>

If the comps.xml file is parsed successfully, the pattern compares the results against a user configured list of installed options to search for.

The installed options searched for by default are:

  • Oracle OLAP RDBMS Files
  • Oracle Partitioning

In certain cases, the name of the installed options as entered into the installed_options_via_file Configuration field will be converted via a table to the same name as that entered in the installed_options_via_query Configuration field.

Finally, the pattern models a Detail Node for each installed options, and links it to the Oracle RDBMS SI.

The result is an easy-to-read Table, visible directly from the Software Instance.

Note: The list of options to search for is customizable from the Configuration section of the Pattern Module
Skip to end of metadata
Go to start of metadata
Labels:
tku_2012_apr_1 tku_2012_apr_1 Delete
detail_node detail_node Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.