Oracle AI Database 26ai LTS, Free/Developer Learning Paths, Licensing Awareness, and Feature Boundaries

Learning outcomes

ServiceHub’s proof of concept works, and a manager asks a deceptively simple question: “We tested this in Oracle Free; can production use the same features?” A technically correct answer cannot come from a feature checkbox alone. Oracle AI Database has a product brand, release-update numbers, a COMPATIBLE setting, multiple offerings, and separately governed options and management packs. The goal of this lesson is not to memorize a licensing table. It is to learn how to build an evidence trail that survives product changes.

1. Product name, RU, and COMPATIBLE are three different facts

Oracle AI Database 26ai is the product/release branding used by Oracle. Current software updates in this generation report version numbers in the 23.26.x train. A Release Update (RU) is a bundled maintenance level that contains fixes and can introduce release-update-specific behavior. Your installed Oracle Home and database SQL registry can also have patch state that must be inspected directly.

The initialization parameter COMPATIBLE is different again. It gates compatibility-sensitive on-disk and feature behavior; raising it can be consequential and can affect downgrade possibilities. Never infer COMPATIBLE from a marketing name or set it merely to make a feature appear. Query it and compare the result with the feature’s current documentation.

SELECT banner_full FROM v$version;SELECT instance_name, version, version_fullFROM   v$instance;SELECT value AS compatibleFROM   v$parameterWHERE  name = 'compatible';SELECT action_time, action, status, description, source_version, target_versionFROM   dba_registry_sqlpatchORDER  BY action_time DESCFETCH FIRST 10 ROWS ONLY;

The first three queries establish runtime identity. DBA_REGISTRY_SQLPATCH records SQL-side patch application history when applicable. A version string does not prove that every Oracle Home in a fleet is at the same level, nor does it prove that datapatch completed successfully after binary patching. Chapter 28 will treat those lifecycle mechanics in depth.

2. Oracle AI Database Free is a learning/runtime offering—not a “Developer Edition”

Oracle’s current free offering is Oracle AI Database Free. Do not rename it “Oracle Developer Edition” by analogy with another database vendor. Oracle publishes explicit limits: up to two CPUs for foreground processing, 2 GB RAM across SGA and PGA, 12 GB of user data, and one Free installation per logical environment. The software can be deployed without an environment restriction, including production, but Oracle states that Free is unsupported and receives no patches, including security patches. That makes it a good mandatory learning baseline and a poor default recommendation for an Internet-facing production database.

The Free limitation is especially important in later performance chapters. A query that spills under a 2 GB combined memory ceiling does not prove that the same plan will spill on a production server, and a fast Free result does not prove that a larger system will scale linearly.

3. Editions, offerings, options, and packs are a live matrix

Oracle licensing is not accurately represented by one axis called “edition.” Current documentation distinguishes Free, Standard Edition 2-related deployments, Enterprise Edition, engineered-system configurations, and OCI database service offerings. Enterprise deployments can have separately licensed options and management packs. Cloud offerings may bundle capabilities differently. Historical rules also change, so an old blog post or a remembered 19c matrix cannot settle a 26ai production decision.

Examples you will meet later include RAC, Active Data Guard, Partitioning, Advanced Compression, Database In-Memory, Advanced Security, Diagnostics Pack, and Tuning Pack. The exact entitlement depends on the current offering. Some capabilities visible or included in Free can still be extra-cost in an Enterprise Edition production deployment. That counterintuitive fact is why feature availability and entitlement must be separate columns in your design record.

4. Deliberately wrong approach: “V$OPTION says TRUE, so we own it”

A DBA queries V$OPTION, finds a feature whose value is TRUE, and concludes that the company may use it in production. That conclusion is unsafe. V$OPTION is technical build information; it is not a contract interpreter. Likewise, being able to query an AWR-related view or call a package does not prove that a Diagnostics or Tuning Pack is licensed for the current offering.

SELECT parameter, valueFROM   v$optionWHERE  parameter IN ('Partitioning', 'Real Application Clusters');SELECT valueFROM   v$parameterWHERE  name = 'control_management_pack_access';

