Skip to content
  • There are no suggestions because the search field is empty.

Oracle Effective License Position

The Oracle Effective License Position (ELP) Report provides a complete comparison between the calculated license requirements—based on actual Oracle Database usage and infrastructure data—and the entitlement data uploaded through Oracle Entitlements Manager.

 The ELP considers metrics such as processor counts, virtualization, hardware topology, database option usage, and Oracle’s licensing rules (including core factors and capping) to determine whether an organization is compliant, under-licensed, or over-licensed across its Oracle estate.

This report serves as the final output of the Licenseware Oracle Database license optimization workflow, offering stakeholders an actionable view of license exposure, optimization opportunities, and audit readiness.

 

Graphical Overview

The Graphical Overview section provides a high-level visual summary of your Oracle license position across the environment. It includes key insights into device counts, deployment structure, and license compliance metrics.

ELP Overview

  • Number of Devices: Total count of servers or virtual machines where Oracle deployments were discovered.
  • Number of Databases: Total Oracle database instances analyzed in the assessment.

This gives immediate visibility into the scope of the deployment under review.

Virtual vs Physical

A pie chart showing the distribution of Oracle deployments across:

  • Physical (Cluster or Physical): Environments where physical hardware is used.
  • Virtual (Domain, Pool or Virtual): Deployments running on virtualized infrastructure.
  • Unknown: Systems where the virtualization state could not be determined.

Understanding virtualization is crucial for applying Oracle's licensing rules correctly (e.g., partitioning, soft vs hard partitioning).

Devices by Operating System

Another pie chart breaks down devices by operating system, such as:

  • Windows
  • Linux
  • ESX
  • AIX
  • Others

This can be useful for identifying OS-based licensing trends or areas where specific Oracle products are deployed more heavily.

Compliance by Product and Metric

This bar chart highlights the license compliance position for each Oracle product and license metric:

  • Positive values indicate surplus licenses.
  • Negative values indicate shortfall (under-licensed).
  • Metrics are split between Processor and Named User Plus, using color coding for clarity.

This visualization allows stakeholders to immediately spot areas of risk or inefficiency across key products such as:

  • Oracle Database Enterprise Edition
  • Tuning Pack
  • Advanced Security
  • Database Lifecycle Management Pack
  • Real Application Clusters

This graphical section provides the foundation for deeper compliance investigation and guides remediation or optimization strategies.

 

Oracle Compliance

The Oracle Compliance Table provides a detailed, line-by-line breakdown of how entitlement data aligns with the calculated licensing requirements for each Oracle product. This table is the core of the Effective License Position (ELP) report, enabling precise visibility into over- or under-licensing, across both Processor and Named User Plus (NUP) metrics.

Key Columns and Data Points

  • Product Name: The Oracle product under analysis (e.g., Database Enterprise Edition, Tuning Pack).
  • Processor Owned / NUP Owned: The total number of licenses owned per metric, as uploaded via the Oracle Entitlements Manager.
  • Processor Required: The number of processor licenses required, calculated using usage data, infrastructure details, and Oracle’s licensing rules (e.g., core factor, virtualization, and capping).
  • Processors Covered by NUP Minimum: Displays any processors covered through minimum user-based licensing, where applicable.
  • Processor Compliance / NUP Compliance: The delta between licenses owned and required. Positive values indicate surplus; negative values show license shortfall.
  • License Level: Typically shown as Full Use, indicating unrestricted deployment rights.
  • Active Support: Indicates whether the entitlement is covered by active support (true/false).
  • Processor License Cost / NUP License Cost: The estimated license cost based on current Oracle pricing, allowing cost impact analysis of any shortfalls.

Usage

This table enables:

  • Compliance validation for each Oracle product
  • Identification of licensing gaps or excesses
  • Estimation of cost exposure due to under-licensing
  • Support for audit preparation and renewal planning

Combined with the graphical overview, this tabular view gives license managers and compliance teams the actionable detail needed to respond to risk or realign entitlements effectively.

 

Oracle Server Worksheet

This section provides a standardized view of database-to-server mappings in alignment with the Oracle Server Worksheet (OSW) format—an industry-accepted structure commonly expected by Oracle during audit submissions or license declarations.

Each row presents a consolidated summary of database deployments, associating capped infrastructure devices with individual virtual machines and databases. The virtualization model (e.g. VMware, other), product version, and Oracle options in use are explicitly listed to ensure traceability.

The report also highlights the license metric applied (typically Processor), making it easier to validate that licensing aligns with Oracle’s core-based entitlement rules. Where applicable, both management packs (e.g. Diagnostics Pack) and database options (e.g. Active Data Guard, Advanced Compression) are recorded alongside each instance.

By matching each database to its virtualized or physical host context and applied licensing metric, this worksheet offers clear, audit-ready evidence of license-relevant deployments.

 

icense Baseline

The Tabular Breakdown section of the Oracle Entitlements Baseline Report provides a detailed, filterable view of all uploaded entitlement records. Each row represents a single entitlement entry and includes essential information needed for license reconciliation and compliance tracking.

Key Columns Displayed

  • Product Family: Categorizes whether the entitlement relates to a database or non-database product.
  • Product Category: Specifies the product grouping (e.g., Oracle Database, Enterprise Edition Options).
  • Product Name (Raw): The name of the licensed Oracle product, as provided in the uploaded entitlement file.
  • Quantity: The number of entitlements available for the product.
  • License Metric: Indicates whether the entitlement is based on metrics such as Processor, Named User Plus, or Application User.
  • License Level: Typically set to Full Use, representing unrestricted usage rights.
  • Restrictions: Any contractual limitations applicable to the entitlement (e.g., Full Use, Limited Use).
  • Active Support: A boolean field (true/false) showing whether the entitlement has active support coverage.

Functionality Highlights

  • Search and Filter: Use the built-in search bar and filter controls to quickly locate specific products or license types.
  • Column Customization: Toggle column visibility using the "Hide columns" option for a personalized view.
  • Data Integrity: Values displayed reflect the original uploaded data, ensuring traceability to your entitlement source files.

 

Oracle Usage Evidence

This section provides the technical evidence used to determine the usage classification of each Oracle Database option. It includes detailed feature-level insights and the specific sample data that triggered a classification of Used, Historical, Verify, or Not Used.

Each row corresponds to a detected usage event, including the database version, feature name, source file, and result. The additional details such as detected usages, total samples, usage intervals, host, instance name, and licensing notes help validate the classification with clear, auditable evidence.

The evidence is collected over a defined sample interval and includes metadata such as:

  • Feature Name & File: Identifies the specific option and the input file from which data was extracted.
  • Detected Usages and Total Samples: Quantifies how often the feature was seen in use versus the total opportunities to detect it.
  • Licensing Notes: Provides guidance on whether additional licensing is required for that feature under Oracle’s terms.
  • Sample Period & Evidence Strings: Technical data confirming the match to known Oracle usage patterns.

These results support the classifications seen in previous sections of the report and are key in driving licensing conclusions in the Consolidated Oracle Database Report, especially when differentiating between incidental and licensable usage.