Oracle's Spatial claim almost always rests on one view (DBA_FEATURE_USAGE_STATISTICS) that Oracle's own bug notes admit misfires on Locator. This page gives you the concrete artifacts (usage logs, application configuration, function inventory) to rebut the claim and cap exposure at zero.
There Is No EBS Licence: Only Lines
Session 1 of the Oracle EBS Licensing Series. Oracle E-Business Suite is licensed module by module, each with its own metric, and the metric you accept at purchase governs your cost for a decade. The foundation session: why the module is the entitlement, why support is 72 percent of the ten year bill, and why the database underneath is usually the bigger number.
Oracle's Spatial claim almost always rests on one view (DBA_FEATURE_USAGE_STATISTICS) that Oracle's own bug notes admit misfires on Locator. This page gives you the concrete artifacts (usage logs, application configuration, function inventory) to rebut the claim and cap exposure at zero.
In 25 years of taking Oracle claims apart, the Spatial finding is one of the softest lines LMS ever puts in front of a customer. It is soft for a structural reason and a technical reason. Structurally, the option that Oracle is trying to bill you for (list price historically $17,500 per processor and $350 per Named User Plus, per House of Brick's March 2018 pricing) was folded into the base database on December 5, 2019 with no price increase. Technically, the detection query Oracle relies on cannot tell Locator (free) from Spatial (formerly chargeable), and Oracle has documented that defect in its own support notes for over a decade.
The distinction you are defending is a packaging boundary, not a functional one. Locator is documented as a feature of Standard Edition that provides core spatial services but is not designed for full GIS workloads. Spatial adds named feature families on top. Your evidence pack does not need to prove a negative in the abstract. It needs to prove three concrete things: (1) the flagged rows are Locator or metadata artifacts, (2) no Spatial-only function ran, and (3) the configuration itself forecloses Spatial use. If you want the underlying licensing model first, read our Oracle Spatial and Graph licensing buyer guide and the feature-by-feature breakdown in Oracle Locator vs Spatial.
Oracle's own bug note concedes that a query against the view is not a true test for use of SDO. That single admission moves the burden of proof back onto LMS.
Every Spatial claim starts with DBA_FEATURE_USAGE_STATISTICS. This is the data source behind Oracle's options_packs_usage_statistics.sql script, and it is the single most disputed view in Oracle auditing. Oracle's own guidance (Doc ID 1317265.1) states the report 'is to be used for informational purposes only and this does not represent your license entitlement or requirement.' Put that sentence in your first written response. It is Oracle's own disclaimer, and it prevents LMS from treating the script output as proof.
Do not accept a flagged row at face value. Build a triage file that maps every row to a disposition. The columns that matter are DETECTED_USAGES, TOTAL_SAMPLES, CURRENTLY_USED, FIRST_USAGE_DATE, LAST_USAGE_DATE, and AUX_COUNT. Two dispositions turn a liability into a challengeable row:
Build this file now, before the audit call, not during it. The mechanics of how a benign row gets misread are covered in accidentally using Oracle Spatial, which walks through the exact feature-usage finding you did not buy.
When LMS asserts multi-year unlicensed Spatial usage, they are almost always extrapolating from a handful of sample windows. DBA_FEATURE_USAGE_STATISTICS is populated by AWR-style sampling on a weekly cadence, not by continuous metering. DETECTED_USAGES counts the number of times the sampler detected activity, and TOTAL_SAMPLES tells you how many samples were taken. Oracle cannot prove from these columns that a feature was in production service across the whole claimed period. It can only prove the feature was touched during certain sample windows.
This matters for the number. If LMS bills 36 months of processor licensing off a feature that DETECTED_USAGES shows was touched in two sample windows, the burden of showing continuity sits with them, and the sampling cadence undercuts it. In my experience, forcing LMS to justify the claim period (rather than accepting their default of 'from first detection to now') routinely removes 60 to 90 percent of a proposed back-support figure even before you win the Locator argument itself.
DETECTED_USAGES proves a feature was touched during a sample window. It does not prove production service across a multi-year period. Make LMS carry that burden.
The most common Spatial audit trigger is not real Spatial use at all. It is metadata. The LMS query identifies all geospatial objects for both Locator and Spatial and Graph, and it cannot distinguish between them. House of Brick documented this directly (March 2018): the query 'has the potential to flag false positives for licensed features if you are using only Locator.' If this happens during an audit, you explain that only Locator is in use and Spatial does not need to be licensed.
Two concrete artifacts prove the point. First, an ORACLE SPATIAL INSTALLED: TRUE line looks alarming but proves nothing about use. AMIS documented (January 2021) that if the ALL_SDO_GEOM_METADATA count returns 0, Spatial is not being used, even when the installed flag reads TRUE. Capture that count. Second, MDSYS audit-trail entries can appear with no Spatial or GeoRaster use at all (Oracle Support Doc 1338587.1, February 2022). If LMS points to MDSYS audit records, that document is your rebuttal.
| What LMS flags | What it looks like | What it actually proves | Your evidence |
|---|---|---|---|
| ALL_SDO_GEOM_METADATA row present | Spatial 'in use' | Only that geometry metadata exists (Locator uses this too) | Row count and object owner (SYS/MDSYS vs app schema) |
| ORACLE SPATIAL INSTALLED: TRUE | Spatial licensed | Component installed, not used | ALL_SDO_GEOM_METADATA count = 0 |
| MDSYS audit records | Spatial activity | Internal MDSYS auditing, no user Spatial call | Doc 1338587.1; audit policy config |
| SDO_AGGR_MBR usage | Spatial function | Locator-licensed aggregate operator | Spatial Database Advisor licensing note |
This is the artifact that wins the argument on the merits. You produce an inventory that shows which Spatial functions your application actually calls, and demonstrate that none of them fall inside the chargeable roster. The chargeable feature families are named and finite. Spatial added Geocoder, GeoRaster, Network Data Model, Topology, Spatial Analytic Functions, and the Routing engine in Oracle 10g, then added 3D Support and Web Services in 11g. If none of these run, you are on Locator.
Two traps to handle head-on. First, do not let LMS treat core operators as Spatial. SDO_AGGR_MBR is explicitly licensed for use in Locator (Spatial Database Advisor, November 2020), so its presence in your call log is evidence of Locator, not against it. Second, the real accidental-Spatial risk sits inside the SDO_GEOM package: several geoprocessing functions in that package are Enterprise-Edition-only. Standard Edition sites can drift into these without knowing. Your function inventory must specifically enumerate SDO_GEOM calls and confirm they are the Locator-licensed subset.
If your estate runs on Standard Edition 2, the ceiling on what you can even do is your friend here. See Oracle Spatial on Standard Edition 2 for what works and what cannot be licensed at all on that edition.
The strongest configuration evidence is a database where Spatial is not installed at all, only Locator. Oracle documents the exact procedure: Note 1070647.1 ('How To Deinstall Oracle Spatial Keeping Oracle Locator'), executed via mddins.sql, which manually removes Spatial and leaves only Locator. Running this ensures you can use only features available in Locator and none that are available only with Spatial. If you have done this, capture the deinstall log, the resulting component status, and the date. That artifact forecloses the entire claim: you cannot use a component that is not installed.
For estates you cannot deinstall (active GIS workloads that genuinely need Spatial), the analysis shifts from defense to entitlement, and the metric choice drives the bill. Work through processor versus Named User Plus for a GIS estate before you concede any position.
Effective December 5, 2019, Oracle Spatial and Graph was included with Oracle Database (Enterprise Edition and Standard Edition 2) with no price increase. Oracle removed Spatial from the price list, which House of Brick (June 2022) reads as evidence it is no longer separately purchasable. For any database at 19c or later, the 'included' status is your headline defense. LMS cannot bill you for an option that ships with the license you already hold.
There is one trap. The 'included' status is version-conditional in the binding documents. Only the 19c program documentation clearly states Spatial and Graph is included. Program documentation for earlier versions has not been updated. From a purely contractual standpoint, an 'included license' cannot be assumed for a pre-19c estate. So if LMS is auditing a 12c or 18c database, do not lean on the 2019 change alone. Combine it with the Locator-only function inventory and the metadata rebuttal, because the technical proof (no Spatial use) holds regardless of version, while the 'included' argument only holds cleanly from 19c forward.
This also creates a cleanup lever going forward. At 23ai or 26ai migration, audit Spatial and Graph usage and retire any separately licensed Spatial that is not actually used, then capture the support reduction (Redress Compliance, May 2026). The graph side of that story, and what happened to the graph license specifically, is covered in from Spatial and Graph to 23ai.
Order matters. In a live audit, present the artifacts in the order that requires LMS to concede first: (1) Oracle's own informational-only disclaimer on the report, (2) the metadata false-positive rebuttal with your ALL_SDO_GEOM_METADATA = 0 evidence, (3) the row triage file with AUX_COUNT and schema-owner dispositions, (4) the sampling-cadence argument to cap any surviving claim period, (5) the function inventory proving no Spatial-only call, and (6) the zero-exposure configuration proof if you deinstalled. For estates at 19c and later, lead the written response with the December 2019 inclusion and treat the rest as reinforcement.
Every one of these artifacts should exist before the audit call, not be assembled under time pressure while LMS controls the clock. For the broader response architecture, see our Oracle audit defense strategy and the tactical detail in 22 Oracle license audit secrets. Assembled correctly, a Spatial claim is one of the few Oracle findings you can genuinely take to zero.
No. That flag only means the component is installed, not used. The controlling evidence is the ALL_SDO_GEOM_METADATA count: if it returns 0, Spatial is not in use (AMIS, January 2021). Capture that count and present it. Installation alone is not a licensable event.
Because Oracle itself says not to. Doc ID 1317265.1 states the report is informational only and does not represent your license entitlement. Separately, Oracle's bug notes (Doc ID 1309070.1) document false positives where only Locator is used, and concede a query against the view is not a true test for use of SDO. The view triggers the conversation; it does not settle it.
Effective December 5, 2019, Spatial and Graph is included with Oracle Database at no extra cost, and it was removed from the price list. For a 19c-or-later estate this ends the claim. The trap is that only 19c program documentation confirms inclusion; pre-19c documentation was not updated, so for older databases you must also prove Locator-only use technically.
The chargeable feature families are named: Geocoder, GeoRaster, Network Data Model, Topology, Spatial Analytic Functions, Routing, 3D support, and Web Services, plus specific geoprocessing functions in SDO_GEOM. Core storage, spatial indexing, and operators like SDO_AGGR_MBR are Locator-licensed. Your function inventory must show that no chargeable function ran.
Use the sampling cadence. DETECTED_USAGES only proves a feature was touched during specific sample windows, not that it ran continuously across years. Force LMS to justify the full claimed period; the burden of proving continuity sits with them, and the sampling cadence undercuts a multi-year assertion built on a few detections.
A deinstall of Spatial that keeps Locator, run per Oracle Note 1070647.1 via mddins.sql. This leaves only Locator features installed and forecloses the entire claim because you cannot use a component that is not present. Keep the deinstall log, resulting component status, and the date as your artifact.
The strategic framework for Oracle audit defense across LMS, license verification, and contractual response. Beyond the tactical playbook.
Gated with a work email on the download page. No sales follow up you did not ask for.
Get the White Paper →
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One buyer side briefing a week. Renewal signals, audit moves, and the levers that work. No vendor spin.
