Issues with Discovery
FlexNet Manager Suite
2024 R1
(On-Premises)
Having checked the prerequisites (see Troubleshooting Agent-Based Collection of Oracle Inventory) and shown that the FlexNet Inventory Agent is correctly installed and can access the InventorySettings.xml file, you already know that the discovery process for initially identifying the target inventory device (the Oracle server) has worked.
However, there is a second kind of discovery
involved in gathering Oracle inventory. Recall that the installed FlexNet Inventory Agent is policy-driven, not rule-driven (meaning that after
device discovery, it is no longer affected by discovery or inventory rules that you
set in the web interface). It has no local record of previous
discoveries; it has only its policy driving it to see what is available on this
inventory device. In the case of an Oracle server as the target inventory device,
the installed FlexNet Inventory Agent is driven to prepare three files for
upload:
- The standard hardware and software inventory (.ndi)
file that is prepared on every inventory deviceRemember: If the
PerformOracleFMWScan
preference is true (and InventorySettings.xml is available and up-to-date), this .ndi includes any evidence found for Oracle Fusion Middleware applications. - A separate discovery (.disco) file that records the (re-)discovery of the installed Oracle Database
- A separate inventory (.ndi) file exclusively for the inventory of all the Oracle database instances found on this device.
Symptoms
If this stage of discovery fails, the typical symptoms are:- The inventory device (Oracle server) is visible in the page
- The Oracle instance(s) are missing from the . page
To troubleshoot Oracle discovery:
FlexNet Manager Suite (On-Premises)
2024 R1