Since December 5, 2019, Oracle Spatial is an included feature of SE2, not a paid option. This guide draws the exact line between what SE2 can run, what runs but performs badly, and what still needs Enterprise Edition or a separate license.
Since December 5, 2019, Oracle Spatial is an included feature of SE2, not a paid option. This guide draws the exact line between what SE2 can run, what runs but performs badly, and what still needs Enterprise Edition or a separate license.
Oracle Spatial is included with Oracle Database Standard Edition 2 at no additional license cost. That has been true since December 5, 2019, when Oracle stopped selling Spatial and Graph (and Advanced Analytics) as priced options and folded the functionality into the base database license. Before that date, Spatial and Graph was an Enterprise Edition only option that listed at $17,500 per Processor and $350 per Named User Plus. If you are still being told SE2 needs a separate Spatial purchase, that advice is at least six years out of date.
The trap is not licensing entitlement. The trap is execution and architecture. SE2 has no parallelism, so every Spatial operation runs serially. And several things that carry the word 'graph' or 'spatial' in Oracle's product catalog are separate products that SE2 does not include. This is where Oracle sales and LMS conflate a free in-database feature with a paid external product, and where buyers overpay or accidentally deploy something they cannot cover. For the option-level view across all editions, see our Oracle Spatial and Graph licensing buyer guide.
On SE2 the question is not 'can I license Spatial.' You already own it. The question is 'will it perform, and is what I'm building actually the free feature.'
Oracle's own OAA/OSG Licensing Change FAQ is unambiguous: all licensed users of Oracle Database EE and SE2 with active support, plus all editions of Database Cloud Service with active subscriptions, are licensed to use Spatial and Graph features. The FAQ goes further and states these are no longer options of Oracle Database at all. The functionality is now a feature of the base license. The right to use applies retroactively to Database 11.2 and higher, so an older estate is covered too.
The current 23ai era product pages restate this: Spatial is included in all editions of the database, all database cloud services, and Autonomous Database, without additional licensing cost. Oracle's SE2 FAQ lists spatial as a supported data type alongside relational, JSON, XML, and graph. This is settled ground.
One caution from long experience defending audits: blog announcements and FAQs are not contractually binding. The Licensing Information User Manual (LIUM) and the program documentation for your specific version are what govern. The 12c program documentation, for instance, still lists Spatial and Graph as a purchasable EE option, which is exactly the stale language that keeps this confusion alive. If you want a clean paper trail, capture the LIUM section for your database version that confirms Spatial inclusion, and keep the OAA/OSG FAQ as supporting evidence. Do not rely on a screenshot of a marketing page alone.
This is the single most important technical fact for SE2 buyers, and Oracle states it plainly in the FAQ: SE2 does not support parallel operations, so Machine Learning, Graph, and Spatial features execute serially on SE2. Every feature is included 'to the extent that the underlying database supports them.' You get the full Spatial feature set by entitlement, but you get none of the parallel query, parallel index build, or parallel DML that a large GIS estate depends on.
In practical terms, a spatial join across millions of geometries that would fan out across cores on Enterprise Edition runs on a single thread on SE2. Bulk spatial index creation is serial. Large partitioned spatial queries are serial. If your workload is a modest departmental GIS with a few hundred thousand features, this rarely bites. If your workload is a national dataset, a telco network model, or heavy nightly spatial ETL, the serial ceiling is the reason to price Enterprise Edition, and it is a performance decision, not a licensing one. The EE decision then interacts with core counting and the option, which is why the Enterprise versus Standard Edition comparison matters before you commit.
SE2 gives you Spatial in full. It just runs it one thread at a time. That is a benchmark you should run before you architect, not after.
There is a free performance lever most teams forget. Spatial Vector Acceleration used to require a Spatial license. Oracle removed that requirement and now only asks that the host database be licensed, on any edition including SE2, and grandfathered the change back to 12c. But it is off by default. You must set the database parameter SPATIAL_VECTOR_ACCELERATION to TRUE to get optimized spatial operator performance. Community reports confirm that now that Spatial is free, teams routinely forget to flip this on and then complain about slow spatial operators. On SE2, where you have no parallelism to fall back on, this parameter matters even more. Check it as your first tuning step.
Here is where money actually leaks. Oracle sells external ecosystem products alongside the database that carry the same brand words as the free in-database features. The free feature is the in-database engine. The paid product is the separate server. On SE2, being clear about this is the difference between compliant and exposed.
The clearest example is graph analytics. In-database Property Graph queries via PGQL, and RDF triple store queries via SPARQL, need no additional license on EE or SE2. But large-scale parallel graph analytics run through the PGX in-memory engine (PageRank, community detection, and similar algorithms) require a separate Oracle Graph Server license. That distinction is the primary conflation trap Oracle field teams create. If a proof of concept quietly stands up Graph Server to run PGX algorithms, you have deployed a separately licensed product, and on SE2 the serial database underneath it does not change that fact. Our forthcoming note on the graph license changes in 23ai tracks how this line moved for graph specifically.
Several components are license-free but still require separate installation, which trips up teams who assume 'included' means 'already there.' Spatial Studio, Property Graph In-Memory Analytics (PGX), and the old Oracle R Enterprise all need separate installation. On SE2 specifically, running mdinst.sql enables Spatial, but if you need the RDF Graph features or the explicit topology model (the SDO_TOPO package), you need an additional patch to install them. None of these are extra license charges, but they are extra steps, and the presence of a separately installed component is exactly what an LMS auditor looks for as evidence of usage.
| Capability | License on SE2 | Notes |
|---|---|---|
| Core Spatial data type, SDO_GEOMETRY, spatial operators | Included | Runs serially. Enable SPATIAL_VECTOR_ACCELERATION. |
| Spatial indexing, geocoding, routing (in-database) | Included | Serial execution; benchmark before committing to SE2. |
| In-database Property Graph (PGQL) and RDF (SPARQL) | Included | No extra license on SE2 or EE. |
| Explicit topology (SDO_TOPO) and RDF Graph install | Included, but patch required | Extra install step on SE2, not extra license cost. |
| Spatial Studio (visual tool) | Included, separate install | Free, but must be installed separately. |
| Large-scale parallel graph analytics via PGX / Graph Server | NOT included | Separate Oracle Graph Server license required. |
| Parallel spatial query, index build, DML | NOT available | SE2 has no parallelism, regardless of Spatial entitlement. |
Spatial being free does not lift SE2's structural caps, and those caps decide whether SE2 is even a viable home for your GIS. SE2 is limited to two occupied sockets per server, with occupied being the test rather than installed, and no more than sixteen CPU threads per database. Licensing is per occupied socket, not per core, so the cost is flat regardless of core count within those two sockets. SE2 lists at $17,500 per Processor or $350 per Named User Plus, with a Named User Plus minimum of 10 per Processor. Enterprise Edition lists at $47,500 per Processor or $950 per NUP with a 25 NUP per Processor minimum. Full context on the caps sits in our SE2 licensing guide and the SE2 versus Enterprise Edition breakdown.
For a spatial estate the metric choice matters. A large number of GIS end users can make Named User Plus expensive fast, while a heavily virtualized or high-core server can make Processor licensing the trap on EE. We walk the tradeoff in the Processor versus NUP decision for a GIS estate. On SE2 the flat per-socket model often wins for smaller footprints, provided the serial performance holds up.
Because Spatial is now free, the classic finding of 'you used a Spatial feature you didn't license' has largely evaporated for the in-database engine. That is a genuine improvement for buyers. But two exposures remain, and both are architectural rather than entitlement based.
The defense is evidence, not argument. Keep configuration output showing which components are installed, the SPATIAL_VECTOR_ACCELERATION setting, and the absence of Graph Server processes. Our accidental Spatial enablement note and the forthcoming Locator-only evidence pack show the exact artifacts to collect. If you deliberately want to stay in the free zone, the Locator versus Spatial line is worth confirming even though Spatial is now free, because Locator remains the narrower, provably-lighter footprint.
First, confirm your entitlement in the contract-grade documents. Pull the LIUM section for your database version that shows Spatial as an included feature, and store the OAA/OSG FAQ alongside it. Do not accept an Oracle rep's verbal claim that SE2 needs a Spatial add-on; that is negotiating theater against six-year-old documentation.
Second, benchmark the serial reality before you architect. Run your heaviest spatial query and your largest index build on SE2 with SPATIAL_VECTOR_ACCELERATION set to TRUE. If it clears your SLA, SE2's flat per-socket cost is a strong buy. If it does not, the driver for Enterprise Edition is parallelism, and you should price EE with the understanding that the Spatial functionality is still free on EE too, so you are paying for the engine, not the option.
Third, ring-fence anything named 'Graph Server' or 'PGX.' Treat those as separately licensed products and require a business case and a license check before any environment installs them. Validate your discount assumptions against the 2026 cost benchmarks so you are not negotiating against list. Do all three before Oracle proposes a 'Spatial bundle' you already own.
No. Since December 5, 2019, Spatial and Graph is no longer a priced option. Its functionality is an included feature of the base Oracle Database license on both SE2 and Enterprise Edition, retroactive to version 11.2. If you have SE2 with active support, you already own Spatial.
SE2 has no parallelism. Oracle's own FAQ states that Spatial, Graph, and Machine Learning features execute serially on SE2. Every spatial join, index build, and query runs on a single thread. First enable the SPATIAL_VECTOR_ACCELERATION parameter, which is free but off by default. If serial execution still misses your SLA, the reason to move to Enterprise Edition is performance, not licensing.
The separately licensed Oracle Graph Server and its PGX in-memory engine, used for large-scale parallel graph analytics like PageRank and community detection, are not included and require a separate license. In-database Property Graph (PGQL) and RDF (SPARQL) queries are included at no extra cost. The Graph Server is the primary product Oracle sales conflates with the free in-database feature.
Yes, Spatial Studio carries no additional license charge on SE2. However, it requires a separate installation; it is not present just because Spatial is included. The same applies to PGX and, if you need RDF Graph or the SDO_TOPO topology model, an additional patch is required to install those features on SE2.
Not for the in-database Spatial engine, which is free on SE2. Exposure comes from two things: deploying the separately licensed Graph Server or PGX engine, and enabling Enterprise-only features such as partitioning or parallel query to make spatial workloads perform. Keep configuration evidence showing what is installed and that no Graph Server is running.
SE2 lists at $17,500 per Processor with flat per-socket pricing and includes Spatial in full, capped at two occupied sockets and sixteen threads per database. Choose SE2 if serial spatial performance clears your SLA and you fit the socket ceiling. Choose Enterprise Edition only when you need parallelism, and price it knowing Spatial itself is still free there too.
Oracle SE2 licenses per occupied socket at 17,500 dollars, two sockets maximum, 16 thread cap. Free paper on the metric choice and Enterprise Edition trap.
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.
