Oracle Locator vs Spatial: Which Features Are Free and Which Trigger a Bill

The functional line between free Locator and the paid Spatial option collapsed on 5 December 2019, and most buyers are still negotiating, auditing, and paying against a rulebook that no longer exists. This page shows exactly where the money now sits: contract vintage, external server products, support shelfware, and LMS scripts that cannot tell Locator from Spatial.

The Line You Are Looking For No Longer Exists

If you came here for a function-by-function map of what Locator gives you free and what tips you into a paid Spatial bill, stop. That map was retired on 5 December 2019, when Oracle folded Advanced Analytics and Spatial and Graph into the database itself: included with Enterprise Edition, Standard Edition 2, Personal Edition, and Database Cloud Service Standard and Enterprise, for database version 11.2 and higher, with no increase to the price of Database licenses or DBCS subscriptions. That is Oracle's own language in its licensing change FAQ, not a reseller's interpretation. The strongest artifact is not the announcement, though, because announcements are marketing. It is the 19c Spatial Developer's Guide, whose "Changes in This Release" notes state plainly that all Spatial and Graph capabilities are available with both Enterprise Edition and Standard Edition 2, and that references to Oracle Locator, including every Locator versus Spatial distinction, have been removed from the manual. Oracle deleted the boundary from its own documentation. Anyone still architecting around SDO_GEOM function inventories, or still refusing a linear referencing call because a 2013 blog post said it was EE-only, is spending engineering hours defending a wall that Oracle demolished.

Oracle deleted the Locator versus Spatial boundary from its own documentation, which is exactly why buyers should stop reading function lists and start reading their ordering documents.

The practical instruction for your team is a redirect, not a lookup. Pull your ordering documents, your CSIs, and the program documentation for the specific database version you actually run, and read those. The bill in 2026 comes from contract vintage, from support you never cancelled, and from external server products that Oracle sells alongside the database. It no longer comes from which geometry function your developer typed. Our Spatial and Graph licensing buyer guide covers the audit posture in detail.

What the Old Paid Line Actually Was, and Why It Still Matters

You still need the historical baseline, because Oracle's audit scripts, its sales talk tracks, and your own aged estates all run on it. Before December 2019, Locator shipped as a Standard Edition feature covering core spatial services, and Oracle's 12.1 documentation was explicit that it was not designed for GIS applications requiring complex spatial data management. Anyone needing linear referencing, advanced geoprocessing, or Spatial web services was pointed at the priced option. Spatial and Graph was Enterprise Edition only, listed at $17,500 per processor and $350 per Named User Plus on the technology price list. Three traps from that era still generate findings on estates that have never been remediated: Standard Edition sites calling EE-only geoprocessing functions inside SDO_GEOM; Oracle XE shipping the complete SDO_GEOM package, which made accidental use trivially easy; and the restriction on a given SDO_GEOM function extending automatically to its equivalent ST_* function in the SQL/MM (OGC) type library, so renaming the call changed nothing. In our audit-defense work, that ST_* equivalence is the single most common thing a customer engineer does not know.

One asymmetry survived into 12c and is worth knowing before you argue it: SDO_GEOM.SDO_LENGTH on an XYZ linestring returns 2D length for Locator users and slope length for Enterprise users. That is a data-correctness issue, not a licensing one, and it is the kind of detail that separates a credible buyer-side position from a nervous one. Keep the old line in your file for one reason only: when an Oracle representative quotes a pre-2019 rule at you, you want to name the exact document they are citing and the exact date it stopped governing your estate. The same pattern shows up elsewhere in the stack, where free features sit one keyword away from licensed ones.

The Contract Vintage Trap: 19c Is Documented, 12c Is Not

The biggest live exposure in 2026 is not code, it is paperwork. Oracle's 19c Spatial Developer's Guide states plainly that all Spatial and Graph capabilities are available with both Enterprise Edition and Standard Edition 2, and it deleted the Locator comparison material outright. That is program documentation, which means it is incorporated by reference into your license agreement and is contractual evidence you can put in front of an auditor. The 12c program documentation says the opposite: Spatial and Graph is listed as an option that "can be purchased with Oracle Database Enterprise Edition." Oracle never retroactively republished the 11.2, 12.1, 12.2 or 18c documentation sets to match the December 5, 2019 announcement. So if you are running an older release, the only artifacts supporting free use are an Oracle blog post and an FAQ page, and neither is contractually binding. In a dispute, LMS will read your ordering document and the program documentation for the version you deployed, in that order, and the FAQ will not appear in either.

Treat the FAQ as evidence of Oracle's intent, not as a grant of rights. Intent is useful in a commercial negotiation and close to worthless in a contractual one. If you are on 11.2 through 18c and you are about to deploy SDO_GEOM geoprocessing, geocoding, or network data model functions beyond the historic Locator subset, do the following before the first index gets built.

• Get the inclusion written into an amendment or a new ordering document naming your specific database versions and CSIs, not a sales email.
• Archive the FAQ page and the 19c documentation page with timestamps, so the intent record survives Oracle's next site refresh.
• Where an amendment is refused, upgrade the affected instances to 19c or later and let the documentation do the work.
• Cross-check the exposure model in our Oracle Spatial and Graph audit exposure guide before you respond to any LMS data request.

