Oracle Spatial and Graph Licensing 2026

Spatial and Graph is the rare Oracle option whose licensing got cheaper rather than more expensive, but the change created its own trap: estates assume that because Spatial is free on current releases it was always free, and historical usage on older databases still carries a recorded obligation. This article sets out what Spatial covers, exactly when and how its licensing changed, and where a buyer side estate still needs to watch for exposure. It sits under the database licensing pillar and belongs with the options and packs reference.

What is Oracle Spatial and Graph?

Spatial and Graph is the database capability for storing, indexing, and querying geographic and geometric data, together with graph data models for network and relationship analysis. It powers location services, asset mapping, logistics routing, telecommunications network modelling, and similar workloads where the data has a spatial or connected structure. The feature set includes geometry types, spatial indexing and operators, network data models, raster and topology support, geocoding, and routing.

For most of its history this full feature set was an Enterprise Edition only priced option, sitting alongside Partitioning and the other catalogue entries. What changed was not the technology but the commercial packaging.

How Spatial licensing changed at 19c

From Oracle Database 19c, Oracle folded Spatial and Graph into the base database at no additional licence cost, making it available with both Enterprise Edition and Standard Edition 2. The advanced features that previously required the priced option became included capabilities. For estates standardised on 19c or later, Spatial is simply part of the database and carries no separate charge.

This is genuinely good news, but it changes the licensing question from how much to pay to whether any historical liability remains, because the option's removal from the price list does not erase the usage that was recorded while it was still chargeable.

Locator versus the Spatial option

Locator has always been a free subset of spatial functionality, included with every database regardless of edition. It provides basic geometry types and the core spatial operators sufficient for simple proximity and containment queries. The full Spatial option historically added the advanced layer: network data models, raster and topology, geocoding, and routing.

On pre 19c releases the line between Locator and the full option was a commercial boundary, and using an advanced feature crossed it into chargeable territory, exactly the kind of narrow boundary that governs the Enterprise Edition option set generally. On 19c and later the boundary lost its price significance because the advanced features became free, though the feature usage views still record which capability ran.

Where legacy Spatial charges linger

Two situations keep Spatial relevant to a current licence position. The first is databases still running releases before 19c, where the full Spatial option remains chargeable and any advanced feature usage is a live obligation. The second is contracts and support agreements written during the priced era that still itemise Spatial, where the line may persist on a renewal quote even though the feature is now free on current releases.

A third, subtler case is an estate that ran chargeable Spatial features on an older release and has since upgraded to 19c. The historical usage record persists, and an auditor can assert an obligation for the period the database ran the older version. Untangling these cases is part of the options audit discipline.

How Oracle detects Spatial usage

Detection works through the database feature usage statistics views and the component registry. The feature usage views record each Spatial capability that has executed, with first and last usage dates, and those dates survive upgrades. The component registry shows whether Spatial is installed. Oracle's audit scripts read both, so an auditor sees not only that Spatial is present but which features ran and when.

On a database upgraded from a pre 19c release, this is the mechanism that exposes historical usage. The usage that occurred while the option was chargeable is still in the views, dated to the period the older release was running, and the same core factor arithmetic that governs every option determines the size of any asserted obligation.

Spatial licensing by database release

How to contain Spatial exposure

Containment is largely a matter of release hygiene and record review. Estates standardised on 19c or later carry no current Spatial charge and only need to confirm no legacy line is being carried forward on support renewals. Estates still running pre 19c databases should query the feature usage views to confirm whether any chargeable Spatial feature ran, and either license it, retire the feature, or prioritise the upgrade to a release where it is free.

For databases recently upgraded from older releases, the historical usage record should be reviewed and documented so that any audit assertion about the pre upgrade period can be answered with facts rather than guesses. Reconstructing that history accurately is the kind of work the database licensing service performs, and it is far easier done proactively than under audit defence.

The buyer side view

The buyer side position on Spatial and Graph is to capture the saving on current releases while not assuming the past was free. Confirm that no legacy Spatial line survives on support renewals, prioritise upgrades that move chargeable usage onto a release where the feature is included, and document historical usage on any database that ran a pre 19c version so an audit cannot assert an unanswered obligation. Treated this way, Spatial is a cost that has largely disappeared, provided the estate proves it. Start from the database pillar, run the options audit against your feature usage views, and where legacy usage is unclear request a consultation. For a related scenario, see backup server licensing.