Oracle: Database PowerPack Release Notes, version 104

Version 104 of the Oracle: Database PowerPack adds support for container database (CDB) and pluggable database (PDB) instances and addresses multiple issues. This version also adds new Run Book Action policies, Run Book Automation policies, events, and Dynamic Applications.

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

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.

NOTE: If you discovered a container database in version 103 or earlier of this PowerPack, you should remove those devices prior to upgrading to version 104. Once you have upgraded to version 104, you can run a new discovery session for those devices.

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

  • Database credential support was added for CDB, non-CDB, and PDB instances and values in the "Oracle: DB Example" SOAP/XML credential were updated.

    • NOTE: Prior versions of this PowerPack support CDB instances as a database instance but the Dynamic Applications can exhibit inconsistent results.

  • The "Database Container Instance" device class and icon were added to the PowerPack.

  • The "Container Database Instance (CDB) collection object was added to the "Oracle: DB Instance Config" Dynamic Application.

  • The following action policies were added to the PowerPack:

  • Oracle: DB Instance Device Classification
  • Oracle: DB CDB Dynamic Application Alignment
  • Oracle: DB non CDB Dynamic Application Alignment

  • The following automation policies were added to the PowerPack:

  • Oracle: DB Instance Device Classification Required
  • Oracle: DB non CDB Dynamic Application Alignment

  • The following Dynamic Applications were added to the PowerPack:

  • Oracle: DB ASM Diskgroup Config
  • Oracle: DB ASM Instance Config
  • Oracle: DB PDB Discovery
  • Oracle: DB RMAN Backup Status Config

  • The following events were added to the PowerPack:

  • Oracle: DB Instance Device Classification Required
  • Oracle: DB non CDB Dynamic Application Alignment Required

  • An issue was addressed in which an error would occur when a SID name in an HTTP header of a SOAP/XML credential contained "SSH" or "PSH". (Case: 00226174)

  • An issue was addressed in which the "Oracle: DB Rows Stats" Dynamic Application was generating alerts due to an incorrect formula calculation. The fix includes an update to the formula to calculate the percentage and the "Oracle: DB Chained Rows exceeded major threshold" event threshold was updated to a percentage type. (Case: 002300865)

  • An issue was addressed in which the "silo_oracle_db" library was skipping the first "TNS_ADMIN" header configured in a SOAP/XML credential. (Case: 00213375)

Known Issues

The following known issues affect version 104 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.

  • SSH commands have a maximum timeout of 60 seconds. If you have a server that is taking more than 60 seconds to respond to SSH commands, you might find inconsistencies in the "Oracle: DB Server Config" Dynamic Application and eventually the DCM tree.

  • ASM related Dynamic Applications only align to ASM instances. If you have a RAC, CDB, or, PDB that has an ASM feature enabled and has access to the following views, you can manually align ASM instances to the RAC, CDB, or PDB

  • v$asm_diskgroup
  • v$asm_client
  • v$ASM_DISK