General

Adaptive Result Cache Object Exclusion

With adaptive result cache object exclusion, the database decides to blocklist certain objects if using the result cache is not beneficial for these objects, based on statistical evidence such as the number of invalidations, the cost savings of using result caching, and others. You have full control over the objects considered for exclusion to ensure you can continue using result cache for all your objects of interest.

Adaptive exclusion of objects that don't benefit or even have a detriment impact on result caching reduces the overall development and management workload for you. It can improve the database performance out of the box.

View Documentation

Diagnose and Repair SQL Exceptions Automatically at Compile-Time

SQL diagnostics can automatically detect and repair many severe compile-time SQL exceptions that would otherwise cause SQL statements to fail.

This feature improves the robustness of your applications and its service levels.

View Documentation

Read-Only Tablespace on Object Storage

Read-only tablespaces can be moved to and from Oracle Object Storage transparently, storing portions of a database on lower-cost storage in the Cloud. 

Allowing to move tablespaces to Oracle Object Storage enables a data lifecycle management strategy, storing the data on the most cost-effective storage tier based on its business value or access frequency.

View Documentation

Unified Memory

Unified Memory is a flexible and simple memory configuration for Oracle Databases that uses a single parameter to control database memory allocations, reducing or eliminating the need for system restart to change memory configurations. Unified Memory is especially useful in multiple workload high density database consolidation environments.

Unified Memory simplifies memory management to run multiple workloads in a highly consolidated environment with minimum disruption. It is easier to set the single parameter MEMORY_SIZE for configuring the database instance memory instead of using separate parameters like SGA_TARGET and PGA_AGGREGATE_LIMIT.

View Documentation