Product Description
The management packs can be purchased only with Enterprise Edition. The features in these packs are accessible through Oracle Enterprise Manager Database Control, Oracle Enterprise Manager Grid Control, and APIs provided with Oracle Database software.
The pattern obtains the following management packs:
- Oracle Diagnostic Pack
- Oracle Tuning Pack
- Oracle Data Masking Pack
- Oracle Change Management Pack
- Oracle Configuration Management Pack
- Oracle Provisioning and Patch Automation Pack
All management packs are enabled by default and require separate license until they are manually disabled.
Software Instance Triggers
| OS type | Trigger Node | Attribute | Condition | Argument |
|---|---|---|---|---|
| Unix, Windows | SoftwareInstance | created, confirmed | ||
| and type | = | "Oracle Database Server" | ||
| and instance | exists | |||
| and edition | = | "" or "Enterprise" |
Oracle Management Packs via Query
The pattern executes an SQL Query against the Oracle Database Instance, unless this option has been disabled in the pattern configuration. The pattern uses 'success_login_cred' attribute of related "Oracle Database Server" SI to run DB Query.
| Note: Pattern tries to run sql query to system tables "sysman.mgmt_license_view" or "sysman.mgmt_admin_licenses", which could require additional privileges setup for oracle database User. |
| Note:The database query to Oracle Database Server will only run if the extended_sql_discovery option is enabled in the Oracle Database pattern configuration section. By default it is enabled |
The following query obtains all enabled management packs.
- for Oracle 11: select PACK_NAME from sysman.mgmt_license_view where target_type='oracle_database'
- for Oracle 10: select PACK_NAME from sysman.mgmt_admin_licenses"
The result is the list of enabled packs for specific Oracle instance.
For Oracle 11 pattern also tries to run sql query which obtains value of oracle parameter "control_management_pack_access":
- select VALUE from v$parameter where name = 'control_management_pack_access'
An initialization parameter, CONTROL_MANAGEMENT_PACK_ACCESS, controls access to the Diagnostic Pack and Tuning Pack. This parameter can be set to one of three values:
- DIAGNOSTIC+TUNING: Diagnostic Pack and Tuning Pack functionally is enabled in the database server.
- DIAGNOSTIC: Only Diagnostic Pack functionality is enabled in the server.
- NONE: Diagnostic Pack and Tuning pack functionally is disabled in the database server.
Oracle Management Packs via File
If query method is not succeed for Oracle 11, then pattern tries to read information from the file: "<db_si.ora_home>\\ccr\\state\\<db_instance>.ll" which contains "state" data which is collected once per day:
- Windows: 'findstr control_management_pack_access "<db_si.ora_home>\\ccr\\state\\<db_instance>.ll"
- Unix: 'grep control_management_pack_access "<%db_si.ora_home>/ccr/state/<db_instance>.ll"
Finally, the pattern models a Detail Node for each management pack, and links it to the Oracle RDBMS SI.
The result is an easy-to-read Table, visible directly from the Software Instance.
Testing
This pattern has been tested against Oracle Database Server running on multiple platforms (Unix/Linux and Windows) with different configurations
Information Sources
- Oracle® Database Licensing Information was used to get list of available management packs and thier description.
- Oracle® Enterprise Manager Command Line Interface was used to see how to grants licenses on a set of user-specified packs or all packs to a set of user-specified targets or all targets belonging to the input licensable target type.
Open Issues
There are no known open issues with this pattern.
| TOP |
|---|
Created by: Vadym Ratniuk 18 Nov 2011
Updated by: Vadym Ratniuk 19 April 2012
Reviewed by: Viktor Moyseyenko 23 Jan 2012
Tideway Blog