Oracle Database Updates & Release Notes

This page describes the features and behavior changes that are new in Release Update 19.32.

Behavior Changes

Release Update 19.32 introduces the behavior changes described below. Review each item before applying the Release Update (RU). Most changes affect behavior only when the relevant feature is in use. Where applicable, test application, administrative, audit, and connectivity workflows in a non-production environment before rollout.

BFILENAME Queries Excluded from the Database Result Cache

Behavior change: SQL statements that contain the BFILENAME function are no longer cached in the Database Result Cache and no longer display Result Cache information in their execution plans.

This change keeps execution plans accurate and prevents unsupported caching behavior for queries that reference external files, improving predictability and operational confidence.

Correct Audit Object Association for VPD/RLS-protected Objects

Behavior change: Audit records for access to objects protected by Oracle Virtual Private Database (VPD) or Fine-Grained Auditing (FGA) are now associated with the correct object.

Audit records and object-level policy evaluation remain accurate for queries protected by Oracle Virtual Private Database. This improvement helps administrators maintain accurate audit traceability and supports compliance reporting.

View documentation:

• Auditing of Oracle Virtual Private Database Predicates
• Fine-Grained Auditing on Tables or Views That Have Oracle VPD Policies

DBMS_REDEFINITION Enforcement of Database Vault Authorization

Behavior change: DBMS_REDEFINITION now enforces Database Vault checks before table redefinition operations proceed. When Database Vault is enabled, the user invoking table redefinition must now be authorized to access both the original table and any interim table used during the redefinition process.

This change applies to the following entry points in DBMS_REDEFINITION:

• CAN_REDEF_TABLE
• START_REDEF_TABLE
• REDEF_TABLE
• ROLLBACK
• FINISH_REDEF_TABLE

The update checks Database Vault Realm, Command Rule, and Ops Control protections before allowing data movement between tables. If the user is not authorized under Database Vault, the operation is blocked and an appropriate error is returned. It prevents unauthorized use of table redefinition to move data out of Database Vault-protected tables or to alter protected table metadata without Database Vault authorization.

Expanded Default Password Detection in DBA_USERS_WITH_DEFPWD

Behavior change: Supported DBA_USERS_WITH_DEFPWD queries now return additional default password account findings and associated product labels for SYS, SYSTEM, and ADMIN account combinations.

This feature gives administrators a more complete view of default password risks and the related product context for remediation.

View Documentation

orapki cert display Command Shows Additional Certificate Attributes

Behavior change: The orapki cert display -cert command has been enhanced to display public key information along with existing certificate details. Specify the -complete and -details options with orapki cert display -cert to display the additional attributes in the command output.

This feature lets you verify certificate strength directly from the orapki utility, which makes security validation and certificate hardening easier without needing a separate tool.

View Documentation

orapki wallet p11_verify Reports Native Failure

Behavior change: The orapki wallet p11_verify command now reports an error when native PKCS#11 verification fails instead of allowing the failure to go undetected or be reported unclearly.

This feature makes PKCS#11 wallet verification failures visible, so you can identify and troubleshoot verification issues more quickly. Clearer error reporting reduces confusion during wallet validation.

View Documentation

Scheduler Single Named Destination Privilege Enforcement

Behavior change: Scheduler privilege validation has been updated for jobs that use a single named destination. When you enable or run one of these jobs, Scheduler validates that the job owner has the required privileges. CREATE ANY JOB authorizes the use of single named destinations in another user’s schema. For SYS-owned single named destinations, the job owner must have ALTER privilege on the destination object.

This update improves security by ensuring that jobs can be enabled or run against protected SYS single named Scheduler destinations only when the job owner has the required object-level privileges. Existing behavior for non-SYS single named destinations is unchanged.

View Documentation

Security Hardening of Database Vault Authorization on Scheduler Jobs

