Version 106 of the "Oracle: Database" PowerPack includes updates to the ASM Dynamic Applications and TCPS support for authentication purposes. This PowerPack is now compatible with Python 3.6.
- 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 "Oracle: Database" PowerPack version 106.
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 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 106. Once you have upgraded to version 106, 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:
- Search for and download the PowerPack from the PowerPacks page (Product Downloads > PowerPacks & SyncPacks) at the ScienceLogic Support Site.
- In SL1, go to the PowerPacks page (System > Manage > PowerPacks).
- Click the Actions menu and choose Import PowerPack. The Import PowerPack modal appears.
- Click PowerPack file from step 1. and navigate to the
- Select the PowerPack file and click . The PowerPack Installer modal displays a list of the PowerPack contents.
- Click PowerPack is added to the PowerPack Manager page. . The
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:
-
Added the following Dynamic Applications to this PowerPack:
- "Oracle: DB ASM Diskgroups Stats"
- "Oracle: DB ASM Disks Config"
- "Oracle: DB ASM Disks Stats"
NOTE: These Dynamic Applications are auto-aligned to the root device. When upgrading this PowerPack, you will need to either manually align the Dynamic Applications, or run the discovery session for that device again. To monitor ASM, you will need either SYSDBA privileges, or be in the OSASM group. ScienceLogic recommends that the ASMSNMP user with SYSDBA privileges monitors the Oracle ASM instances. The ASMSNMP user is an Oracle ASM user with specific privileges (SYSDBA) that allows them to monitor for Oracle ASM instances.
-
The "Oracle: DB Tablespace Stats" Dynamic Application had the following updates:
- Refactored the Dynamic Application snippet code to include numeric values for space
- Tuned queries for more performance and stability
- Added new alerts and events for numeric space usage
- Added and updated new collection objects, presentation objects, and thresholds
-
The "Oracle: ASM Diskgroup Config" Dynamic Application had the following updates:
- Updated the snippet code
- Updated collector affinity from Root Device Collector to Assigned Collector
- Changed the poll frequency from 2 hours to 15 minutes
- Removed the following collection objects:
- Diskgroup
- DB Name
- DB Status
- Failure Group Name
- Mount Path
- Diskgroup Name
- Diskgroup State
- Added the following collection objects:
- Type
- Offline Disks
- Compatibility
- Database Compatibility
- Voting Files
- Disk Group Info
- Name
- State
- Migrated the following collection objects to the "Oracle: DB ASM Diskgroup Stats" Dynamic Application:
- Free Space
- Total Space
- Used Space
- Added new events and alerts for Disk Group states
-
The "Oracle DB ASM Instance Config" Dynamic Application had the following updates:
- Updated the snippet code
- Removed the "Oracle Home" collection object
- Added a new "Cluster Name" collection object
- Changed the collector affinity from "Root Device Collector" to "Assigned Collector"
- Updated the poll frequency from 1 hour to 15 minutes
In version 106 of this PowerPack, the "Oracle DB ASM Instance Config" was duplicated since it is now aligned to a different device. The old version of this Dynamic Application is still in the PowerPack with the name "Oracle DB ASM Instance Config (moved)". The "Oracle DB ASM Instance Config (moved)" Dynamic Application will be removed completely in a future version of the PowerPack.
NOTE: The "Oracle DB ASM Instance Config" Dynamic Application will now be aligned to ASM instances that are modeled by the new "Oracle: DB ASM Discovery" Dynamic Application.
-
Updated the expiry time from 15 minutes to 30 minutes for the following events:
- Oracle: DB Archived FileSystem: No file system data found
- Oracle: DB Device Classification Required
- Oracle: DB Dynamic Application Alignment Required
- Oracle: DB Instance Device Classification Required
- Oracle: DB Instances are not running on the server
- Oracle: DB Log Entry
- Oracle: DB non CDB Dynamic Application Alignment Required
- Oracle: DB Non-Archived FileSystem: No file system data found
-
Removed the following example credentials:
- Oracle: DB NONCDB Example
- Oracle: DB RAC/NONCDB Example
- Oracle: DB Example
- Oracle: DB Powershell Example
-
Added the following example credentials:
- Oracle: DB Example - ASM
- Oracle: DB Example - TCPS
- Oracle: DB Example SOAP - TCPS
- Oracle: DB Example SOAP - RAC
-
Renamed the following example credentials:
- "Oracle: DB CDB Example" to "Oracle: DB Example - CDB/non-CDB"
- "Oracle: DB PDB Example" to "Oracle: DB Example - PDB"
- "Oracle: DB RAC/CDB Example" to "Oracle: DB Example - RAC"
- "Oracle: DB Powershell AD Example" to "Oracle: DB Example PSH"
- "Oracle: DB CDB/PDB SOAP Example" to "Oracle: DB Example SOAP - CDB/PDB"
- "Oracle: DB NONCDB SOAP Example to "Oracle: DB Example SOAP - non-CDB"
- "Oracle: DB SSH Server Example" to "Oracle: DB Example SSH"
-
Updated the PowerPack to be compatible with Python 3.6.
-
The “Oracle: DB ASM Diskgroup Config (moved)” and “Oracle: DB ASM Instance Config (moved)” Dynamic Applications were duplicated and disabled by default. These Dynamic Applications will be fully removed in the next release. You can safely unalign them.
-
Disabled the "Oracle: DB RAC Disk Group Space Stats" Dynamic Application by default. Previously, this Dynamic Application collected the same information as the "Oracle: DB ASM Diskgroup Stats" Dynamic Application.
-
This PowerPack now supports a more secured communication (TCPS) protocol for authentication purposes.
-
Added a new version of the "silo_oracle_db" library which uses python-oracledb for TCP connections. TCPS connections will continue to use cx_Oracle.
-
All Run Book Action (RBA) in this PowerPack will now have the SSL_VERIFY key set to "False". If you are running SL1 with self-signed certificates, the SSL_VERIFY key must be set to "False". If you have a CA certificate, you may set the SSL_VERIFY key to "True".
-
Removed the "Oracle: DB ASM Dynamic Application Alignment" run book action.
-
Removed the "Oracle: DB ASM Dynamic Application Alignment" run book automation.
-
Removed the "Oracle: DB ASM Dynamic Application Alignment Required" event.
-
Added a new "Oracle: DB ASM Discovery" Dynamic Application. This Dynamic Application will be automatically aligned to the root device.
NOTE: If you have upgraded from a previous version of this PowerPack to version 106, the Dynamic Application will not be automatically aligned and will require you to manually align it to the root device, or run the discovery session again for that device. To do so, update your SOAP headers and add a new entry for every ASM instance, with ASM:<db cred id>, where <db cred id> is the Database credential for that ASM instance. You can either stop ASM Dynamic Applications that already aligned to former devices from keeping history records, or delete the ASM Dynamic Applications. You must delete old ASM run book actions (RBAs) to prevent them from aligning to the wrong devices.
In version 106 of this PowerPack, the "Oracle: ASM Diskgroup Config" was duplicated since it is now aligned to a different device. The old version of this Dynamic Application is still in the PowerPack with the name "Oracle: DB ASM Diskgroup Config (moved)", but now with some collection objects removed. The "Oracle: DB ASM Diskgroup Config (moved)" Dynamic Application will be removed completely in a future version of the PowerPack.
NOTE: This Dynamic Application is now auto-aligned to the root device. When upgrading this PowerPack, you will either need to manually align the Dynamic Applications, or run the discovery session for that device again.
Known Issues
The following known issues affect this release of the 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.
- TNS_ADMIN and GRID_PATH are not supported in SOAP/XML credentials for Windows devices.