Oracle: Database PowerPack Release Notes, version 200

Version 200 of the "Oracle: Database" PowerPack includes improvements in the discovery process for Oracle devices by removing certain dependencies, updates several Dynamic Applications, and addresses alert and alignment issues.

  • Minimum Required SL1 Version: 12.1.0

Before You Install or Upgrade

Ensure that you are running version 12.1.0 or later of SL1 before installing the "Oracle: Database" PowerPack.

For details on upgrading SL1, see the relevant SL1 Platform Release Notes.

If you have the "SLPS: Oracle DB" PowerPack or "Oracle DB" PowerPack installed, you must remove them from your SL1 system.

You must also remove any discovered Community Pack related features, for example devices, device trees, and all Oracle device classes before initially installing this version of the PowerPack. However, if you are only upgrading to the latest version of the PowerPack, you do not need to remove Oracle Database trees and Oracle device classes.

Installation and Upgrade Process

If you are currently using the Dynamic Applications in this PowerPack to monitor devices, collection errors might occur for one or two polling cycles during the installation of a new version. To prevent collection errors during an upgrade, you can optionally disable collection for monitored devices before performing the following steps and re-enable collection after the upgrade.

To install this PowerPack:

  1. Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
  2. In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
  3. Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
  4. Click Browse and navigate to the PowerPack file from step 1.
  5. Select the PowerPack file and click Import. The PowerPack Installer modal displays a list of the PowerPack contents.
  6. Click Install. The PowerPack is added to the PowerPack Manager page.

Features

This release includes the following features:

  • Dynamic Applications that collect configuration and performance data about Oracle Database instances

  • Device classes for each of the Oracle devices monitored
  • Sample credentials for discovering Oracle instances
  • Event policies and corresponding alerts that are triggered when Oracle devices meet certain status criteria
  • A device dashboard for viewing the status of your Oracle database instances

Enhancements and Issues Addressed

