Agent-Based Collection of Oracle Inventory

FlexNet Manager Suite 2023 R2 (On-Premises)

This section provides details about Oracle discovery and inventory using a local instance of FlexNet inventory agent. In this context, 'local' means that FlexNet inventory agent is installed and executing on the target Oracle server.

Except as noted in following topics, it does not matter how the FlexNet inventory agent was deployed. In the terms defined in the Gathering FlexNet Inventory PDF, the concept of 'local agent-based inventory collection' covers:

• The Adopted case
• The Agent third-party deployment case.

Prerequisites for local agent-based inventory collection

The following must be in place for collection of Oracle inventory by a local copy of the FlexNet inventory agent installed on the target Oracle server:

1. The installed Oracle Database must be release 9i or later on UNIX-like platforms; and on Windows platforms, release 10g or later is preferred.
2. You have licensed the FlexNet Manager for Datacenters product (for details, see Appendix F: Features Enabled in FlexNet Manager for Datacenters).
3. You have deployed and configured one or more inventory beacon(s) in your network, such that at least one inventory beacon can access each of your target Oracle servers. For detailed information about inventory beacons, their deployment, and configuration, see the topics under What Is an Inventory Beacon? in the online help. You initiate deployment of an inventory beacon by navigating to Discovery & Inventory > Beacons.
4. If you intend to use the capabilities of FlexNet Manager Suite to discover Oracle servers on the network and automatically install the FlexNet inventory agent on them (a process called 'adoption'), you also require the following:
   • Your organizational site and subnet hierarchy is recorded through the Discovery & Inventory > Subnets page of the web interface (see Subnets in the online help).
   • You have assigned the defined subnets to inventory beacon(s) through the Discovery & Inventory > Beacons page of the web interface (see Assigning a Subnet to a Beacon in the online help).
5. You have set up the accounts required for operation, and (in the Adopted case) possibly separate accounts for adoption of the target Oracle servers. Details of the accounts for different platforms are in Credentials for Local Agent-Based Inventory.
6. You have deployed the FlexNet inventory agent to the target devices, ensuring that for UNIX-like systems, you have authorized or installed version 13.0.1 or later of the FlexNet inventory agent (earlier versions of the FlexNet inventory agent may fail to collect Oracle inventory on UNIX-like systems where permissions prevent global access to Oracle directories or files):
   • In the Agent third-party deployment case, following the guidelines starting from the Agent third-party deployment: Implementation topic within the Gathering FlexNet Inventory PDF
   • In the Adopted case, following the guidelines in the Adopted: Implementation topic in the same PDF.
     Tip: When you know the names or network locations of the Oracle servers you want to adopt, you can declare a single rule in the web interface for FlexNet Manager Suite to target and adopt these known machines. If you are unsure where all your Oracle databases may have been installed, you can use a more generalized discovery rule to find and identify those devices, and subsequently adopt them.