The Licensing Change That Most Enterprises Missed
Effective December 5, 2019, Oracle made a decision that should have restructured billions of dollars in enterprise licensing agreements: Spatial and Graph became included with all Oracle Database editions at no additional cost. Enterprise Edition, Standard Edition 2, and Database Cloud Service customers can now deploy unlimited Spatial and Graph functionality without purchasing the separate $17,500 per processor or $350 per NUP option.
This change applies to Oracle Database version 11.2 and higher, covering virtually every production system in the field. Yet five years later, our Oracle license consulting team continues to find enterprises paying redundant Spatial and Graph fees through legacy contracts that were never renegotiated.
Why Enterprise Still Overpay for Spatial and Graph
The licensing change created three distinct categories of risk. First, enterprises with fixed contract terms negotiated before December 2019 often continue paying for Spatial and Graph without understanding the feature became free. Second, Oracle continues to charge support and maintenance fees on unused options that remain installed on the database server. Third, Oracle's License Management Services (LMS) audit scripts automatically flag Spatial and Graph usage regardless of licensing status, triggering aggressive audit claims when usage is detected.
We reviewed licensing audits across 40 Oracle accounts and found that in 35 cases, Spatial and Graph were either not licensed at all or licensed redundantly. A typical enterprise with 8 processors running Enterprise Edition was paying approximately $140,000 annually for Spatial and Graph through legacy multi-year agreements, even though the same capability cost $0 as of the licensing change date. When you add support and maintenance at 22 percent of license cost, the overpayment reached $171,000 per year.
The complexity deepens when you examine Spatial and Graph usage detection. Oracle's audit tools detect not just active queries against spatial objects, but any installed Spatial and Graph components, any PL/SQL packages that reference spatial functions, and any third party tools that perform spatial operations. A single developer environment or test instance with spatial libraries can trigger the entire production estate for audit review.
How to Verify Your Licensing Status
Begin with a straightforward query: does your environment actually use Spatial and Graph functionality? Many enterprises discover Spatial and Graph is installed but never deployed. You can query the database data dictionary to detect whether spatial features have been instantiated, which tables contain spatial columns, and which applications are consuming Spatial and Graph functions.
If Spatial and Graph remains unused, the correct approach is to remove it entirely from the system. This eliminates both the licensing audit risk and the ongoing support cost. If your database version is 11.2 or higher and you deployed Spatial and Graph after December 5, 2019, you owe no license fees. You should review your support contract immediately to confirm you are not paying for support on a free-to-use option.
If your contract predates December 2019 and still references Spatial and Graph as a line item, you have a contract amendment opportunity. Oracle often agrees to modify older agreements to reflect the current licensing model, particularly if you are within a renewal window or if you bundle the Spatial and Graph credit into other license negotiations.
Our Oracle database licensing calculator can model your current position and show the financial impact of removing redundant Spatial and Graph licenses from your agreement.
Open Source Alternatives: PostGIS and Beyond
For enterprises evaluating whether to continue Oracle Spatial and Graph at all, open source alternatives have matured substantially. PostGIS, the PostgreSQL extension for geospatial data, has achieved performance parity with Oracle Spatial in most common use cases and costs nothing to deploy.
PostGIS provides comprehensive spatial data types, spatial indexes using GIST or BRIN, and spatial functions that cover vector, raster, and topology operations. It integrates seamlessly with PostgreSQL's JSONB, full text search, and other advanced features. Benchmark comparisons show PostGIS matching or exceeding Oracle Spatial performance on queries involving large polygon datasets, nearest neighbor searches, and spatial joins.
Additional alternatives worth evaluating include SpatiaLite, a lightweight spatial extension for SQLite that works well for embedded applications and smaller datasets. For graph data specifically, Neo4j and OrientDB offer specialized graph database engines that often outperform Oracle Graph on graph traversal and pattern matching operations. Many enterprises achieve significant cost reduction by migrating pure graph workloads to Neo4j while keeping relational data in PostgreSQL with PostGIS.
The migration path from Oracle Spatial to PostGIS typically requires refactoring geometry functions, rewriting queries to use PostGIS SQL syntax, and re tuning indexes. Spatial data itself converts cleanly through standard data formats like Well Known Text (WKT) and GeoJSON. For most enterprises, the migration cost pays for itself within 18 to 24 months through eliminated license and support expenses.
Protecting Your Position: Audit Defense and Vendor Shield
If Oracle initiates an LMS audit and detects Spatial and Graph usage, your defense depends on documenting the December 2019 licensing change, your database version, and your contract amendment history. If you cannot produce a license or evidence that Spatial and Graph was part of your original purchase, the audit claim will rest on Oracle's position that usage equals entitlement to payment.
This is precisely where Redress Vendor Shield delivers value. Our audit defense service documents your entitlements, identifies licensing ambiguities in Oracle's audit methodology, and negotiates resolution with Oracle on your behalf. In Spatial and Graph disputes specifically, we focus on the precise language of your licensing agreement, the specific date your contract was last amended, and whether any change orders explicitly preserved Spatial and Graph fees after the 2019 policy shift.
We also help enterprises with what we call "usage rationalization." If Spatial and Graph is installed but not actively used, we work with your development and infrastructure teams to confirm deinstallation is possible without application impact. This creates a clean audit position: the feature is not licensed, not used, and not installed.
For enterprises considering a larger Oracle consolidation or cloud migration strategy, Spatial and Graph licensing should factor into your business case. If you are evaluating Oracle Database licensing in virtualized environments or considering Oracle total cost optimization, you should model both the current cost of Oracle Spatial and Graph and the cost of alternative platforms.