The following enhancements and issued addressed are included in this release of the PowerPack:

  • Removed the following dependencies to improve the discovery process for Oracle devices:
    •  tnsnmanes.ora
    •  smon process
    •  pmon process
    •  Listener status parsing
    •  OS informations
    • oratab (for Linux servers)
  • Refactored nearly all Dynamic Applications to eliminate cache dependencies, enhancing overall system reliability and performance.
  • Removed support for the following SOAP/XML credential headers:
    • SID:PORT
    • TNS_ADMIN
    • GRID_PATH
    • HOST
    • TYPE_OF_OS
  • Updated the Collector Affinity from Root device collector to Assigned collector.
  • Modified the PowerPack so Windows users no longer need a PowerShell credential.
  • Maintained support that Linux users must still use the SSH credential for the following Dynamic Applications:
    • Oracle: DB Archived File System Stats
    • Oracle: DB Non-Archived File System Stats
  • Added support for Oracle Database version 23ai.
  • Made the following updates for the "Oracle: DB Server Config" Dynamic Application:
    • Removed the cache dependency
    • Updated the discovery object
    • Renamed the "OS Type" collection object to "Port String"
    • Removed the following collection objects:
      • Oracle DB Status
      • DB Name
      • UUIDAvailable
      • OS Version
      • Server Config
      • Listener Lookup
      • PMON Lookup
      • ASM Lookup
      • Oratab Lookup
      • Oracle DB Config Lookup Status
      • SMON Lookup
      • RAC Lookup
  • Made the following updates for the "Oracle: DB Instance Discovery" Dynamic Application:
    • Removed the cache dependency
    • Removed the "RAC Status" collection object
    • Renamed the following collection objects:
      • "Instance Config" to "Database-Level Information"
      • "Listener Host" to "Database Created Date"
      • "Listener Names" to "Database ID"
      • "Instance" to "Database Name"
      • "Instance Status" to "Database Open Mode"
      • "Listener Port" to "Database Role"
      • "Oratab Entry" to "Database Unique Name"
      • "Listener Config" to "Instance-Level Information"
      • "Listener Name" to "Instance Hostname"
      • "Listener Instances" to "Instance Name"
      • "Listener Log File" to "Instance Startup Time"
      • "Listener Parameter File" to "Instance Status"
      • "Listener Protocol" to "Instance Version"
  • Made the following updates for the "Oracle: DB Instance Config" Dynamic Application:
    • Removed the "Instance Reachable" collection object
    • Added the "ASM Installed" collection object
    • Removed the following alerts and events:
      • Oracle: DB Instance Connection Status Reachable
      • Oracle: DB Instance Connection Status Unknown
      • Oracle: DB Instance Connection Status Unreachable
  • Updated the "Oracle: DB Log Alerts Config" Dynamic Application to align to CDB Oracle Database instances.
  • Made the following updates for the "Oracle: DB Data Guard Gap Stats" Dynamic Application:
    • Modified the Dynamic Application to only collect if the Oracle database has the parameter dg_broker_start set to TRUE
    • Simplified the query to improve performance of the Dynamic Application
    • Renamed the following collection objects and presentation objects:
      • From "Gap to Primary" to "Thread"
      • From "Gap Received" to "Last Sequence Received"
      • From "Gap Applied" to "Last Sequence Applied"
      • From "Standby DB" to "Name"Made
  • Made the following updates for the "Oracle: DB Resource Stats" Dynamic Application:
    • Renamed the following thresholds:
      • From "Process Utilization Critical" to "Process Utilization Percent Critical"
      • From "Process Utilization Major" to "Process Utilization Percent Major"
      • From "Session Utilization Critical" to "Session Utilization Percent Critical"
      • From "Session Utilization Major" to "Session Utilization Percent Major"
      • From "Transaction Utilization Critical" to "Transaction Utilization Percent Critical"
      • From "Transaction Utilization Major" to "Transaction Utilization Percent Major"
    • Added new thresholds:
      • Process Utilization Percent Minor
      • Session Utilization Percent Minor
      • Transaction Utilization Percent Minor
    • Renamed the following alerts:
      • From "Oracle: DB Process Utilization exceeded critical threshold" to "Oracle: DB Process Utilization % exceeded critical threshold"
      • From "Oracle: DB Process Utilization exceeded major threshold" to "Oracle: DB Process Utilization % exceeded major threshold"
      • From "Oracle: DB Process Utilization has returned to normal" to "Oracle: DB Process Utilization % has returned to normal"
      • From "Oracle: DB Session Utilization exceeded critical threshold" to "Oracle: DB Session Utilization % exceeded critical threshold"
      • From "Oracle: DB Session Utilization exceeded major threshold" to "Oracle: DB Session Utilization % exceeded major threshold"
      • From "Oracle: DB Session Utilization has returned to normal" to "Oracle: DB Session Utilization % has returned to normal"
      • From "Oracle: DB Transaction Utilization exceeded critical threshold" to "Oracle: DB Transaction Utilization % exceeded critical threshold"
      • From "Oracle: DB Transaction Utilization exceeded major threshold" to "Oracle: DB Transaction Utilization % exceeded major threshold"
      • From "Oracle: DB Transaction Utilization has returned to normal" to "Oracle: DB Transaction Utilization % has returned to normal"
    • Added new alerts and events:
      • Oracle: DB Process Utilization % exceeded minor threshold
      • Oracle: DB Session Utilization % exceeded minor threshold
      • Oracle: DB Transaction Utilization % exceeded minor threshold
  • Made the following updates for the "Oracle: DB RAC Flash Recovery Stats" Dynamic Application with the following:
    • Added a new threshold:
      • Flash Recovery Usage Minor
    • Added a new alert and event:
      • Oracle: DB RAC Flash Recovery Usage exceeded minor threshold
  • Renamed the "Oracle: DB Tablespace Stats" Dynamic Application to "Oracle: DB Tablespace Datafile Stats" and addressed an issue related to data collection and alerts.
  • Added the new "Oracle: DB Overall Table Stats" Dynamic Application.
  • Added two new collection objects to the "Oracle: DB Tablespaces and Datafiles Status Config" Dynamic Application:
    • Tablespace Autoextensible (Group 1- If the tablespace has autoextensible datafiles)
    • Autoextensible (Group 2- If the datafile is autoextensible)
  • Added the new "Oracle: DB Instance Device UID Update Required" run book automation and "Oracle: DB Instance Device UID Update" run book action to update unique identifiers on Windows devices.
  • Updated the following Dynamic Applications to align to the root device rather than to the CDB/PDB if the Oracle device is a RAC instance:
    • Oracle: DB RAC Disk Group Space Stats
    • Oracle: DB RAC Flash Recovery Stats
    • Oracle: DB RAC Global Cache Stats

    • After updating the PowerPack to version 200, ScienceLogic recommends manually unaligning the RAC Dynamic Applications because they might remain aligned at the CBD and PDB level after updating. Then you must run the discovery session again or manually align the RAC Dynamic Applications to the root device. Otherwise, they will be aligned during nightly discovery.

  • Removed deprecated Dynamic Applications:
    • Oracle: DB ASM Diskgroup Config (moved)
    • Oracle: DB ASM Instance Config (moved)
  • Assigned the "Oracle Database: Instance" device dashboard to the following device classes:
    • Database Container Instance
    • Database Instance
    • Database RAC Instance
    • Database Server
    • Pluggable Database
  • Removed the following API Event Policies:
    • Oracle: DB Could not find SID instances in oratab
    • Oracle: DB failed to get SERVICE_NAME details from the server
    • Oracle: DB instance listener is down
  • Addressed an issue that prevented the "ASM" Dynamic Applications from collecting data when the database credential contained the value %D.
  • Addressed an issue that caused messages about the obsolete "Oracle: DB ASM Dynamic Application Alignment" run book action to be logged on the Database Container Instance device.
  • Addressed an issue that caused non-container instances to retrieve alerts from other instances.
  • Addressed an issue that prevented Oracle devices with Native Network Encryption (NNE) enabled from aligning to Dynamic Applications.
  • Decreased the number of sessions created by the PowerPack by 68% which contributes to improved system efficiency.

Known Issues

The following known issues affect this release of the PowerPack:

  • The error message "Cannot locate a 64-bit Oracle Client library: 'libclntsh.so'" may impact the discovery of devices using Native Network Encryption (NNE) and TCPS. This behavior is associated with a known issue in SL1. ScienceLogic recommends that you install the Oracle Instant Client on the collector unit as a workaround.
  • The "Oracle: DB Open Cursors per Session Stats" Dynamic Application might encounter collection errors when the data collected value is zero.
  • The "Oracle: DB Sessions Deviation is unusual" event policy does not have a clearing event. It is intended as an informational notice rather than a problem state.