Behavior change: Before this release, CREATE, DROP, ALTER, ENABLE, and DISABLE operations performed through the DBMS_SCHEDULER APIs on certain Database Vault realm-protected objects might not have been enforced correctly. This update strengthens the internal realm authorization checks to ensure that Database Vault policies are applied consistently. As a result, operations that previously succeeded may now fail with ORA-01031: insufficient privileges when performed on realm-protected objects without the required realm authorization. In such cases, customers must grant the appropriate users the necessary authorization for the corresponding Database Vault realm.

View Documentation

Security Hardening on XS$NULL

Behavior change: Real Application Security (RAS) application users can no longer grant or revoke ON USER privileges for XS$NULL. If these operations are required, they must be performed by a sufficiently privileged database administrator, such as a user with the GRANT ANY OBJECT PRIVILEGE system privilege.

Unified Auditing for FLASHBACK_TRANSACTION_QUERY Privilege Use

Behavior change: Unified auditing now records the use of the SELECT ANY TRANSACTION privilege when accessing FLASHBACK_TRANSACTION_QUERY.

This feature provides administrators with more complete audit visibility for privileged access to historical transaction data.

View Documentation

New Features

Next-Generation Cryptographic Provider Announcement

Oracle Database 19c now supports a next-generation cryptographic provider based on OpenSSL (next-generation provider), in addition to the existing Dell BSAFE Crypto-C Micro Edition Suite, or MES (legacy provider).

This dual-provider architecture enables the following capabilities:

• TLS 1.3 protocol support
• FIPS 140-3 compliance (via OpenSSL 3.5.x FIPS provider)
• Post-Quantum Cryptography (PQC) algorithms for key exchange (ML-KEM) and digital signatures (ML-DSA)
• Hybrid key exchange groups that combine classic and post-quantum algorithms for quantum-resistant session establishment

The legacy provider remains the default. To switch to the next-generation provider, run the set_crypto_provider.py script and restart the database instance and Oracle Net listener. Only one cryptographic provider can be active at a time.

View Documentation

Behavior Changes

Release Update 19.31 introduces the behavior changes described below. Review each item before applying the Release Update (RU), particularly if you use the affected security, auditing, networking, Heterogeneous Services, blockchain/immutable-table, or file-group functionality.

Most changes affect behavior only when the relevant feature is in use. Where applicable, test application, administrative, audit, and connectivity workflows in a non-production environment before rollout.

Blockchain Table Verification

Behavior change: Blockchain-table verification can now be performed in parallel through a new PL/SQL procedure.

Parallel verification can reduce elapsed time but may increase CPU, I/O, and parallel-execution resource use while verification runs.

Review before upgrade:

• Identify scheduled or manual blockchain-table verification jobs.
• Review Resource Manager, parallel-execution limits, and maintenance windows.
• Test verification duration and system impact with representative table sizes.

View Documentation

Default NFS Version Selection with Direct NFS Client

Behavior change: The default NFS version used by Direct NFS client has changed. Previously, when no oranfstab file was present, Direct NFS defaulted to NFSv3. With this change, Direct NFS queries the system mount table (mtab) to determine the NFS version and uses that version instead.

The primary benefit is support for NFS storage servers that do not support NFSv3. This is particularly important in cloud environments, such as Oracle Autonomous AI Database, where customers cannot create an oranfstab file to explicitly configure Direct NFS to use NFSv4.

File-Group Metadata Visibility

Behavior change: READ ANY FILE GROUP is no longer the supported mechanism for determining which file-group metadata a user can see through ALL_FILE_GROUPS.

Previously, this privilege could expose all file-group records through ALL_FILE_GROUPS. In 19.31, visibility should be granted using the appropriate SELECT privilege on the relevant metadata views. MANAGE ANY FILE GROUP continues to govern file-group management operations.

Review before upgrade:

• Identify users, roles, scripts, and tools that rely on READ ANY FILE GROUP.
• Confirm that users requiring file-group metadata have the required SELECT access.
• Test queries against ALL_FILE_GROUPS and related file-group views after patching.

View Documentation

Heterogeneous Services extproc Idle Timeout

Behavior change: The new HS_IDLE_TIMEOUT initialization parameter provides explicit control of idle timeout behavior for Heterogeneous Services external-procedure sessions.

