<Deprecated> Metering the number of Oracle Database concurrent sessions

To retrieve detailed information about the number of Oracle Database concurrent user sessions that run on the computers in your environment, use the Get Oracle Concurrent Sessions Number fixlet. When the data is imported to BigFix Inventory, it is displayed in the Resource Utilization report.

Before you begin

Note: Get Oracle Features fixlet is deprecated and Get Oracle Database Measurements fixlet is available to perform the actions that were earleir supported by Get Oracle Features fixlet. Get Oracle Features fixlet is available in the BigFix Inevntory version 10.

The task establishes Oracle database connection as the LocalSystem user on Windows, or as the database instance owner on Linux, AIX or Solaris. Ensure that this user has the Oracle SYSDBA privilege.

About this task

BigFix Inventory supports metering of Named User Plus license consumption. Run this task to retrieve information about the current number of concurrent sessions, and the high water mark value of concurrent sessions for Oracle Databases that are installed on the computers in your infrastructure. These values are individually retrieved for each database instance with the following SQL query.
SELECT sessions_highwater, sessions_current FROM v$license;
The database instance must be running when the task is executed. Otherwise, the values of high water mark, and current number of sessions equal 0 in the report. After you run this task, the data is collected on a daily basis by default, to preserve the high water mark value that is reset after each database instance restart.

For more information about the Oracle licenses, see: Oracle Database Licensing.

Procedure

  1. Log in to the BigFix console.
  2. In the navigation bar, click Sites > External Sites > BigFix Inventory > Fixlets and Tasks.
  3. In the upper right pane, select Get Oracle Concurrent Sessions Number.
  4. Optional: To enable debug logging, select the Debug mode check box.
    The information is logged in the script_trace_sessions.txt file that is, by default, in the following location.

    /var/opt/BESClient/LMT/ORACLE

    C:\Program Files (x86)\BigFix Enterprise\BES Client\LMT\ORACLE

  5. Optional: On Unix endpoints, you can change the folder in which the temporary script used by the fixlet is created. By default, it is Oracle instance owner's default folder. In case there is a security policy in place which forbids keeping executable scripts in this folder, you can select a subfolder of /tmp folder.
  6. To run the task, click Take Action. On the Target tab, select computers from which you want to retrieve the information, and click OK.
  7. Ensure that the software scans are enabled, and run automatically. If not, run the software scan manually. Select the Resource Utilization Scan.
  8. Ensure that the scan results are automatically uploaded. If not, upload the results to the BigFix server manually.
  9. To make the data available in BigFix Inventory, wait for the scheduled import of data, or run it manually.

Results

The retrieved data about the Oracle database concurrent sessions is listed in the Resource Utilization report. To view the data, log in to BigFix Inventory, and go to Reports > Resource Utilization.
The screen shows the detected Oracle Database concurrent sessions.