OUI Evidence Reported by FNMS (Oracle Universal Installer)

OUI Evidence Reported by FNMS (Oracle Universal Installer)

Synopsis

Trying to clean up the Instances of Oracle programmer as reported by FNMS. The problem appears to be OUI evidence that is reported by FNMS ? but we can not identify the source of the evidence on the endpoint.

Discussion

The oraInst.loc, inventory.xml and comps.xml files are used by OUI to track software installed by an OUI installer. A oraInst.loc (e.g. "/etc/oraInst.loc") contains an inventory_loc entry, for example:

  • inventory_loc=/u/oracle/app/oraInventory
  • inst_group=oinstall

Under the inventory_loc path will be a "ContentsXML/inventory.xml" file (in this example, "/u/oracle/app/oraInventory/ContentsXML/inventory.xml"). The inventory.xml file provides HOME elements that contain a LOC attribute. For example:

...
<HOME_LIST>
<HOME NAME="OraDb11g_home1" LOC="/u/oracle/app/oracle/product/11.2.0/dbhome_1" TYPE="O" IDX="1"/>
</HOME_LIST>
...

Each home includes an "inventory/ContentsXML/comps.xml" file (in this example, "/u/oracle/app/oracle/product/11.2.0/dbhome_1/inventory/ContentsXML/comps.xml"). The comps.xml file contains the installer evidence extracted by the inventory agent. For example:

...
<PRD_LIST>
<TL_LIST>
<COMP NAME="oracle.server" VER="11.2.0.1.0" BUILD_NUMBER="0" REP_VER="0.0.0.0.0" RELEASE="Production" INV_LOC="Components/oracle.server/11.2.0.1.0/1/" LANGS="en" XML_INV_LOC="Components21/oracle.server/11.2.0.1.0/" ACT_INST_VER="11.2.0.1.0" DEINST_VER="11.2.0.0.0" INSTALL_TIME="2011.Jun.02 20:39:31 EST" INST_LOC="/u/oracle/app/oracle/product/11.2.0/dbhome_1/oracle.server">
<EXT_NAME>Oracle Database 11g</EXT_NAME>
<DESC>Installs an optional preconfigured starter database, product options, management tools, networking services, utilities, and basic client software for an Oracle Database server. This option also supports Automatic Storage Management database configuration.</DESC>
<DESCID>COMPONENT_DESC</DESCID>
<STG_INFO OSP_VER="10.2.0.0.0"/>
...

For each "COMP" element in the "TL_LIST", the following properties are used:

  • "EXT_NAME" element - Package "Name"
  • "VER" attribute of "COMP" - Package "Version"
  • "INST_LOC" attribute of "COMP" - Package "InstallLocation"
  • "INSTALL_TIME" attribute of "COMP" - Package "InstallDate"
  • A hard coded "Oracle Corporation" - Package "Publisher"

From the example:

<Package Name="Oracle Database 11g" Evidence="OUI" Version="11.2.0.1.0" InstallDate="20110602T203931">
<Property Name="InstallLocation" Value="/u/oracle/app/oracle/product/11.2.0/dbhome_1/oracle.server"/>
<Property Name="Publisher" Value="Oracle Corporation"/>
</Package>

If the agent is told to scan the file system (i.e. -o IncludeDirectory=/), it will discover the oraInst.loc, inventory.xml and comps.xml files as part of that scan. The tracker.log should be inspected which will give details on which packages have been found on the device. You will see messages similar to the following appearing in the tracker.log -

[2018/04/15 01:24:20 AM (G, 0)] {2940} The file 'C:\oracle\inventory\ContentsXML\comps.xml' has been detected as a possible package registry

You should review each .xml file to make sure it contains the correct information that accurately reflects which applications are installed on the device by OUI. For more information, you can enable the '+Inventory/Packaging/OracleUniversalInstaller' agent trace flag. For information on how to enable an agent trace, see knowledge article "How to enable etcp tracing for Inventory Agent".

Labels (2)
Was this article helpful? Yes No
No ratings
Version history
Revision #:
1 of 1
Last update:
‎Jun 08, 2018 10:31 AM
Updated by: