Oracle Enterprise Manager (OEM) licensing works as follows:
- Included with Oracle Database: OEM’s basic functionalities are part of the Oracle Database license.
- Separate Licenses for Premium Functions: Advanced features, known as OEM Packs (e.g., Diagnostics, Tuning Packs), require an additional license.
- Default Enabled Packs: During installation, several OEM Packs are enabled by default.
- Disabling Unlicensed Packs: Users must manually deselect unlicensed packs post-installation to avoid non-compliance.
- Usage-Based Licensing: Licensing depends on using specific features within OEM Packs.
Oracle Enterprise Manager Licensing
Oracle Enterprise Manager (OEM) is a powerful tool that simplifies database and system management in Oracle environments. Properly licensing its features is critical to ensuring compliance and avoiding unexpected costs.
1. Basic OEM Functionalities Included with Oracle Database
- What’s Included: The core OEM features come bundled with your Oracle Database license at no additional cost.
- Examples include basic monitoring and administration tools like database instance management and simple alerting capabilities.
- Limitations: While these features provide essential functionality, premium OEM packs do not include advanced diagnostics, performance tuning, or automation capabilities.
2. Separate Licenses for Advanced OEM Packs
- Premium Features: Advanced functionalities are offered as part of specific OEM Packs, such as:
- Diagnostics Pack: Includes tools like Automatic Database Diagnostic Monitor (ADDM), Active Session History (ASH), and Automatic Workload Repository (AWR).
- Tuning Pack: Provides SQL Access Advisor, SQL Tuning Advisor, and Real-Time SQL Monitoring.
- Other Packs: Additional packs like Cloud Management Pack or Lifecycle Management Pack address specific operational needs.
- Licensing Requirements: These packs require separate licenses, and the licensing terms must match the Oracle Database license type (e.g., CPU or Named User Plus).
3. Default Enabled Packs During Installation
- Default Settings: When OEM is installed, certain advanced packs, such as Diagnostics and Tuning Packs, are enabled by default.
- Compliance Risk: If unlicensed packs remain enabled and their features are used, it can result in non-compliance during Oracle audits.
- Action Required: Users must proactively disable unlicensed packs to avoid accidental usage.
4. Disabling Unlicensed Packs
- Manual Deactivation: Unlicensed packs must be manually deselected in the OEM interface to prevent accidental use.
- Steps:
- Log in to Oracle Enterprise Manager.
- Navigate to the setup or management section.
- Disable features associated with unlicensed packs.
- Example: If your organization has only licensed the Diagnostics Pack, disable Tuning Pack features such as SQL Tuning Advisor to ensure compliance.
5. Usage-Based Licensing
- How Licensing Works: Licensing uses specific features within the OEM Packs. Simply enabling the pack is not a licensing requirement; using its features does.
- Key Considerations:
- Running AWR reports or using ADDM constitutes usage of the Diagnostics Pack.
- Employing SQL Tuning Advisor constitutes usage of the Tuning Pack.
- Tracking Usage: Organizations can use Oracle-provided scripts or logs to monitor which features have been accessed.
Oracle Enterprise Manager Licensing
Oracle Enterprise Manager (OEM) is a versatile tool that provides extensive database management capabilities for Oracle environments.
While the Oracle Database license includes basic OEM functionalities, accessing advanced features requires additional licenses for Oracle Database Enterprise Edition Management Packs (OEM Packs).
Here’s a detailed look at OEM licensing, focusing on its installation process and compliance considerations.
The OEM Installation Process
OEM is typically installed alongside the Oracle Database and can be deployed in three main architectures:
- Database Control: A single-instance configuration for managing one database instance.
- Grid Control: Enables centralized management of multiple databases and servers in an enterprise environment.
- Cloud Control: Extends Grid Control capabilities to provide advanced monitoring and management for cloud environments, including Oracle Cloud and hybrid architectures.
These architectures cater to different levels of database management complexity, from simple setups to large-scale, multi-database ecosystems.
OEM Functionality and Licensing
While basic OEM functionalities are part of the Oracle Database license, advanced capabilities are classified as licensable features and require a separate license for specific OEM Packs.
These include:
- Diagnostics Pack: This pack enables performance diagnostics through tools such as the Automatic Database Diagnostic Monitor (ADDM) and Active Session History (ASH).
- Tuning Pack: Provides tools such as SQL Tuning Advisor and SQL Access Advisor to optimize database performance.
- Database Lifecycle Management Pack: Automates provisioning, patching, and configuration management tasks.
- Data Masking and Subsetting Pack: This pack secures sensitive data by masking it for non-production environments and creating smaller subsets for testing.
- Cloud Management Pack for Database: Offers management and monitoring features for databases deployed in the cloud.
Default Activation of OEM Packs
During installation, the Oracle Management Agent (OMA) automatically enables several OEM Packs by default, regardless of what the customer has licensed. These include:
- Diagnostics Pack
- Tuning Pack
- Database Lifecycle Management Pack
- Data Masking & Subsetting Pack
- Cloud Management Pack for Database
Key Issue: These packs’ default activation can lead to the inadvertent use of unlicensed features, resulting in non-compliance with Oracle’s licensing policies.
The Features of Diagnostics and Tuning Packs
Oracle’s Diagnostics Pack and Tuning Pack are advanced tools designed to optimize database performance, monitor system health, and address performance bottlenecks.
These packs provide a range of features that enhance the management and efficiency of Oracle databases. However, proper licensing is essential to ensure compliance with Oracle’s policies.
Features of the Diagnostics Pack
The Diagnostics Pack focuses on monitoring, diagnosing, and maintaining the health of Oracle databases.
Key features include:
- Automatic Workload Repository (AWR)
- Collects and maintains performance statistics to detect and resolve performance issues.
- Stores historical data for trend analysis and proactive management.
- Automatic Database Diagnostic Monitor (ADDM)
- Analyzes AWR data to provide actionable recommendations for resolving database performance issues.
- Performance Monitoring (Database and Host)
- Offers real-time and historical performance data for both databases and their underlying hosts.
- Helps identify resource bottlenecks and system inefficiencies.
- Event Notifications
- Sends alerts for events like threshold breaches or resource constraints, enabling quick responses to potential issues.
- Blackouts
- Temporarily disables monitoring for scheduled maintenance periods, ensuring alerts are not triggered unnecessarily.
- Additional Tools
- Includes a variety of views and reports for in-depth diagnostics and system analysis.
Features of the Tuning Pack
The Tuning Pack builds on the capabilities of the Diagnostics Pack, focusing on SQL optimization and database performance tuning. Key features include:
Includes reports and utilities to support database administrators in fine-tuning SQL queries and database structures.
SQL Access Advisor
Recommends changes to data structures like indexes, materialized views, and partitions to improve query performance.
SQL Tuning Advisor
Analyzes poorly performing SQL statements and provides recommendations for rewriting or optimizing queries.
SQL Tuning Sets
Allows you to group and manage SQL statements for collective tuning and analysis.
Reorganize Objects
Helps optimize database objects like tables and indexes to improve performance.
Automatic SQL Tuning
Continuously monitors and adjusts SQL performance without manual intervention.
Additional Tools
Difference Between “Access Pack Agreed” and “Access Pack Granted” in Oracle OEM Licensing
In Oracle Enterprise Manager (OEM) licensing, the terms “Access Pack Agreed” and “Access Pack Granted” refer to how the usage of licensable management packs, such as Diagnostics Pack or Tuning Pack, is handled and tracked.
Understanding the distinction between these concepts is critical for ensuring compliance with Oracle’s licensing policies.
1. Access Pack Agreed
When a pack is marked as Access Pack Agreed, it indicates that the organization has explicitly accepted and licensed the usage of the associated management pack.
- Implications:
- The organization has a valid license for the specified pack.
- All features and functionalities of the pack can be utilized without compliance concerns.
- During an audit, Oracle will expect to see a license agreement covering the exact packs for which “Access Agreed” is set.
- Example: If you select “Access Pack Agreed” for the Diagnostics Pack in Oracle OEM, you have licensed this pack and are authorized to use features like Automatic Database Diagnostic Monitor (ADDM) or Active Session History (ASH).
2. Access Pack Granted
When a pack is marked as Access Pack Granted, it means that the OEM installation has enabled the features of the associated pack, regardless of whether the organization has officially licensed it.
Example: If “Access Pack Granted” is set for the Tuning Pack without a corresponding license, and SQL Tuning Advisor is used, this would constitute non-compliance. He used these features when confronted with them during an Oracle audit.
Implications:
- Features of the granted pack are available for use, but the organization must ensure proper licensing.
- Compliance issues could arise during an Oracle audit if unlicensed features are used.
- Organizations are responsible for disabling unlicensed packs to avoid unintentional usage.
FAQs
What is Oracle Enterprise Manager (OEM) licensing?
Oracle Enterprise Manager licensing governs the use of its advanced management packs and features, classified as licensable options. While basic functionalities are included with the Oracle Database license, advanced features like the Diagnostics and Tuning Packs require additional licenses.
Are basic OEM features free to use?
Yes, the Oracle Database license includes basic OEM functionalities such as database monitoring and basic administration at no extra cost. However, accessing advanced features requires separate licenses.
What are OEM packs, and why are they licensable?
OEM packs, like the Diagnostics Pack and Tuning Pack, are advanced tools that provide features such as performance diagnostics, SQL tuning, and automation. Oracle classifies these packs as premium add-ons, which require separate licensing.
How do I know which OEM packs are enabled in my system?
You can review the packs enabled by checking the Management Pack Access Settings in Oracle Enterprise Manager. Oracle Management Agent (OMA) often enables these packs by default during installation, even if they are not licensed.
What is the difference between “Access Pack Agreed” and “Access Pack Granted”?
“Access Pack Agreed” indicates that you have licensed the specific OEM pack and are authorized to use its features. “Access Pack Granted” means the pack is enabled, but you may not have the required licenses, creating potential compliance risks.
Do I need a license for both Diagnostics and Tuning Packs?
Yes, the Tuning Pack requires a Diagnostics Pack license as a prerequisite. You must also license the Diagnostics Pack to use features like SQL Tuning Advisor.
What happens if unlicensed OEM packs are used?
Using unlicensed OEM packs can result in non-compliance with Oracle’s licensing policies. This may lead to penalties or the requirement to purchase licenses retroactively during an audit.
Can I disable unlicensed OEM packs?
Yes, unlicensed packs can and should be disabled to avoid accidental usage. This can be done in the Management Pack Access Settings within Oracle Enterprise Manager.
How does Oracle track OEM pack usage?
Oracle tracks OEM pack usage through feature logs and auditing tools. Any activity involving a licensable feature, such as generating AWR reports or using SQL Tuning Advisor, is considered usage and requires appropriate licensing.
Is licensing for OEM packs based on database licensing?
Yes, OEM pack licenses must match your Oracle Database license type. For example, if you have CPU-based database licenses, the same licensing model applies to your OEM packs.
What are the common challenges with OEM licensing?
Challenges include identifying unlicensed usage due to default pack activation, understanding complex licensing requirements, and ensuring compliance during audits. Keeping track of which packs are actively used can also be difficult.
How can I audit my OEM pack usage?
You can use Oracle-provided scripts like option_usage.sql and used_options_details.sql to review which OEM packs and features are in use. This helps identify any discrepancies in licensing.
Are OEM packs included with Oracle Cloud services?
Many OEM packs, such as Diagnostics and Tuning Packs, are included with Oracle Cloud services under the Bring Your Own License (BYOL) policy. However, licensing rules vary based on deployment.
How do I address compliance risks with OEM licensing?
To address compliance risks, regularly audit your OEM usage, disable unlicensed packs, and ensure that your licenses align with your database and management needs. Educating your team about licensing policies also helps.
