THIS IS A COST OPTION

Disable In-Memory Option

In 12.2.0.1.0 with the April 2019 RU it appears that Oracle does not capture use of the In-Memory option in the feature usage statistics. However, if INMEMORY_SIZE is non zero and INMEMORY_QUERY is ENABLE then the In-Memory option is definitely used for tables CREATEd or ALTERed to be INMEMORY.

Therefore, to avoid potential problems during an Oracle Audit (on instances where this option is not licensed)...

• ALTER SYSTEM SET inmemory_query='DISABLE' SCOPE=both;

• ALTER SYSTEM SET inmemory_size=0 SCOPE=spfile;

• DO NOT use the INMEMORY argument on any tables

Check Feature Usage

SET LINESIZE 200

SELECT u1.name, u1.detected_usages

FROM dba_feature_usage_statistics u1

WHERE u1.version = (SELECT MAX(u2.version)

FROM dba_feature_usage_statistics u2

WHERE u2.name = u1.name

AND u1.name LIKE 'In-%')

ORDER BY u1.name;

Any non-zero values indicates that usage has been detected. This could be an issue during an Oracle Audit (unless you can prove that the non-zero value is due to bug 19308780).

Oracle Database In-Memory Features

• In-Memory Column Store

• Fault Tolerant In-Memory Column Store (Requires Exadata, Supercluster, Oracle Database Appliance, or Exadata Cloud Service)

• In-Memory Aggregation

• Heat Map

• Automatic Data Optimization

Bibliography