Oracle: Database PowerPack Release Notes, version 103

Version 103 of the Oracle: Database PowerPack adds support and addresses issues related to Oracle database host selection and user permissions.

  • Minimum Required SL1 Version: 10.1.0

Before You Install or Upgrade

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

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

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

You must also remove any pre-existing discovered Oracle Database device trees and all Oracle device classes before initially installing the PowerPack.

NOTE: You do not need to remove Oracle Database device trees and Oracle device classes if you already have the PowerPack installed and are upgrading to the latest version.

Installation and Upgrade Process

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 are included in the PowerPack:

  • Added support for the alignment of the "Oracle: DB Archived File System Stats" and "Oracle: DB Non-Archived File System Stats" Dynamic Applications to AIX and Solaris OS.

  • Added the Dynamic Application "Oracle: DB Instance Invalid Object Stats".

  • An enhancement was introduced in which the HTTP Header: SERVICE_NAME can be used in place of SID. However, if the SERVICE_NAME is different from the SID, discovery will fail.

  • Addressed an issue in which an exception was raised for SSH communication that caused an erroneous message.
  • Updated the "Session Stats" Dynamic Application to return the value "0", for the "Session Count" collection object, when the SQL query returns a null value (for Inactive Sessions).
  • A solution was applied to the "Percent Free" data graph which failed to display a number of Oracle DB performance data.
  • Addressed an issue in which the PowerPack failed for Windows server due to two different server paths.
  • Updated an event message with new Problem Resolution text.

  • Addressed an issue in which the "Oracle: DB Instance Discovery" Dynamic Application did not include the listener name in the log message during event generation.

  • Fixed an issue in which the formula, for the Oracle: DB Buffer Cache Hit Ratio value, was incorrect.

  • Fixed an issue in which the Oracle DB PowerPack failed to install on AIO systems due to size.

  • Added support for Active Directory accounts to configure Oracle monitoring.

  • Addressed an issue in which Oracle DB Tablespace Utilization alerts appeared false and inaccurate.

  • An enhancement was introduced in which SID headers can add a HOST option, with a custom IP, to connect with Oracle DB. Users can use the following header combos:

    • SID:<INSTANCE>:PORT:<NUMBER>

    • SID:<INSTANCE>:PORT:<NUMBER>:HOST:<HOST>

    • HOST:<HOST>

  • An enhancement was added in which Listener Names must be unique and not identical. If a user's SQLnet files are not in the default location, i.e. "$ORACLE_HOME/network/admin/", they must set "TNS_ADMIN" to the location where they reside, and add it to the http_header. The correct header format reads as follows:

    • SID:DB1:PORT:1521:TNS_ADMIN:/path/to/DB1s/sqlnetfiles

    • SID:DB2:PORT:1522:TNS_ADMIN:/path/to/DB2s/sqlnetfiles

  • Updated the Oracle: DB Powershell Example credential's Hostname/IP field from "<IP_OF_THE_SERVER>" to "%D".
  • Updated an event policy for the "Oracle: DB Server Config" Dynamic Application to include the name of the instance for clarity.

  • Addressed an issue in which the event "Oracle: DB Dynamic Application Alignment Required" was not triggered for Solaris during device discovery.

Known Issues

The following known issues affect version 103 of the Oracle: Database PowerPack:

  • 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.