This preface contains:
Changes in Oracle Database Release 21c, Version 21.1
The following are changes in Oracle Database PL/SQL Packages and Types Reference for Oracle Database release 21c, version 21.1.
This section lists the major new features in Oracle Database release 21c PL/SQL Packages and Types Reference.
The following features are new in this release:
DBMS_OPTIM_BUNDLEpackage is used to manage the installed but disabled module bug fixes which cause an execution plan change.
DBMS_AUTO_MVpackage provides the following new
PL/SQLprocedures functions and procedures for automatic materialized views. This performs analysis and recommendation, verification, and maintenance of automatic materialized views.
DBMS_ACTIVITYpackage provides the following new
PL/SQLprocedures functions and procedures for Object Activity Tracking System (OATS). This is a generic RDBMS based tracking service that provides information about various types of activities associated with different database objects.
DBMS_FLASHBACK_ARCHIVE_MIGRATEpackage provides new
PL/SQLfunctions and procedures for exporting and importing the Flashback Archive base tables along with their history to another database using the Transportable Tablespaces.
DBMS_MLEpackage provides new
DBMS_AVTUNEpackage provides new
PL/SQLfunctions and procedures to analyze query access levels and aggregation workloads for each auto-cache enabled analytic view (AV) and creates or drops AV auto-caches to improve the overall performance of the SQL queries on that AV.
- The following new subprograms were introduced in the
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 & 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 enable you to implement a centralized ledger model where all participants in the blockchain network have access to the same tamper-resistant ledger. The following new packages are available in this release:
A new function
GET_BLOCK_MAPhas been added to the
DBMS_PLSQL_CODE_COVERAGEpackage to help you calculate the total coverage number for a schema.
See "GET_BLOCK_MAP Function"
JSON data guide supports extended JSON scalar types like double, float, timestamp, and so on.
Oracle Database Advanced Queuing Support for JSON data type
AQ now supports
JSONpayload type. A dedicated
JSONdata type allows the user to store
JSONdata in a post-parse binary format, which allows much faster access to nested
See "DBMS_AQ Data Types"
Enhanced Result CacheThe
DBMS_RESULT_CACHEpackage provides the following new
PL/SQLprocedures that allows users to block an object from the result cache.
- Support for
DBMS_CRYPTOAsymmetric Key Operations
Starting with this release, the
DBMS_CRYPTOPL/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
- The following two new procedures are introduced in the DBMS_APP_CONT_ADMIN
package to enhance the application continuity protection check:
- ACCHK_REPORT Procedure
- ACCHK_SET Procedure
- New parameter,
AUTO_INDEX_TABLEis added in
CONFIGUREprocedure in the
DBMS_AUTO_INDEXpackage. You can use the
AUTO_INDEX_TABLEconfiguration setting to specify tables that can use auto indexes.
- The following 3 parameters are added to the
ADD_VIRTUAL_COLUMNSProcedure in the
DBMS_JSONpackage to enhance view creation and adding of virtual columns:
- The following parameters are added to the
CREATE_VIEWprocedure in the DBMS_JSON package to enhance view creation and adding of virtual columns:
- The following 3 parameters are added to the
List of deprecated features in Oracle Database release 21c version 21.1 PL/SQL Packages and Types Reference.
Oracle recommends that you do not use deprecated features/values in new applications. Support for deprecated features is for backward compatibility only.
Oracle Wallet Manager (OWM)is deprecated with Oracle Database 21c.
Please ensure your wallets are using the strongest protections available. Instead of using Oracle Wallet Manager, Oracle recommends that you use the command line tools
- The use of
- The use of
MD4algorithms are deprecated.
- Oracle Enterprise Manager Database Express (EM Express) is deprecated.
This section lists the desupported features in Oracle Database release 21c version 21.1 PL/SQL Packages and Types Reference.
The following features are desupported in this release:
A multitenant container database is the only supported architecture in Oracle Database 21c. While the documentation is being revised, legacy terminology may persist. In most cases, "database" and "non-CDB" refer to a CDB or PDB, depending on context. In some contexts, such as upgrades, "non-CDB" refers to a non-CDB from a previous release.
DBMS_XMLSAVEpackage is desupported in Oracle Database 21c.
DBMS_XMLQUERYpackage is desupported in Oracle Database 21c.
DBMS_CRYPTO: Desupported algorithms include MD4, MD5 and RC4-related algorithms. Removing older, less secure cryptography algorithms prevents accidental use of these APIs. To meet your security requirements, Oracle recommends that you use more modern cryptography algorithms.
Starting with Oracle Database 21c, several XML Database features are desupported.
DBMS_XDBT. There is no replacement.
- PL/SQL procedure
- PL/SQL function
Starting in Oracle Database 21c, the Large Object (LOB) features
DBMS_LOB.LOADFROMFILEis desupported. Use
LOB buffering is also desupported. Hence, the
BUFFERING_ENABLEDexception is no longer supported.
DBMS_OBFUSCATION_TOOLKITpackage was desupported in Oracle Database 10g Release 2. It is now removed in Oracle Database 21c.
DBMS_CRYPTOreplaces the functionality that
DBMS_CRYPTOincludes more modern and secure encryption technologies for your security requirements.
The ability to create flat file dictionary dumps of pluggable databases (PDBs) is desupported in Oracle Database 21c.
In previous releases, using a flat file dictionary was one means of mining the redo logs for the changes associated with a specific PDB whose data dictionary was contained within the flat file. This feature is now desupported. Starting with Oracle Database 21c, Oracle recommends that you call
DBMS_LOGMNR.START_LOGMNR, and supply the system change number (SCN) or time range that you want to mine. The SCN or time range options of
START_LOGMNRare enhanced to support mining of individual PDBs.
OPTIMIZE_PROGRESS_TABLEparameter from the
DBMS_APPLY_ADM.SET_PARAMETERprocedure is desupported in Oracle Database 21c.