An Oracle blog post is evidence of intent, not a grant of rights, and LMS reads the ordering document first.

The Shelfware Trap: You Are Still Paying Support for a Free Feature

Oracle extended the inclusion benefit to new users of Spatial and Graph. It did not cancel anything for customers who had already bought it. That means several thousand estates are still paying annual support on processor licenses for functionality Oracle now bundles into every Database edition it sells. The arithmetic is unpleasant. Support runs at roughly 22 percent of the original net license fee, and Oracle's standard uplift on renewal has been running at up to 8 percent annually in the deals we have reviewed, which compounds. At the list price that applied when most of these licenses were sold ($17,500 per processor), a modest 20 processor footprint carries roughly $77,000 a year in support for a feature that is now free, and that figure grows every renewal.

Whether you can stop it depends entirely on contract structure, not on the merits. This is the same pattern we see across bundled option support, and it is why order-line hygiene matters more than discount percentage. Check your CSI structure before you ask Oracle anything.

If you bought Spatial and Graph after December 2019, or in the months immediately before it while Oracle's own product teams knew the change was coming, open a refund or credit conversation now and put the inclusion date in writing. Oracle will not volunteer it. For bundled orders, stop treating termination as the goal: the realistic win is converting that dead line item into leverage on the next renewal, alongside the same discipline you would apply to other options that sit one keyword away from a licensed feature. Audit your CSI list this quarter and identify every Spatial line still drawing support.

Where the 2026 Bill Actually Comes From: The Execution Boundary

Stop hunting for a function list. The old test (which SDO_ package you called) died with the 5 December 2019 change, and Oracle's own 19c Spatial Developer's Guide removed the Locator comparison from the manual entirely. The test that survives is architectural: does the workload execute inside the database process, or does it execute in a separate server that you installed and started yourself? In-database SQL against SDO_GEOMETRY, spatial indexing, coordinate transformation, raster and topology is included with a licensed Database (Enterprise Edition, Standard Edition 2, or the Database Cloud Service tiers) and carries no incremental fee. The moment analysis moves out of the SGA and into Oracle Graph Server and Studio, Property Graph In-Memory Analytics (PGX), or Spatial Studio, you are running products that are not part of Oracle Database, that Oracle ships with their own installers, and that Oracle prices and audits separately. Oracle's own FAQ confirms the separate-installation status of Spatial Studio and PGX while carefully framing it as unrelated to the licensing change. On OCI, Spatial Studio is a separately priced cloud service layered on top of Autonomous Database or DBCS, so provisioning it inside a tenancy that already pays for the database does not make it inclusive.

• Treat any component with its own installer, its own port, its own service account, or its own OCI provisioning flow as billable until you have written confirmation otherwise, and keep that confirmation with the order document, not in an email thread.
• Put deployment governance where the risk is: block unapproved installs of Graph Server, PGX and Spatial Studio at the build-pipeline and OCI service-limit level, because a developer download is faster than any contract review.
• Record the execution boundary in your architecture register, and pair it with the entitlement evidence described in our Oracle Spatial and Graph licensing buyer guide before Oracle asks.
• Expect sales and LMS to conflate the free in-database feature with the paid external product, and rebut with the deployment inventory rather than a functional argument.

If it required its own installer or its own OCI provisioning, assume it bills until proven otherwise.

Free Is Not Equivalent: The SE2 Performance Catch

Inclusion is not parity, and buyers who read the December 2019 change as a licence-avoidance route to Standard Edition 2 usually discover the difference in production rather than in procurement. Oracle's own OAA/OSG FAQ states plainly that SE2 does not support parallel operations, so Machine Learning, Graph and Spatial features execute serially. For a mapping estate that means large raster processing, bulk geocoding, and spatial joins across multi-million-row geometry tables run on a single execution path no matter how many cores the host has. In our experience negotiating and remediating these estates, that is the point where the saving reverses: teams answer serial execution with bigger hardware, longer overnight batch windows that start colliding with the business day, or an unplanned migration to Enterprise Edition negotiated under time pressure, which is the worst possible position for discount. Note too that SE2 carries its own socket and thread limits independent of the spatial question, so the workload ceiling arrives from two directions at once. Benchmark before you commit: run your heaviest geospatial batch on SE2 with representative data volume, measure elapsed time against the current EE baseline, and price the delta in infrastructure and missed SLA before you count the licence saving.

• Test the three workloads that actually hurt: raster tiling, bulk geocoding, and spatial joins at production row counts.
• Cost the serial penalty as hardware plus elapsed batch time, then compare it against EE list, not against your current discounted EE rate.
• If EE is the likely destination, negotiate the move now while you still have alternatives, not after the batch window breaks.

Killing the Audit False Positive Before It Becomes a Finding

