Franck PachotDatabase Developer Advocate
All minibooks
Database field guide · 28
Editions, options, metrics, and evidence
Build an evidence-based Oracle licensing inventory from contracts, deployed editions, enabled options, infrastructure metrics, and actual feature use.
Build the mental model before choosing the mechanism.
This minibook was AI-generated from Franck Pachot's archived blog posts. Links to the original articles are included for source context and verification.01
Technical views reveal deployment and use, but licenses are legal rights defined by orders, agreements, metric definitions, and support history. Product behavior cannot interpret a contract by itself.
02
Enterprise Edition is a prerequisite for many separately licensed options, while Standard Edition has a different included feature set and infrastructure metric. A database version string alone does not establish entitlement.
03
Processor, named-user, socket, OCPU, and cloud-provider policies count different things. Virtualization and host mobility can expand the infrastructure considered licensable beyond one virtual machine.
04
Feature-usage views, option banners, installed components, parameters, and workload evidence answer different questions. False positives and historical use require version-aware interpretation.
05
Operations that look like ordinary DDL may invoke separately licensed capabilities depending on edition, release, and syntax. Compression and multitenant limits illustrate why deployment review must reach object definitions and operations.
06
A defensible process inventories entitlements and deployment, detects drift, reviews planned changes, records decisions, and repeats after patching, scaling, failover, or acquisition.
07
Concrete mechanics, diagnostic evidence, and executable patterns to carry into a real system.
Record the database banner, installed options, components, and pluggable database topology. This is technical evidence, not a licensing conclusion.
SELECT banner_full FROM v$version;
SELECT parameter, value FROM v$option ORDER BY parameter;
SELECT comp_name, version, status FROM dba_registry ORDER BY comp_name;DBA_FEATURE_USAGE_STATISTICS includes detection counts, dates, and auxiliary details. Interpret each row with release-specific documentation and actual workload evidence.
SELECT name, detected_usages, first_usage_date, last_usage_date,
currently_used, feature_info
FROM dba_feature_usage_statistics
WHERE detected_usages > 0 ORDER BY name;A licensing inventory needs host, cluster, virtualization, cloud shape, mobility, and disaster-recovery context in addition to database facts.
database -> Oracle home -> VM or container -> physical host -> cluster
-> cloud instance shape -> region/DR role
# Attach source, collection time, and entitlement metric to every edge.Evaluate new options, topology changes, failover targets, scaling, and cloud migration before activation, then retain the approved evidence with the change record.
1. State requested capability and edition.
2. Identify included or separately licensed dependencies.
3. Map affected infrastructure and metrics.
4. Obtain contractual review.
5. Deploy, rescan, and archive evidence.08
Optional deep dives with the complete experiments and product-version context behind this guide.