Configure Collection of Oracle Inventory
Rules must be established that allow Oracle inventory collection, including the use of .ora files.
- A target that identifies the machines on which the rule is to be exercised
- Actions that are the be performed on those target machines
- The schedule on which the rule is to be applied.
When an action includes permission to use a .ora file, the relevant inventory beacon uses the locally-available .ora file to 'filter' the related target and identify the Oracle Database servers from which inventory should be collected. For example, if you target an IP range that covers your server room, and include the action setting to apply the .ora file to this range, then Oracle inventory is collected only from the matching machines listed in the .ora file.
Once a discovery and inventory collection has been completed, the individual Oracle Database servers are identified in the list of discovered devices. Should you wish to change to tighter targeting rules, you can use this information to redefine the target until (if you wish) it identifies exactly the Oracle Database servers and no others. Keep in mind that if you use this approach, you will need to adjust the target each time you vary the list of your Oracle Database servers. To reduce this manual maintenance, keep a target that specifies an appropriate IP range (or ranges), and applies the .ora file to this to identify the individual Oracle Database servers from which to collect inventory.
To configure Oracle inventory collection:
FlexNet Manager Suite (On-Premises)
2022 R1