AI tools are becoming increasingly capable of answering complex enterprise licensing questions, including Oracle licensing where small misunderstandings can carry significant contractual and financial risk. The real question is whether AI can interpret Oracle’s detailed policies, product dependencies, and audit-sensitive rules with the same accuracy and context as a specialist who works daily with Oracle Java, WebLogic, Database Options and Packs, and Oracle Cloud Infrastructure requirements.
To find out, we tested four leading AI tools across four Oracle specific licensing questions that frequently cause uncertainty for organisations. These included:
• Which Java versions are freely covered by OpenJDK and which Oracle Java versions require a paid subscription
• Whether an existing Oracle WebLogic license can cover the use of Oracle Business Intelligence when both run on the same instance
• How to correctly identify which Oracle Database Options and Packs are installed and whether historical usage evidence can be removed
• The key prerequisites for migrating to Oracle Cloud Infrastructure, including technical, architectural and licensing considerations
We assessed the following AI tools:
• Claude Sonnet 4.5
• OpenAI GPT-5 (ChatGPT)
• Gemini Pro
• Copilot GPT-5
Each AI tool received the same Oracle licensing questions. Their responses were scored on accuracy, completeness, and practical usefulness, particularly in the context of Oracle audits, negotiations, and cloud migrations where incorrect interpretations can quickly escalate risk and cost.
Below is how they performed.
Claude Sonnet 4.5 and Co-Pilot GPTS scored the highest in this Oracle-specific round, delivering strong accuracy across all four questions.
OpenAI GPT-5
1. Which Java versions can be covered by Open JDK and which versions are covered by Oracle Java for which a license is needed?
OpenJDK
- Oracle’s OpenJDK builds (Java 9+) are released under GPL v2 + Classpath Exception and are free to use/redistribute. (Other vendors’ OpenJDK builds like Eclipse Temurin, Amazon Corretto, etc., are also free under their distro terms.)
Oracle JDK (commercial)
- JDK 21 and later: available under Oracle’s No-Fee Terms and Conditions (NFTC) — free for all users. (Oracle’s own FAQ states “Oracle JDK 21 and later is under NFTC.”) Oracle
- JDK 17 and older: coverage depends on the period and license. Oracle’s policy changes mean many orgs now need an Oracle Java SE Universal Subscription for production use of these versions (and since Jan 2023 Oracle moved to a per-employee pricing model). In practice, most enterprises treat 8/11/17 Oracle JDK usage as subscription-required, unless they’re using OpenJDK builds instead.
Quick rule of thumb
- If you want “free Java,” standardize on OpenJDK builds. If you need Oracle JDK support or specific Oracle tooling assurances, use Oracle Java SE Universal Subscription (especially for 8/11/17), while JDK 21+ can be free under NFTC.
2. If I’m having an Oracle WebLogic license and I’m also using Oracle Business Intelligence (OBI) on the same instance, can my Weblogic license cover the use of OBI?
No — OBIEE/OAS requires its own license; your general WebLogic license doesn’t “cover” OBI.
- Oracle BI products include a restricted-use WebLogic (WebLogic Standard Edition or WebLogic Server Basic) strictly for running the BI stack; it does not grant general WebLogic rights beyond that scope. Conversely, holding a WebLogic license does not entitle you to run OBI/OAS without licensing OBI/OAS.
- Oracle’s Application Licensing Table and BI licensing notes confirm the restricted-use nature of the middleware bundled with applications.
3. Please provide the steps in identifying what Oracle DB options & packs I have installed on my Oracle Databases. Can I delete the historical evidence of using the options/packs that are not licensed?
Discovery steps (do all three):
- List feature usage: query DBA_FEATURE_USAGE_STATISTICS to see what options/packs have been detected as used (and when).
- Run Oracle’s official script: options_packs_usage_statistics.sql (My Oracle Support) for a normalized report across options and management packs.
- Verify installed components / disable if unneeded: review DBA/REGISTRY views and, where applicable, use chopt to disable optional components you don’t intend to use going forward (e.g., Data Mining, OLAP).
About deleting history:
- Do not delete or tamper with historical usage data. Oracle audits rely on multiple data sources (DB views, AWR/trace, host inventory, LMS/GLAS Collection Tool outputs). Removing local evidence can be treated as spoliation and won’t prevent discovery via Oracle’s official tooling. Control future exposure by disabling features; keep an auditable trail.
4) Prerequisites for migrating to Oracle Cloud Infrastructure (OCI)
At a minimum, line up the following before you migrate any workload:
Foundations (“landing zone”)
- OCI tenancy established; compartment design, IAM groups/policies, tagging, budgets/quotas, and a CIS-aligned landing zone (Terraform blueprints available).
Networking & connectivity
- VCN/subnets, DRG, routing, security lists/NACLs.
- For hybrid connectivity, plan VPN Connect and/or FastConnect (bandwidth, redundancy, IP prefix validation).
Migration service prep
- For Oracle’s Cloud Migrations service: configure resource manager stack, object storage buckets, Vault (credentials/keys), and required policies in the target compartments.
Operational readiness
- Align with Well-Architected pillars (security, reliability, performance/cost, operations). Use Oracle’s reference implementations and GitHub landing-zone modules for automation.
TL;DR
- Java: Free → OpenJDK; Oracle JDK 21+ can be free under NFTC; 8/11/17 typically need Oracle Java SE Subscription for production.
- WebLogic vs OBI: You cannot use a general WebLogic license to “cover” OBI; OBI/OAS carries its own license and bundles restricted-use WebLogic only for that purpose.
- DB options/packs: Use DBA_FEATURE_USAGE_STATISTICS + Oracle’s options/packs script; don’t delete history — disable features and document.
- OCI migration: Stand up a landing zone, IAM & networking, and meet Cloud Migrations service prerequisites; plan VPN/FastConnect.
Claude Sonnet 4.5
1. Which Java versions can be covered by Open JDK and which versions are covered by Oracle Java for which a license is needed?
OpenJDK (Free for All Uses):
Since September 2017, Oracle provides JDK releases under a free open source license (similar to that of Linux). Availability and community support of OpenJDK releases provided by Oracle is listed separately on jdk.java.net.
All Java versions have free OpenJDK implementations available from various providers (Oracle OpenJDK, Eclipse Temurin, Amazon Corretto, Azul Zulu, Red Hat OpenJDK, Microsoft builds).
Oracle Java Licensing Requirements:
Since September 2023, Oracle provides the Oracle JDK 21 under a free use license for All Users. Since September 2025, Oracle provides the Oracle JDK 25 under a free use license for All Users. Oracle JDK releases for Java 8, 11, and 17 are available under the Oracle Technology Network License Agreement for Java SE, which is free for Personal, Development and other Users only.
Breakdown by Version:
- Java 8, 11, 17: Oracle JDK 17, Oracle JDK 11, Oracle JDK 8, and Oracle JRE 8 with Java Web Start, are available to Oracle Customers via My Oracle Support and also under the OTN License Agreement for Java SE. This OTN license permits personal use, development, testing, prototyping, demonstrating, and some other limited uses at no cost. Production use requires a paid license.
- Java 21: Oracle JDK 21 and later release are available under a Oracle No-Fee Terms and Conditions License for all users. Updates of JDK 21 released after September of 2026, are planned to be offered under the Java SE OTN license. Free until September 2026.
- Java 25: Since September 2025, Oracle provides the Oracle JDK 25 under a free use license for All Users. Currently free.
Key Takeaway: Any Java version can be used for free if you choose a non-Oracle distribution. Oracle’s own JDK is free only in specific cases (older versions under the old license, or during a limited no-fee window for certain LTS releases).
2. If I’m having an Oracle WebLogic license and I’m also using Oracle Business Intelligence (OBI) on the same instance, can my Weblogic license cover the use of OBI?
No, your standalone WebLogic license does NOT cover OBI. However, OBI includes its own WebLogic license.
Oracle Business OBIEE 12c and Oracle Analytics Server include WebLogic Server Standard Edition bundled for hosting the BI platform. The OBIEE license covers this WebLogic usage. However, if you wanted clustering for OBIEE beyond what WebLogic SE supports, you’d have to license WebLogic EE separately for those nodes.
Important Restrictions:
Oracle WebLogic Server Standard Edition: Its use is restricted to supporting OBI SEE only. Clustering capabilities for WebLogic Server are not allowed unless otherwise licensed.
Critical Compliance Point:
If you installed a custom Java web app on the same WebLogic that runs OBIEE, that would violate the license terms of OBIEE’s bundled WebLogic. The remedy would be to purchase a full WebLogic license for that tier, and separate the environments.
Summary:
- OBI comes with its own restricted WebLogic SE license
- This WebLogic can ONLY be used for running OBI
- You cannot use this WebLogic for other applications
- If you need clustering beyond what SE provides, you need WebLogic EE licenses
- Your existing standalone WebLogic license does not entitle you to use OBI
3. Please provide the steps in identifying what Oracle DB options & packs I have installed on my Oracle Databases. Can I delete the historical evidence of using the options/packs that are not licensed?
Steps to Identify Installed Options & Packs:
Step 1: Query DBA_FEATURE_USAGE_STATISTICS
Step 2: Use Oracle’s Official Script
Step 3: Force an Update
Can You Delete Historical Evidence? NO – This is NOT Recommended and Likely Ineffective
Critical Warning: The feature usage view is the same one that Oracle would refer to in the case of a formal audit of its products at a customer site.
Why You Cannot/Should Not Delete:
- Oracle’s audit tools capture this data: The LMS tool likely uses this to mark an option as “Used” if any usage was recorded. For instance, if a single partitioned table exists or existed, the feature usage view will have an entry for partitioning with a detected usage count
- Oracle’s policy: Oracle’s policy is that if an option is used, you must license it for that database environment
- Evidence exists in multiple places: The data isn’t just in one view – it’s tracked across multiple internal tables and Oracle’s LMS scripts capture comprehensive data during audits
What You SHOULD Do Instead:
- Disable unlicensed features immediately: Organizations should disable unlicensed database options and management packs to prevent accidental use and should regularly check usage to highlight compliance issues early and limit financial risks
- Use CONTROL_MANAGEMENT_PACK_ACCESS parameter: For management packs, set this parameter to restrict usage
- Document your compliance efforts: Disabling it before an official audit submission shows good faith effort (though it doesn’t erase past usage)
- Purchase licenses or negotiate: Either license the features you’ve used or negotiate with Oracle
4. What are the prerequisites of migrating to Oracle Cloud Infrastructure?
Prerequisites for OCI Migration:
1. Access & Identity Requirements:
Access to an Oracle Cloud Infrastructure (OCI) tenancy. Create or designate compartments to use. Oracle Cloud Migrations integrates with IAM for authentication and authorization of all interfaces (OCI Console, SDK, CLI, and REST APIs)
An administrator in your organization sets up the required Oracle Cloud Migrations service policies
2. Source Environment Requirements:
The Oracle Cloud Migrations service supports the following source and target environment, and asset types:
- VMware vCenter environments (vSphere 8.0 supported with VDDK 7.0U2)
- AWS EC2 instances
- Physical servers
3. Operating System Compatibility:
For Linux VMs:
- Oracle Linux (with automatic Premier Support access)
- Various validated Linux distributions
For Windows VMs:
- All windows instances on shared compute must be registered with the Oracle-provided Key Management Service (KMS) server. Bring your own license (BYOL) for Windows Server is not permitted when launching a VM instance on a shared host
4. Licensing Compliance:
Ensure that you comply with all the OS and application licensing requirements when you run migrated instances on Oracle Cloud Infrastructure (OCI). For information about licensing requirements of Microsoft products on OCI, see Microsoft Licensing on OCI
5. Pre-Migration Assessment:
Before beginning the migration, prepare your Oracle Cloud environment. Next, you must establish a secure connection between your on-premises environment (or any external infrastructure) and Oracle Cloud
Create a workload list with either your CMDB (configuration management database) or by using automated discovery tools. Enumerate your existing resources and performance requirements. Align the discovered assets and applications with business priorities or phases. Map on-premises or other cloud resources to OCI resources
6. Technical Setup:
- Set up source environment connections
- Deploy remote agent appliance for discovery and replication
- Configure network connectivity between on-premises and OCI
- Establish secure data replication channels
7. Planning Requirements:
- Create migration projects grouping related workloads
- Develop detailed migration plans including testing phases
- Schedule data replication windows
- Plan for cutover timing with minimal downtime
The key is proper planning, ensuring licensing compliance, establishing secure connectivity, and having the right IAM policies and permissions in place before starting the migration process.
Gemini Pro
1.Which Java versions can be covered by Open JDK and which versions are covered by Oracle Java for which a license is needed?
This is a critical distinction. The licensing model for Oracle’s own Java build changed significantly in 2019.
- Oracle Java (Needs a License):
- Since 2019, if you are using the Oracle JDK (the one you download directly from Oracle) for commercial, production use, you need a paid Java SE Universal Subscription.
- This applies to updates for Java 8 (released after January 2019) and all subsequent versions, including the Long-Term Support (LTS) releases like Java 11, Java 17, and Java 21.
- The subscription is typically licensed “per-employee,” which can be very expensive.
- OpenJDK (Covered and Free):
- OpenJDK (Open Java Development Kit) is the open-source project and reference implementation of Java. It is free for all use, including commercial.
- You can get free, commercially supported OpenJDK builds from many providers, including:
- Eclipse Temurin (from the Adoptium project)
- Amazon Corretto
- Microsoft Build of OpenJDK
- Red Hat OpenJDK
- Even Oracle provides an “Oracle OpenJDK” build that is free for commercial use. The key is to use their OpenJDK build, not their commercial Oracle JDK.
In short: If you want to use Java for free, use any version of OpenJDK from a major provider. If you use the commercial Oracle JDK, you must pay for a subscription.
2. If I’m having an Oracle WebLogic license and I’m also using Oracle Business Intelligence (OBI) on the same instance, can my Weblogic license cover the use of OBI?
No, your WebLogic license does not cover the use of OBI.
These are two separately licensed products.
- Oracle WebLogic Server: This license (e.g., Standard or Enterprise Edition) gives you the right to run the WebLogic application server for your custom applications.
- Oracle Business Intelligence (OBI): This is a separate, licensable product. It has its own license (typically per-user or per-processor).
A common point of confusion is the reverse: When you buy OBI, it often includes a “restricted-use” license for WebLogic. This means you get a “free” copy of WebLogic, but you are only allowed to use it to run the OBI components (and nothing else, like your own custom Java apps).
Your full-use WebLogic license does not grant any rights to run OBI. You must license OBI separately.
3. Identifying and Managing Oracle DB Options & Packs
Steps to Identify Usage
You can identify which options and packs have been used by querying a specific data dictionary view.
- Log in to the database with DBA privileges.
- Query the DBA_FEATURE_USAGE_STATISTICS view. This view is updated about once a week by a system job.
- You can also check Oracle Enterprise Manager (OEM), which has a “Database Feature Usage” section.
Oracle also provides official scripts (like options_pack_usage.sql, found on My Oracle Support) that provide a more detailed report, as this view can sometimes show false positives.
Can I delete the historical evidence?
Warning: This is strongly discouraged and is considered a violation of your Oracle license agreement.
During an official software audit, Oracle’s auditors (LMS) do not trust this one table. They run their own proprietary, in-depth audit scripts that check for installed objects, running processes, and other artifacts of the options.
If you are caught deleting this data, it is seen as a willful attempt to hide non-compliance. This will destroy any goodwill in an audit and likely result in severe penalties, including forcing you to license all “suspected” usage at full list price with no discounts.
The only compliant way to resolve this is to:
- Identify what you are not licensed for.
- Formally disable the features (if possible).
- Contact Oracle or your reseller to “true-up” and pay for any past or current unlicensed use.
4. Prerequisites for Migrating to Oracle Cloud Infrastructure (OCI)
Migrating to OCI is a major project. The prerequisites fall into three main categories:
1. Assessment and Planning
- Workload Analysis: You must inventory all on-premise applications, databases, and servers you intend to move.
- Performance Baseline: You need to measure your current performance (CPU, memory, storage IOPS, network throughput) to correctly “right-size” your new cloud instances.
- Dependency Mapping: You must understand which applications talk to which databases and which systems talk to each other. This is crucial for planning your “migration waves.”
- Target Service Selection: You need to decide what you are migrating to. For example, will your database run on a VM (IaaS), on Exadata Cloud Service, or on Autonomous Database (PaaS)?
2. Commercial and Licensing
- License Review: You must have a clear understanding of all your current on-premise Oracle licenses.
- BYOL vs. License-Included: You must decide on a licensing model.
- Bring Your Own License (BYOL): You can re-use your existing on-premise licenses (if they have active support) to get a significant discount on OCI services.
- License-Included: You pay a single, all-in price for the OCI service that includes the software license. This is often simpler but can be more expensive if you already own licenses.
3. Technical and Network
- Network Connectivity: You must establish a secure, high-speed connection between your datacenter and OCI. This is typically done with:
- IPSec VPN: Good for testing and non-critical workloads.
- FastConnect: A dedicated, private, high-bandwidth connection that is the standard for production workloads.
- Identity and Access Management (IAM): You need a plan for managing users. Will you create new users in OCI IAM, or will you federate with your existing identity provider (like Microsoft Entra ID or Okta)?
- Migration Tooling: You need to select the right tool for the job. For databases, this could be Oracle Zero Downtime Migration (ZDM), RMAN, or Data Pump.
Co-Pilot365
1. Which Java versions can be covered by Open JDK and which versions are covered by Oracle Java for which a license is needed?
· What it is:
OpenJDK is the open-source implementation of the Java Platform, Standard Edition (Java SE).
· License:
Distributed under the GNU General Public License (GPL) with Classpath Exception.
o This means you can use, modify, and distribute it freely—even in commercial applications—without paying license fees.
· Coverage:
o Provides the full Java SE specification.
o Includes the Java compiler (javac), runtime (java), and core libraries.
· Support:
o Community-driven updates.
o No official long-term support (LTS) unless you use a vendor distribution (e.g., Adoptium, Amazon Corretto, Red Hat).
Oracle Java
· What it is:
Oracle’s distribution of Java SE, based on OpenJDK but with additional testing, performance tuning, and enterprise support.
· License:
o Since Java 11, Oracle changed its licensing model:
§ Free for development and personal use.
§ Commercial use requires a paid subscription (Oracle Java SE Subscription).
· Coverage:
o Same Java SE features as OpenJDK.
o Extra tools and support for enterprise environments.
· Support:
o Official patches, security updates, and long-term support from Oracle.
Key Difference
· OpenJDK: Free, open-source, community-supported.
· Oracle Java: Free for dev/test, paid license for production/commercial use if you want Oracle’s binaries and support.
2. If I’m having an Oracle WebLogic license and I’m also using Oracle Business Intelligence (OBI) on the same instance, can my Weblogic license cover the use of OBI?
Does a WebLogic license cover Oracle BI (OBIEE/OAS)?
· No, a paid WebLogic license does NOT automatically cover Oracle Business Intelligence products like OBIEE or Oracle Analytics Server (OAS).
These BI tools have their own separate licenses, typically based on:
o Processor-based licensing (for large or unlimited user access).
o Named User Plus (NUP) licensing (for smaller, controlled user bases).
What about WebLogic bundled with BI?
· Oracle BI Suite Extended Edition (legacy OBIEE) includes a restricted-use WebLogic Standard Edition license:
o Only for hosting the BI application.
o Clustering is not allowed under this restricted license.
o You cannot use that WebLogic instance for other apps outside BI.
If you already have a paid WebLogic license
· That license does not waive the need for an OBIEE/OAS license.
You still need to license the BI product separately because Oracle treats them as distinct products with separate metrics and price lists.
Summary:
· WebLogic and Oracle BI are licensed independently.
· BI products come with their own restricted-use WebLogic license for internal BI use only.
· If you want to run BI and other apps on the same WebLogic instance, you need both licenses (WebLogic + BI).
3. Identifying and Managing Oracle DB Options & Packs
Here’s how you can approach this:
Step 1: Identify Installed Oracle DB Options & Packs
Oracle provides several ways to check which options and management packs are installed or used:
Method A: Using DBA_FEATURE_USAGE_STATISTICS
Run:
SQL
SELECT name, detected_usages, currently_used, last_usage_date
FROM dba_feature_usage_statistics
ORDER BY name;
Show more lines
· name: Feature name (e.g., Partitioning, Advanced Compression).
· detected_usages: How many times Oracle detected usage.
· currently_used: Whether it’s currently in use.
· last_usage_date: Last time it was used.
Method B: Using V$OPTION
Run:
SQL
SELECT parameter, value FROM v$option;
Show more lines
· Shows which options are installed and enabled (not necessarily used).
Method C: Oracle Enterprise Manager
· Navigate to Database → Features Usage report for a GUI-based view.
Step 2: Identify Management Packs
Check:
SQL
SELECT * FROM dba_feature_usage_statistics WHERE name LIKE ‘%Pack%’;
Show more lines
Common packs:
· Diagnostics Pack
· Tuning Pack
· Data Masking Pack
· Database Lifecycle Management Pack
Step 3: Can You Delete Historical Evidence?
· No, you cannot legally delete or alter historical usage evidence in Oracle tables like DBA_FEATURE_USAGE_STATISTICS.
Oracle LMS (License Management Services) uses this data for audits.
· Tampering with these records violates Oracle’s license agreement and can lead to compliance issues.
· The correct approach:
o Disable unlicensed options (e.g., via ALTER SYSTEM SET or by not using related features).
o Document and ensure future compliance.
o If accidental usage occurred, Oracle recommends working with LMS to resolve.
Summary:
· Use DBA_FEATURE_USAGE_STATISTICS and V$OPTION to identify installed and used features.
· Do not delete historical evidence—focus on disabling and preventing future use.
4. Prerequisites for Migrating to Oracle Cloud Infrastructure (OCI)
1. Assess Current Environment
· Inventory your assets:
o Oracle Database versions, options, and packs.
o Applications and middleware (WebLogic, OBIEE, etc.).
· Check compatibility:
o OCI supports Oracle DB versions 11gR2, 12c, 18c, 19c, and 21c.
o Ensure your OS and application stack are supported.
2. Licensing & Compliance
· Decide between:
o Bring Your Own License (BYOL): Use existing Oracle licenses.
o License Included (LI): Pay for licenses as part of OCI subscription.
· Validate:
o Database options and packs you use (Partitioning, Advanced Compression, etc.).
o Middleware licenses (WebLogic, BI).
3. Networking & Security
· Set up OCI tenancy and compartments.
· Plan:
o VCN (Virtual Cloud Network) with subnets.
o VPN or FastConnect for secure connectivity.
· Configure IAM policies for access control.
4. Migration Strategy
· Choose approach:
o Lift & Shift (VM migration).
o Replatform (move DB to OCI DB service).
o Refactor (cloud-native redesign).
· Tools:
o OCI Database Migration Service.
o RMAN, Data Pump, or GoldenGate for data migration.
5. Storage & Backup
· Plan for:
o Block storage for compute.
o Object storage for backups.
· Configure Data Guard or OCI Backup Service for disaster recovery.
6. Performance & High Availability
· Decide on:
o OCI Autonomous Database vs. OCI DB System.
o HA options: RAC, Data Guard, Exadata Cloud Service.
7. Compliance & Governance
· Ensure:
o GDPR, SOC, HIPAA compliance if applicable.
o Audit policies and monitoring via OCI Logging & Monitoring.
Important:
Before migration, run Oracle Cloud Advisor and OCI Migration Planner to validate readiness.
This round of testing shows how far AI tools have progressed in understanding Oracle licensing, and also where important gaps remain. Claude Sonnet 4.5 and Co-Pilot GPTS delivered the strongest overall performance, providing clear and mostly accurate guidance across Java, WebLogic, Database Options and Packs, and OCI migration requirements.
Oracle licensing often hinges on versioning, usage evidence, policy exceptions, and cloud prerequisites that require context AI tools cannot yet apply. Used correctly, AI can complement internal research, but it is not a substitute for informed decision making or a structured licensing
