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

Getting Started: Oracle OLA Data Gathering Requirements

To perform an Oracle License Assessment (OLA) and accurately project Oracle workloads for AWS migration planning, Opscompass requires four separate data sets from the customer environment:

  1. Server and database inventory
  2. Oracle license entitlement information
  3. Oracle database feature and option usage
  4. Database performance history

All four data sets should be collected and submitted together before analysis begins. Information gathered through these processes is used exclusively for Oracle licensing assessment and workload sizing activities.

Prerequisites

Before beginning data collection, ensure you have:

  • Access to Oracle database hosts and environments included in the assessment
  • Oracle Support portal access (if license invoices are unavailable)
  • DBA assistance for database-level data collection
  • Access to any available discovery tooling (Cloudamize or equivalent)

Required Data Collection

1. Server and Database Inventory

Purpose
Server inventory data is used to establish the infrastructure footprint associated with Oracle workloads and provide sizing inputs for migration planning.
Required Information
For every in-scope server or instance, provide:
  • Server name
  • Virtualization type
  • vCPU count
  • Memory (RAM)
  • Disk allocation (GB)
  • Host processor model
  • Cloud instance shape (if applicable)

For Oracle database servers, also provide:

  • Database size on disk
  • Tablespaces
  • Redo logs
  • Flashback logs

Do not include:

  • Archive logs
  • Database backups

Collection Options

Preferred Method
Export inventory data from a discovery platform such as Cloudamize and clearly identify which systems are included in scope.
Alternative Method
If discovery tooling is unavailable, complete the Server Inventory Template provided by Opscompass.

2. Oracle License Entitlement Data

Purpose
License entitlement information is used to determine which Oracle products and quantities are currently licensed.
Preferred Method
Provide PDF copies of Oracle support renewal invoices from the previous 12 months.

Notes:

  • Financial amounts may be redacted.
  • Product names and quantities must remain visible.
Alternative Method
If renewal invoices are not available, export a license report from the Oracle Support portal.
Exporting License Data from Oracle Support
  1. Sign in to Oracle Support Renewals.
  2. Select Create Report.
  3. Under Include Renewal Types, select:
    • Pending
    • History
    • Future
  4. Under Choose Report Type, select Detailed.
  5. Select Download Report.
  6. Save the generated Support Service Renewals Details.csv file.
  7. Submit the CSV file to Opscompass.

3. Oracle Editions, Features, and Options Usage

Purpose
This data identifies which Oracle database editions, features, and optional components are actively in use within the environment. Only metadata is collected; no customer application data is extracted.
Collection Process
  1. Register for Oracle Feature Usage Monitoring.
  2. Download the latest version of Opscompass Studio.
  3. Have a DBA connect Opscompass Studio to each in-scope database using:
    • Database connection details
    • Opscompass credentials
  4. Run the feature usage assessment.
  5. Upload the generated feature usage extract for every in-scope database.
Deliverable
One feature usage extract per database included in the assessment scope.

4. Database Performance History

Purpose
Performance history data provides CPU and I/O utilization information used to estimate AWS sizing requirements and migration targets.
Collection Process
  1. Download the required SQL scripts from the DBCSI portal.
  2. Run the scripts against each in-scope Oracle database.
If diagnostics pack is licensed:
Run the AWR collection script.
If diagnostics pack is not licensed:
  1. Enable STATSPACK.
  2. Allow data collection to run for five days.
  3. Run the STATSPACK collection script.
  4. Submit the output files to Opscompass.

Submission Requirements

After completing all four collection activities, submit the following items together:

  • Server and database inventory
  • Oracle license entitlement documentation
  • Feature usage extracts
  • Database performance history outputs

Submitting all deliverables together allows Opscompass to complete the Oracle License Assessment and AWS sizing analysis efficiently.

Additional Notes

  • The Server Inventory Template is distributed separately from this process.
  • Contact Opscompass if a replacement copy of the template is required.
  • Oracle feature usage collection gathers metadata only and does not extract customer application data.