The second query is also not a license receipt. CONTROL_MANAGEMENT_PACK_ACCESS controls access to management-pack functionality; the correct production decision combines the current licensing guide, your organization’s actual contract/offering, configured access, and feature-use evidence. The repaired pattern is therefore: observe → identify offering → check current license documentation/contract → approve or reject → record decision.

5. Tool versions are independent of the database RU

SQL Developer, SQLcl, SQL*Plus/Instant Client, JDBC, ODP.NET, python-oracledb, and node-oracledb have independent release cycles. A database at one RU can be contacted by multiple supported client versions, subject to Oracle’s compatibility matrices. When a lab uses a client-specific command, record the client version instead of attributing that behavior to the server.

-- From the operating-system shell:sql -version-- Then connect and run server-side SQL:SELECT banner_full FROM v$version;SELECT value AS compatible FROM v$parameter WHERE name = 'compatible';

At the August 2026 review baseline, SQL Developer 26.2 and SQLcl 26.2.1 are current Oracle releases. That sentence will age faster than SQL semantics, so every future chapter prompt explicitly requires a current-tooling check.

6. Hands-on lab: make a version and entitlement evidence card

Create a small text record for the ServiceHub lab. Do not enable or disable any option. Run read-only queries and copy the values exactly as returned.

SELECT systimestamp AS observed_at FROM dual;SELECT banner_full FROM v$version;SELECT instance_name, host_name, version_full FROM v$instance;SELECT value AS compatible FROM v$parameter WHERE name='compatible';SELECT sys_context('USERENV','CON_NAME') AS con_name,       sys_context('USERENV','SERVICE_NAME') AS service_nameFROM dual;SELECT comp_id, comp_name, version_full, statusFROM   dba_registryORDER  BY comp_id;

Add these non-SQL fields manually: deployment type (Free/native, Free/container, Live SQL, or other), host OS/container image identifier, SQLcl version, SQL Developer version if used, and whether a production license decision is in scope. For any feature you plan to use, write “technical presence observed” and “entitlement verified” as separate yes/no/not-applicable fields.

Verification checklist:

• The evidence card has an exact RU/version and a separately observed COMPATIBLE value.
• It names the actual Oracle offering instead of “Developer Edition.”
• If it is Free, it records the 2 CPU / 2 GB RAM / 12 GB user-data learning limits and no-patch/no-support status.
• It records client/tool versions separately from the server.
• No line claims that technical feature presence proves license entitlement.

7. Production judgment

Version control and licensing control belong in architecture review, not after deployment. Pin the Oracle Home/RU you tested, document the intended offering, capture COMPATIBLE, record required options/packs, and list the client drivers/tools that the application depends on. For cloud services, capture the exact service tier because bundled capabilities can differ from on-premises EE. For engineered systems, record that topology explicitly instead of treating it as generic EE.

When a later chapter mentions AWR, RAC, Active Data Guard, Partitioning, TDE, In-Memory, sharding, or AI functionality, repeat the entitlement and release-status check. “It worked in Free” is a technical observation, not a production purchasing conclusion.

8. Summary and next step

Oracle AI Database 26ai is the product generation; 23.26.x identifies current RU levels; COMPATIBLE is an independent database setting. Oracle AI Database Free is the course’s preferred local engine, with strict resource limits and no patch/support stream. Production features must be checked against the current offering/licensing matrix, and client tools have their own version lifecycle. Lesson 3 now applies these boundaries to self-managed servers, containers, OCI services, Autonomous AI Database, and Exadata.

Authoritative references

• Oracle AI Database Licensing Information User Manual — current offerings, options, packs, and permitted features
• Oracle AI Database Free FAQ — Free resource limits, support, patching, and production guidance
• Oracle AI Database Free licensing restrictions — CPU, RAM, data, and installation limits
• Oracle AI Database Free Quick Start — current 26ai Free packages and container image
• Oracle SQL Developer Downloads — current SQL Developer release
• Oracle SQLcl Downloads — current SQLcl release