I’m a spatial data analyst trying to learn about options for pre-computing columns in Oracle 18c.
I've recently learned about Oracle’s In-Memory technology as a possible option:
Oracle 21c - Database In-Memory Support by Oracle Spatial
Spatial supports the use of Oracle Database In-Memory technology.
You can enable a spatial table for use with Database In-Memory by adding virtual columns, and then use operators such as SDO_FILTER to query that table without using a spatial index.
Question:
Is In-Memory an extra-cost add-on to Oracle? Or is it included as standard functionality in all implementations of Oracle 18c Enterprise?
I tried asking in the Oracle In-Memory community, but didn't get a response.
To answer questions like this, check the Database Licensing Information User Manual.
Which has this to say about In-Memory in 18c:
Oracle Database In-Memory ... EE and EE-ES: Extra cost option
So yes, it's extra cost. From 19.8 there is the Database In-Memory Base Level feature. This includes In-Memory access in Enterprise Edition subject to these restrictions:
Allows you to experiment with Oracle Database In-Memory features without purchasing the Oracle Database In-Memory option. The following restrictions apply:
- The size of the In-Memory area (INMEMORY_SIZE) cannot exceed 16 GB for a CDB. In an Oracle RAC environment, the size is limited to 16 GB for each instance.
- The compression level for all objects and columns is automatically and transparently set to QUERY LOW.
- The Automatic In-Memory feature is disabled.
- In-Memory Column Store feature tracking is tracked for "In-Memory Base Level" rather than "In-Memory Column Store."
- The CellMemory feature is disabled for Oracle Exadata.
If you're using 18c, please note that it entered Sustaining Support on 30th June 2021. To stay supported you really should be looking to upgrade to 19c.