The parameter can retain, override, or disable the timeout inherited from SQLNET.INBOUND_CONNECT_TIMEOUT. This can change when idle extproc sessions terminate.

Review before upgrade:

• Identify external procedures and applications using Heterogeneous Services.
• Check the current SQLNET.INBOUND_CONNECT_TIMEOUT setting and any history of ORA-28576 errors.
• Decide whether to set HS_IDLE_TIMEOUT; test both long-running and idle extproc workloads.

Immutable and Blockchain Table DDL and CTAS Processing

Behavior change: Existing tables can now be converted in place to immutable tables, and CREATE TABLE AS SELECT operations for blockchain tables can run in parallel.

These changes introduce additional supported DDL and can alter the resource profile and elapsed time of blockchain-table CTAS operations.

Review before upgrade:

• Review change-management controls that govern conversion of existing tables to immutable tables.
• Check automation, deployment tools, and DDL auditing for assumptions about immutable-table creation.
• Validate capacity and workload-management settings if parallel CTAS is used for blockchain tables.

View Documentation

Kerberos-Constrained Delegation for Database Links

Behavior change: Database links can operate in Microsoft Active Directory environments that enforce Kerberos constrained delegation, including newer Windows platforms where prior ticket-forwarding behavior may not be allowed.

This changes the supported authentication path for Kerberos-enabled database links and removes reliance on older Microsoft registry workarounds.

Review before upgrade:

• Identify database links that use Kerberos authentication.
• Test database-link authentication from Windows 11 and Windows Server 2025 clients or servers, where applicable.
• Review Active Directory constrained-delegation configuration and retire legacy workarounds only after validation.

View Documentation

ONS TLS Elliptic-Curve Restrictions

Behavior change: Oracle Notification Service can now exclude weak elliptic curves from TLS negotiation when DISABLE_WEAK_CURVES is enabled.

Enabling the setting changes TLS handshake behavior. Clients or peers that depend on excluded curves may no longer connect.

To enable this feature, run the following command on any cluster node from the Grid Infrastructure home:

srvctl setenv nodeapps -onsonly -env DISABLE_WEAK_CURVES='yes'

Review before enabling:

• Inventory ONS clients, peers, and monitoring tools.
• Confirm that all TLS participants support approved strong elliptic curves.
• Test ONS connectivity and failover behavior after enabling the setting.
• Coordinate the change with security and vulnerability-management teams.

View Documentation

Unified Auditing of Equivalent Real Application Security Actions

Behavior change: Audit policies for standard database user and role actions also audit the equivalent Real Application Security (RAS) actions.

For example, auditing CREATE USER also captures the corresponding RAS user-creation operation. This increases audit coverage and can increase audit-record volume.

Review before upgrade:

• Review unified audit policies that cover user or role administration.
• Anticipate additional audit records for equivalent RAS operations.
• Confirm that audit retention, reporting, SIEM ingestion, and storage capacity accommodate the additional volume.
• Update audit-review procedures if they distinguish standard SQL actions from RAS procedure calls.

View Documentation

New Features

There are no new features for Release Update 19.31.

This page describes the features and behavior changes that are new in Release Update 19.30.

Behavior Changes

Release Update 19.30 introduces the behavior changes described below. Review each item before applying the Release Update (RU). Most changes affect behavior only when the relevant feature is in use. Where applicable, test application, administrative, audit, and connectivity workflows in a non-production environment before rollout.

PRE_PAGE_SGA

Behavior change: PRE_PAGE_SGA remains a supported initialization parameter in Oracle Database 19c, Release Update 19.30. Removing its deprecated flag keeps automated duplicate and standby creation workflows from failing when the parameter is inherited from a source SPFILE.

Restoring full support for PRE_PAGE_SGA lets you keep legacy configurations in place without disrupting DBCA duplicate, Data Guard standby, or RMAN clone operations, eliminating ORA-32006 interruptions for fleets that cannot immediately drop the parameter.

