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

Oracle Database Consolidated

The Oracle Database Consolidated Report provides a comprehensive, license-focused summary of Oracle database deployments across your infrastructure. It consolidates findings from hardware configuration, virtualisation settings, usage evidence, and processor capping policies to deliver a clear and accurate view of licensing requirements.

This report requires both data from IFMP and ODMB to be uploaded and processed to work.

Graphical Overview

The graphical overview provides a high-level snapshot of the Oracle database estate, including device composition, version distribution, licensing needs, and potential verification tasks. This section serves as a starting point for understanding the overall scale and complexity of the environment.

Key highlights include:

  • Device and Database Breakdown: Total number of devices and databases included in the analysis.
  • Operating System and Device Type: Breakdown of database servers by OS and virtual/physical classification, supporting licensing model accuracy.
  • Version Distribution: Insights into deployment versions such as 11g and 12c, relevant for support lifecycle and feature availability.
  • Licensing Summary: Preliminary license calculations based on processor or NUP (Named User Plus) models, incorporating virtualization and capping configurations.
  • Usage-Based Cost Distribution: Visualization of processor requirements per feature usage (Used, Historical, Cloned or Verify) and corresponding cost implications.
  • Top Cost Drivers: Identification of the highest-cost databases based on feature usage and licensing impact, supporting prioritization in optimization efforts.
  • Verification Tasks: Counts of systems requiring manual verification due to insufficient evidence or ambiguous usage data.

This section provides context for the deeper analysis and serves as an executive summary for key stakeholders.

 

License Requirements

This section outlines the calculated licensing requirements across all Oracle database and feature components, incorporating virtualization, hardware data, capping, and usage insights.

Key Elements:

  • Product Scope: Covers the core Oracle Database Enterprise Edition along with all detected Management Packs and Options (e.g. Diagnostics Pack, Real Application Clusters, Advanced Compression).
  • License Models: Requirements are presented for both CPU-based and Named User Plus (NUP) licensing models. This dual view supports flexibility in evaluating the most cost-effective licensing approach.
  • Cost Calculation: Licensing and support costs are broken down by processor and NUP count, highlighting both the total cost of ownership and licensing impact per product.
  • Usage Alignment: Licensing quantities reflect the number of processors where each feature is considered "Used" or flagged for "Verify" status, ensuring licensing recommendations are evidence-based.
  • Verification Flags: The report highlights products that require further review, such as features with ambiguous evidence or unknown host configurations. These flags help prioritize manual checks to refine final licensing outcomes.
  • Unknown Host Consideration: Where host details are incomplete, conservative assumptions are applied to avoid underestimating license exposure, maintaining compliance integrity.

This section serves as the foundation for financial and compliance planning, enabling informed decisions around optimization, negotiation, or remediation.

 

Oracle Databases Installed

This section provides a detailed inventory of Oracle database instances discovered across the environment. It includes essential deployment attributes for each instance, such as:

  • Device and database names
  • Product edition and version (e.g. 11g Release 2, 12c Release 1)
  • Full version and instance status
  • GoldenGate enabled status
  • Associated application and environment (where available)
  • Data source (e.g. review_lite)

Additionally, the report includes Real Application Clusters (RAC) metadata:

  • RAC Hosts, RAC Instances, and RAC Members Count are shown per database.
  • RAC usage is only flagged as active when the number of members exceeds 1, as Oracle RAC can be technically enabled on a single node but is not arguably licensable in that state.

 

Infrastructure Reconciliation

This section provides a detailed mapping between virtualized devices and their physical or logical infrastructure, applying capping rules to accurately calculate licensable processor counts.

Key Elements:

  • Capping Models Considered: Capping status is derived from virtualization pools, physical host configurations, and cluster-level policies. Structures are labeled as Capped or Uncapped, with uncapped systems flagged for review where hardware details are missing.
  • Structure Types: Devices are grouped by structure type (e.g. Capped - Virtual, Uncapped - Incomplete), ensuring that resource allocation aligns with applicable licensing rules under Oracle policy.
  • Group Licensing Calculation: Each device group consolidates licensing at the correct infrastructure tier, avoiding over-counting across clustered or shared environments.
  • Licensable Editions and Options: Reconciled groups reflect the Oracle Enterprise Edition deployments and any relevant options (such as Active Data Guard or Diagnostics Pack) in use across the infrastructure.
  • Processor Totals: For each reconciled group, the number of required processor licenses and the corresponding cost are calculated post-capping, ensuring licensing obligations reflect actual entitlements needed.

This reconciliation ensures accuracy in high-risk virtualized environments, bridging the gap between raw deployment and compliant licensing assumptions.

 

Databases on Infrastructure

This section presents a detailed breakdown of each database in relation to its hosting infrastructure, combining physical hardware, virtualisation attributes, and Oracle licensing logic to determine processor license requirements.

Key Elements:

  • Infrastructure Attribution: Each database is mapped to its corresponding cluster, physical server, domain, pool, and virtual device, allowing for precise identification of its placement within the overall environment.

  • Virtualisation Metrics: For virtualised environments (e.g. VMWare), the analysis includes physical processor and core counts at multiple levels—device, vCenter, and datacenter—alongside the number of virtual cores allocated to each database. This supports correct licensing scoping in line with Oracle’s treatment of virtualised platforms.

  • Licensing Scope Determination: The report distinguishes whether licensing should be calculated at the virtual layer or elevated to the physical infrastructure, based on capping rules and structure classification. Capped systems are evaluated at their defined limits, while uncapped or incomplete systems trigger conservative calculations.

  • Processor Licensing Output: For each database, the total number of required processor licenses is displayed along with the associated Oracle options (e.g. Partitioning, Diagnostics Pack) and usage status (e.g. Used, Verify, Historical). This ensures that option-based licensing is aligned with infrastructure-level entitlements.

  • Virtualisation Impact: Where databases reside on shared or clustered infrastructure, the model consolidates usage and licensing at the appropriate tier, applying rules to avoid double-counting and accurately reflecting shared consumption across the estate.

This infrastructure-level view enables defensible licensing calculations by aligning technical deployment with Oracle’s policy boundaries—especially in environments involving VMWare or pooled virtualisation.

 

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.

 

Database Sessions and Schemas

Both of these tables are dicussed in the Oracle Database Usage Report article:

https://help.licenseware.io/oracle-database-usage-report


EBS Releases and Database Modifications

These sections are designed to support verification of Oracle E-Business Suite (EBS) deployments and customized database environments, both of which can influence licensing scope and audit outcomes.

The EBS Releases section identifies Oracle Applications deployments by capturing metadata such as the Applications System Name, Apps Release, and Database Release. This data provides transparency into which systems are running Oracle EBS and on what versions—crucial for determining bundled components, usage rights, and licensing requirements tied to Oracle Applications.

The Database Modifications section flags custom objects or schema-level changes across databases. It lists object types, creation timestamps, and last DDL times to help assess whether custom development has occurred. This is especially relevant when evaluating supportability, license compliance for development environments, or integration with Oracle EBS or other licensed Oracle software.

These insights help organizations confirm alignment between deployed Oracle software, customizations, and corresponding entitlements, reducing audit risk and supporting accurate reporting.