The mechanics here are boring, which is exactly why they generate findings. Oracle LMS collection scripts return a line reading ORACLE SPATIAL INSTALLED: TRUE alongside a row count from ALL_SDO_GEOM_METADATA, and Oracle's own guidance concedes that a value greater than zero means Spatial or Locator is in use. Read that again: Oracle's script cannot tell the two apart, and Oracle knows it cannot. Both Locator and Spatial register spatial metadata identically, both populate the same dictionary views, and both light up the same feature flag. The standard geospatial-object query counts objects, not entitlements. What happens next in every audit I have sat through since the pre-2019 pricing era is predictable: the auditor hands you the TRUE line, declares an apparent use of a priced option, and quietly transfers the burden of proof to your application team, who now have to trace source code and prove that no call ever touched a function Oracle considered Spatial-only. That is weeks of developer time you are funding to disprove a script that was never diagnostic in the first place. Two controls kill this before it becomes a finding. First, the preventive one: run mddins.sql to deinstall Spatial and leave Locator only, rather than mdinst.sql, which installs the full option and hands the auditor a genuine positive. Second, the drafting one: never return the raw script output without a covering written response stating that the deployment is Locator-only, naming the deinstall script executed and the date, and citing your contract vintage. Silence is read as concession. The same false-positive pattern appears across the option set, as we cover in the Oracle Spatial and Graph audit exposure guide.

What to Do First

Sequence this over 90 days and do not let Oracle set the order. Days 1 to 30: pull every ordering document, amendment and CSI that names Spatial and Graph, Spatial, or Advanced Analytics, and build a single sheet mapping each licensed database to its version and its contract vintage. This is where the exposure actually sits: the 19c program documentation states the capability is included, while 12c-era documentation still lists Spatial and Graph as a purchasable option. If any production instance is below 19c, treat it as a legal question, not a technical one. Days 31 to 60: run the ALL_SDO_GEOM_METADATA row count and DBA_FEATURE_USAGE_STATISTICS queries yourself, on your schedule, and record the results before Oracle asks for them. In parallel, inventory every Graph Server, PGX and Spatial Studio installation, because those sit outside the database and outside the December 2019 inclusion. That is the execution boundary that still bills. Days 61 to 90: open the support termination or refund conversation, and open it on the separate CSIs first. Where Spatial or Advanced Analytics sits on its own order line with its own CSI, termination produces real cash savings. Where it is bundled, expect Oracle to invoke the repricing clause and tell you your fee is unchanged, which in my experience is close to a universal answer. The single highest-value action is none of the above: get the inclusion language written into your next amendment or renewal, in your own contract, rather than relying on a 2019 FAQ page that Oracle can revise or retire without telling you. A support renewal you were signing anyway costs nothing to amend.

Related advisory: the full topic guide.

Frequently asked questions

Is Oracle Spatial free in 2026?

For licensed Oracle Database users on 11.2 and higher, the Spatial and Graph functionality inside the database has been included at no additional licence cost since 5 December 2019, across Personal Edition, SE2, EE and Database Cloud Service. The caveat is documentary: only the 19c program documentation clearly states this, while older program documentation still describes Spatial and Graph as a purchasable option. Separately installed products such as Graph Server, PGX and Spatial Studio are outside that inclusion and can still bill.

What is the difference between Oracle Locator and Oracle Spatial now?

Functionally, almost nothing. Oracle removed all references to Locator, including the Locator versus Spatial and Graph feature distinctions, from the 19c Spatial Developer's Guide. The only meaningful residual difference reported is behavioural rather than commercial, such as SDO_GEOM.SDO_LENGTH returning 2D length on an XYZ linestring under Locator versus slope length under Enterprise.

Can I stop paying support on Spatial and Graph licenses I already bought?

It depends entirely on how the order was structured. If Spatial and Graph sits on a separate order with its own CSI, you can generally terminate support and take the saving cleanly. If it is bundled with other programs on one order, Oracle applies the pricing following reduction of licenses or support level clause and in the overwhelming majority of cases tells the customer the support fee stays the same.

Why does an Oracle audit script say Spatial is installed when I only use Locator?

The LMS script reports ORACLE SPATIAL INSTALLED: TRUE and counts rows in ALL_SDO_GEOM_METADATA, and that metadata view is populated by Locator usage as well as Spatial usage. Oracle's own guidance acknowledges a non-zero count means Spatial or Locator. Rebutting it requires your application team to evidence which functions were actually invoked, which is why running mddins.sql to deinstall Spatial in advance is the cleaner control.

Does Spatial work the same way on Standard Edition 2 as on Enterprise Edition?

Not in performance terms. SE2 does not support parallel operations, so Spatial, Graph and Machine Learning features run serially. For large geocoding, raster or spatial join workloads that difference can be significant, so benchmark before treating SE2 inclusion as a licence-avoidance strategy.

What should I do if I bought Spatial and Graph recently?

Raise a refund or credit conversation with your account team, citing the inclusion effective 5 December 2019 and Oracle's own statement that customers receive the benefit with no increase in Database licence or DBCS subscription price. Do it in writing, before your next renewal quote is issued, and pair it with a request to add the inclusion language to your ordering document.