View Documentation

New Features

Restricting Directory Paths for PDBs Configured Without PATH_PREFIX

A new CDB-level parameter, DIRECTORY_PREFIXES_ALLOWED, lets administrators restrict which operating system directories PDBs can reference when creating new DIRECTORY objects, even if the PDB was originally created without the PATH_PREFIX clause. When this parameter is set, any newly created DIRECTORY object in a PDB is validated to ensure its path falls under one of the approved directory prefixes. Existing DIRECTORY objects continue to function unchanged for backward compatibility. However, potentially noncompliant directory objects can be identified using DBA_DIR_PREFIX_VIOLATIONS and will appear as warnings in PDB_PLUG_IN_VIOLATIONS after a restart.

This security feature allows the CDB administrator to restrict directory object paths created or accessed from within PDBs to one or more specific operating system directories. It acts as a guardrail for the CDB by preventing PDBs that were created without the PATH_PREFIX clause from accessing or modifying sensitive operating system files or CDB$ROOT container datafiles and metadata files.

View Documentation

Select AI

Through the DBMS_CLOUD_AI package, Select AI serves as an AI gateway enabling users, developers, and applications to interact with Oracle AI Database using natural language supporting multiple generative AI use cases. Select AI provides functionality supporting natural language to SQL, including automatically generating, running, and explaining SQL, and through the DBMS_CLOUD_AI_AGENT package, providing a framework for building, managing, and running AI agents in the database. It also supports synthetic data generation and text summarization and translation. Select AI provides PL/SQL and Python APIs.

Together with the broader foundational Cloud Developer packages, they enable you to integrate AI capabilities directly from the database and support end-to-end workflows that deliver greater data insight with AI.

Select AI enables business users and developers to use a wide range of AI providers and models supporting many AI-enabled use cases and application scenarios. Select AI helps to simplify the adoption of AI in enterprises and organizations across both on-premises and cloud systems. Users get insights faster using natural language without waiting on manual SQL query generation. This can reduce IT bottlenecks and accelerate AI-enabled application development. Using Select AI, enterprises benefit from database security mechanisms and protocols.

View Documentation

This page describes the features and behavior changes that are new in Release Update 19.29.

Behavior Changes

Release Update 19.29 introduces the behavior changes described below. Review each item before applying the Release Update (RU). Most changes affect behavior only when the relevant feature is in use. Where applicable, test application, administrative, audit, and connectivity workflows in a non-production environment before rollout.

Database Vault Default Realms Upgraded to Mandatory Realms

Behavior change: The Oracle Database Vault realm has been changed from a regular realm to a mandatory realm. In addition, a new mandatory Oracle Label Security realm has been added.

These security hardening enhancements strengthen the protection of Oracle-managed Database Vault and Oracle Label Security objects and related execution paths. Mandatory realms provide stronger protection by preventing even privileged users from bypassing realm protection. These changes help preserve the integrity of Database Vault configuration, metadata, and policy enforcement.

New Features

Ability to Control Heartbeats in United Mode and Isolated Mode PDBs

You now can control the size of the batch of heartbeats that use Oracle Key Vault or OCI KMS (OCI Vault) for centralized key management.

The HEARTBEAT_BATCH_SIZE initialization parameter enables you to set the heartbeat batch size. The duration of the heartbeat period defaults to 3 seconds.

This enhancement benefits the situation where you have a very large deployment of PDBs (for example, 1000) that use Oracle Key Vault. By setting the heartbeat batch size, you can stagger the heartbeats across batches of PDBs to ensure that for each batch a heartbeat can be completed for each PDB within the batch during the heartbeat period, and also ensure that PDB keys can be reliably fetched from an Oracle Key Vault server and cached in the persistent state.

View Documentation

This page describes the features and behavior changes that are new in Release Update 19.28.

Behavior Changes

Release Update 19.28 introduces the behavior changes described below. Review each item before applying the Release Update (RU). Most changes affect behavior only when the relevant feature is in use. Where applicable, test application, administrative, audit, and connectivity workflows in a non-production environment before rollout.

Restricting Access to DBA_TAB_STAT_PREFS , CDB_TAB_STAT_PREFS , CDB_TAB_PENDING_STATS , and CDB_IND_PENDING_STATS to DBAs Only

Behavior change: The DBA_TAB_STAT_PREFS, CDB_TAB_STAT_PREFS, CDB_TAB_PENDING_STATS, and CDB_IND_PENDING_STATS views used to be accessible to everyone. Now, they are accessible to users with DBA privileges only.

This change makes these views consistent with any other views starting with the prefix DBA and CDB. Users with non-DBA privileges should only be able to access ALL_TAB_STAT_PREFS, USER_TAB_STAT_PREFS, ALL_TAB_PENDING_STATS, USER_TAB_PENDING_STATS, ALL_IND_PENDING_STATS, and USER_IND_PENDING_STATS.

New Features

DBMS_DEVELOPER PL/SQL Package

The DBMS_DEVELOPER PL/SQL package provides an efficient way for developers to retrieve metadata for database objects, such as tables, views, and indexes. In previous releases, object metadata had to be retrieved using the DBMS_METADATA package, which returned metadata in XML format or by performing queries on various data dictionary tables and views.

The DBMS_DEVELOPER package returns metadata as a CLOB containing JSON formatted text, which can be easily integrated with applications and services, such as developer tools. You can adjust the level of detail to control the amount of metadata returned, tailoring it to your application’s needs. Additionally, metadata retrieval time is significantly improved, enhancing integration with applications and services.

View Documentation

Enhancements to RADIUS Configuration

RADIUS is frequently used to provide multi-factor authentication (MFA) for Oracle Database. Oracle Database 19c now supports the RFC 6613 and 6614 guidelines for RADIUS and implements TCP over Transport Layer Security (TLS) by default. This enhancement introduces new RADIUS-related sqlnet.ora parameters to support the new standards. The enhancement also deprecates several RADIUS-related sqlnet.ora parameters that are no longer needed to support the new standards.

This update to RADIUS standards support improves security for customers using RADIUS-based authentication.

View Documentation

IF [NOT] EXISTS Syntax Support

DDL object creation, modification, and deletion now support the IF [NOT] EXISTS syntax modifiers. This enables you to control whether an error should be raised if a given object exists or does not exist.

The IF [NOT] EXISTS syntax can simplify error handling in scripts and by applications.

View Documentation

Multi-Factor Authentication for Database Authentication

You can enhance Oracle Database security by enabling multi-factor authentication for users. You can use push notifications through the Cisco Duo or Oracle Mobile Authenticator app or combine a username and password with PKI (Public Key Infrastructure) certificate-based authentication.

Multi-factor authentication is a required security requirement for many databases, especially if the database holds sensitive data.

View Documentation

Oracle Database Cloud Backup Module for Azure Blob Storage

The Oracle Database Cloud Backup Module for Azure Blob Storage enables Oracle Database to send backups to and recover from Microsoft Azure Blob Storage. This backup module is compatible with Oracle Databases deployed on-premises or on Azure cloud. Support for writing backups to Azure Blob Storage for Oracle-managed database services is not available. Database administrators can use RMAN commands, RMAN scripts, and Oracle Enterprise Manager to perform backup and recovery operations with Azure Blob Storage.

You can run Oracle Databases in many different locations, and the backup module for Azure Blob Storage provides on-premises and Azure virtual machine users with more flexibility for backup storage locations.

View Documentation

Oracle Update Advisor Support with Oracle FPP

You can leverage Oracle Update Advisor with Oracle Fleet Patching and Provisioning (Oracle FPP). Oracle Update Advisor is a software recommendation framework that analyzes the health of Oracle Database and Oracle Grid Infrastructure, provides patch recommendations, and creates fully functional gold images based on your patch maintenance policy. These gold images are downloaded automatically into the Oracle FPP Gold Image repository.

Using Oracle Fleet Patching and Provisioning in conjunction with Oracle Update Advisor greatly simplifies and streamlines the update experience. You can use the Oracle Update Advisor for both Oracle FPP Local Mode and Oracle FPP Central Server Mode.

View Documentation

Schema Annotations

Schema annotations enable you to store and retrieve metadata about database objects. These are name-value pairs or simply a name. These are free-form text fields applications can use to customize business logic or user interfaces.

Annotations help you use database objects in the same way across all applications. This simplifies development and improves data quality.

View Documentation

SQL Diagnostic Report

The SQL diagnostic package (DBMS_SQLDIAG) includes a new function called REPORT_SQL which generates a zip archive containing a deep-level HTML diagnostic report for a specified SQL statement. The report includes important diagnostic information such as a plan history, non-default database parameters, optimizer statistics history, statistics status, index details, and more. The archive will also include, where available, captured SQL Monitor reports for the SQL.

This feature makes it easier to diagnose SQL performance issues.

View Documentation

Application Identity Logon

• Array Limits for JSON-Relational Duality Views
• Cross-Table Data Grant Support
• Deletable Shared Tables for JSON-Relational Duality Views
• Intelligent Drain Timing
• Log-Buffer-Space-Based Auto Redo Prioritization
• MAA Client Readiness
• OCI API Functions to Validate and Protect Inputs
• Oracle AI Database as a Redis Server
• PDB Target Redo Generation Management
• Scalar Quantization Support for Distributed HNSW Indexes
• Setting Multi-Factor Authentication for Local Deep Sec End User
• Support for DATEADD Function
• Transport-Lag-Based Auto Redo Prioritization
• Unicode 17.0 Support
• User-Defined Identifying Keys for JSON-Relational Duality Views
• Using OCI IAM DB Token to Authenticate with Deep Data Security

This page describes the features and behavioral changes that are new in Release Update 19.7.

SQL Macros (SQM)

You can create SQL Macros (SQM) to factor out common SQL expressions and statements into reusable, parameterized constructs that can be used in other SQL statements. Starting with Oracle Database release 19c, version 19.7, SQL table macros are supported. SQL table macros are expressions, typically used in a FROM clause, to act as a sort of polymorphic (parameterized) view.

SQL macros increase developer productivity, simplify collaborative development, and improve code quality.

View Documentation

This page describes the features and behavioral changes that are new in Release Update 19.8.

Database In-Memory Base Level

Database In-Memory is an option to Enterprise Edition. Database In-Memory now has a new Base Level feature. This allows the use of Database In-Memory with up to a 16GB column store without triggering any license tracking.

This feature allows you to use Database In-Memory without having to license the option. The column store is limited to 16GB when using the Base Level. This helps to show the value of Database In-Memory without having to worry about licensing issues.

View Documentation

CellMemory Level

You can use the CellMemory feature without enabling the IM column store by setting

INMEMORY_FORCE=CELLMEMORY_LEVEL

and

INMEMORY_SIZE=0

.

This feature allows you to use CellMemory without incurring the overhead of enabling the IM column store.

View Documentation

This page describes the features and behavioral changes that are new in Release Update 19.9.

Oracle Grid Infrastructure SwitchHome

You can use the -switchGridHome option with gridSetup.sh to switch from one Oracle Grid Infrastructure home to another.

You can use the -switchGridHome option for patching and upgrading Oracle Grid Infrastructure. Use the -switchGridHome option to switch from the source Oracle Grid Infrastructure home to the patched Oracle Grid Infrastructure home. All Oracle Clusterware and Oracle Restart services start from the patched Oracle Grid Infrastructure home automatically.

View Documentation

Support for DBMS_CRYPTO Asymmetric Key Operations

Starting with this release, the DBMS_CRYPTO PL/SQL package supports asymmetric key operations, in addition to the existing support for symmetric key operations.

To implement the support for asymmetric key operations, the following procedures have been added to the DBMS_CRYPTO package:

• PKENCRYPT
• PKDECRYPT
• SIGN
• VERIFY

View Documentation

This page describes the features and behavioral changes that are new in Release Update 19.10.

Ability to Use Multiple Kerberos Principals with a Single Database Client

Starting with this release, when you configure Kerberos authentication for an Oracle Database client, you can specify multiple Kerberos principals with a single Oracle Database client.

To enable this functionality, you will need to create a separate credential cache for each user in the client and then use the connect string to specify the user.

In previous releases, you were restricted to one Kerberos principal for each Oracle Database client.

View Documentation

DBMS_CLOUD Package

Oracle provides two core mechanisms to work with data in object stores, as part of the new DBMS_CLOUD package or manually defining external tables.

Using DBMS_CLOUD provides benefits and additional functionality that goes beyond DDL and is fully compatible with Oracle Autonomous Database. Oracle strongly recommends leveraging the new DBMS_CLOUD package over manual external table creation.

View Documentation

New Database Initialization Parameters for Database Resident Connection Pooling (DRCP)

New database initialization parameters, MIN_AUTH_SERVERS and MAX_AUTH_SERVERS, have been added to configure Database Resident Connection Pooling (DRCP).

MIN_AUTH_SERVERS and MAX_AUTH_SERVERS allow the number of processes used to handle session authentication for DRCP to be configured for optimal usage.

View Documentation

Oracle Blockchain Table

Blockchain tables are append-only tables in which only insert operations are allowed. Deleting rows is either prohibited or restricted based on time. Rows in a blockchain table are made tamper-resistant by special sequencing and chaining algorithms. Users can verify that rows have not been tampered. A hash value that is part of the row metadata is used to chain and validate rows.

Blockchain tables can be used to implement blockchain applications where the participants trust the Oracle Database provider, but want means to verify that their data hasn’t been tampered with. The participants are different database users who trust the Oracle Database provider to maintain a verifiable, tamper-resistant blockchain of transactions. All participants must have privileges to insert data into the blockchain table. The contents of the blockchain table are defined and managed by the application, with a few added metadata fields maintained by Oracle Database. By leveraging a trusted provider with verifiable crypto-secure data management practices, such applications can avoid the distributed consensus requirements. This provides most of the protection of the distributed peer-to-peer blockchains, but with much higher throughput and lower transaction latency compared to peer-to-peer blockchains using distributed consensus.

View Documentation

Oracle Instant Client Support for Linux for ARM

Starting with Oracle Database 19c Release Update (19.10), Oracle Instant Client is available on Linux for ARM (aarch64).

You can install Oracle Instant Client by downloading either the zip files or RPMs from the Oracle Instant Client download page on Oracle Technology Network (OTN).

View Documentation

Support Per-PDB Capture for Oracle Autonomous Database

To securely capture and replicate individual PDB changes to Oracle Autonomous Database, you can now use Oracle GoldenGate to provide per-PDB capture.

You can now provide local user credentials to connect to an individual PDB in a multitenant architecture Oracle Database, and replicate the data from just that PDB to an Oracle Autonomous Database. You no longer need to create a common user with access to all PDBs on the multitenant container database (CDB) to replicate a PDB to an Oracle Autonomous Database. Instead, you can now provision a local user with a predefined set of privileges to the source PDB that you want to capture. All LogMiner and Capture processing takes place only in this PDB, and only data from this specific PDB is captured and written to the Oracle GoldenGate trail. As part of this feature, the behavior for V$LOGMNR_CONTENTS changes, depending on whether you connect to a PDB, or connect to the CDB$ROOT.

View Documentation

Updated Support for Micro Edition Suite (MES) for FIPS 140.2

Starting with this release, Oracle Database supports Micro Edition Suite (MES) version 4.5 for FIPS 140.2.

The Micro Edition Suite (MES) version 4.5 updates include four new CVEs in the RSA BSAFE MES library, support for the rules that FIPS 140.2 requires, and access to the updated NZ/ZT library from the Crypto Foundation.

This enhancement enables the Oracle Database FIPS 140.2 configuration to benefit from new features and security improvements available from the latest RSA BSAFE MES library.

View Documentation