Other
Secure Distributed Transaction Recovery Background Process (RECO)
Oracle Database enables queries and DMLs on objects hosted on a different database. When objects are updated on a remote database, the transaction on the source database ends up becoming a distributed transaction. If a distributed transaction fails, a database background process (RECO) periodically tries to re-establish contact, with the yet-to-be-notified subordinates and pushes the final outcome to those remote databases.
Secure Distributed Transaction Recovery Background Process (RECO) provides additional security for the RECO process.
IP Rate Limit in CMAN
You can use Oracle Connection Manager (CMAN) to limit the number of new connections allowed from an IP address in the specified unit of time. This IP rate limit feature enables you to protect your database against potential denial-of-service (DoS) attacks.
Malicious clients can send excessive connection requests to the server node. This can saturate the capacity of CMAN to handle new connections per second, and thus cause DoS attacks on your database. Using this security feature, you can prevent these types of attacks by detecting such clients early and rejecting those connections.
OCI Attributes for Microsoft Azure Active Directory Integration with Additional Oracle Database Environments
You can log into additional Oracle Database environments using your Microsoft Azure Active Directory (Azure AD) single sign-on OAuth2 access token. The previous release supported Azure AD integration for Oracle Cloud Infrastructure (OCI) Autonomous Database (Shared Infrastructure). This release has expanded Azure AD integration to support on-premises Oracle Database release 19.16 and later. The project adds the OCI attributes needed to supply the bearer token for connection creation.
This multi-cloud feature integrates authentication and authorization between Azure AD and Oracle Databases in Oracle Cloud Infrastructure and on-premises.