Some users may have issues creating a community account. For more information, please click here.

Information about Oracle Universal Installer (OUI) evidence gathered by the FlexNet inventory agent

Information about Oracle Universal Installer (OUI) evidence gathered by the FlexNet inventory agent

Synopsis

This article discusses how the FlexNet Inventory agent gathers inventory data from Oracle Universal Installer (OUI) files.

Occasionally one encounters a false recognition on Oracle applications due to Oracle Universal Installer (OUI) evidence that is reported by the FlexNet inventory agent, but it is not readily apparent where the source of the evidence is on the endpoint. The information here may help to troubleshoot and diagnose this kind of scenario.

Discussion

OUI tracks details of installed Oracle software components using files named oraInst.loc, inventory.xml and comps.xml.

The /etc/oraInst.loc file 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 directory 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. An example of the type of data that can be found in these files is:

...
<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"/>
</COMP>
...

For each COMP element, the following properties are used:

  • EXT_NAME element - installer evidence "Name"
  • VER attribute - installer evidence "Version"
  • INST_LOC attribute - installer evidence "InstallLocation"
  • INSTALL_TIME attribute - installer evidence "InstallDate"
  • A hard coded "Oracle Corporation" - installer evidence "Publisher"

Package details in a inventory .ndi file generated from the above example would look like:

<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>

Installation directories that no longer exist

Anecdotally, it is not uncommon to find comps.xml files are not reliably updated by Oracle Universal Installer to indicate Oracle applications are no longer installed when an uninstalled is performed. This can result in FlexNet Manager Suite recognizing installations of Oracle applications based on the evidence, despite other files associated with the installation no longer being on the computer.

The FlexNet inventory agent versions 2021 R1 (17.0) and later contain and improvement that will only return evidence from comps.xml files where the directory specified in the INST_LOC attribute actually exists. Earlier agent versions return all evidence as specified in the comps.xml file, regardless of whether referenced installation directories actually exist.

Logging

If the agent is configured to scan the file system, it will discover the oraInst.loc, inventory.xml and comps.xml files as part of that scan. The inventory agent's tracker.log 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 currently installed on the device.

Additional diagnostic tracing information about the scanning performed by the inventory agent may be able to be obtained by enabling the +Inventory/Packaging/OracleUniversalInstaller agent trace flag in the etcp.trace file.

Related resources

Labels (1)
Was this article helpful? Yes No
No ratings
Comments

What if we are still unable to locate the file proving the installation is in fact on the device?  is it just written off as a false positive or is there a workaround?  Should we unlink that evidence to the application?

@joshua_neadow - You should look at the TRACKER.LOG file on the server in question.  This will indicate where each xml file is found that contains OUI install evidence.

You will see entries in the log file such as the following:

[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

Version history
Revision #:
5 of 5
Last update:
‎Aug 20, 2021 02:51 AM
Updated by: