Key Features No Longer Supported in Oracle 23ai

By -

 Oracle regularly introduces numerous features in each version while deprecating or desupporting certain older ones. “Deprecate” means a feature will no longer receive improvements and will eventually become desupported in future versions. “Desupport” indicates that bug fixes will no longer be provided, and in some cases, the feature may become completely unusable.

Below, we review some notable features that Oracle 23ai no longer supports:

Database Upgrade Assistant (DBUA) and Manual Upgrades

From version 23ai, Oracle recommends using AutoUpgrade for database upgrades. The DBUA tool is no longer supported on Linux environments, nor are manual upgrade scripts such as catupgrd, dbupgrade, and catctl. However, DBUA remains usable in Windows environments.

exp/imp Tools

Oracle states in its documentation that the exp/imp tools are no longer supported. Instead, DBAs are encouraged to use DataPump. Despite this, exp/imp tools are still present in Oracle 23.5 and can be used as follows:

[oracle@OEL9 ~]$  exp usef/q@OEL9:1521/IRANDB file=dumpTEH.dmp tables=USEF.TBL_VANAK_PRVC
Export: Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems on Tue Oct 1 11:43:57 2024
Version 23.5.0.24.07
Copyright (c) 1982, 2024, Oracle and/or its affiliates.  All rights reserved.
Connected to: Oracle Database 23ai Enterprise Edition Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems
Version 23.5.0.24.07
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses AL32UTF8 character set (possible charset conversion)
About to export specified tables via Conventional Path ...
. . exporting table                TBL_VANAK_PRVC          0 rows exported
Export terminated successfully with warnings. <br>

Traditional Auditing

Although Oracle introduced Unified Auditing in version 12c, Traditional Auditing remained the default. From version 23ai, Traditional Auditing is no longer supported. Pre-existing policies from earlier versions will remain active after upgrading but creating new policies will not be possible.

Data Recovery Advisor (DRA)

Introduced in version 11g, DRA allowed RMAN commands like LIST FAILURE, ADVISE FAILURE, and REPAIR FAILURE to detect and fix issues such as data block corruption. This feature is fully removed in Oracle 23ai with no replacement.

RMAN> ADVISE FAILURE;
ADVISE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "advise": expecting one of: "allocate, alter, analyze, associate statistics, audit, backup, begin, @, call, catalog, change, comment, commit, configure, connect, convert, copy, create, create catalog, create global, create or replace global, create or replace script, create script, crosscheck, declare, delete, delete from, describe, describe catalog, disassociate statistics, drop, drop catalog, drop database, duplicate, exit, explain plan, flashback, flashback table, grant, grant catalog, grant register, host, import, insert, list, lock, merge, mount, noaudit, open, print, purge, quit, recover, register, release, rename"
RMAN-01007: at line 1 column 1 file: standard input

EM Express

EM Express, introduced in 12c as a lightweight replacement for Oracle Enterprise Manager, is no longer supported in version 23ai. DBAs are advised to use Oracle Enterprise Manager Cloud Control for database monitoring and management.

Grid Infrastructure Management Repository (GIMR)

The GIMR feature, introduced in 12c for logging cluster events, became mandatory in version 12.1.0.2 and later optional in 18cR5. Deprecation started in 21c, and it is no longer supported in 23ai.

Policy-Managed Databases

Previously, Oracle RAC allowed setting databases to Policy-Managed mode, enabling dynamic resource allocation through server pools. However, Oracle deprecated this in 21c, and from version 23ai, only Admin-Managed mode is supported.

These changes reflect Oracle’s ongoing efforts to streamline and modernize its database solutions. DBAs must adapt to these updates to maintain optimal system performance.

Vahid Yousefzadeh
Oracle Database Administrator
Telegram channel :https://t.me/oracledb

Comments

Post a Comment

Popular posts from this blog

Oracle 23ai — Speed up IMPDP Using NOVALIDATE Constraints

By -
  When executing the   IMPDP   command, some operations do not support parallel execution. Creating constraints is one such operation. Oracle must validate the current data in the table before creating a constraint, which requires a full table scan for each validation. This process can be very time-consuming. Consider the following constraints: ALTER TABLE VAHID.MYTB ADD CONSTRAINT CHECK1 CHECK (col3 > 50 ); ALTER TABLE VAHID.MYTB ADD CONSTRAINT CHECK2 CHECK (col9 IN ( 5 , 15 )); We drop the  MYTB  table and recreate it using a dump file: SQL > drop table mytb; Table dropped. W -1 Processing object type TABLE_EXPORT / TABLE / TABLE_DATA W -1 . . imported "VAHID"."MYTB" 19 GB 337830912 rows in 83 seconds using external_table W -1 Processing object type TABLE_EXPORT / TABLE / CONSTRAINT / CONSTRAINT W -1 Completed 2 CONSTRAINT objects in 208 seconds As shown, creating the two constraints ta...
Read more

Staging Tables in Oracle 23ai

By -
  As you may know, using   staging tables   is a common practice in   Data Warehouse   environments, primarily during the data loading process into the   Warehouse Database . Typically, raw data received from   source databases   is first loaded into a temporary area, referred to as   staging tables . After cleansing inconsistent and invalid data and transforming it into a standard format, the cleaned data is stored in the final operational tables. In addition to initial data loading,   staging tables   are also used for updates and are often truncated before reuse. In   Oracle 23ai , a new minor feature has been introduced for this purpose, allowing users to create tables specifically designed as   staging tables . This is achieved by adding the   FOR STAGING   clause to the   CREATE TABLE   statement. Creating Staging Tables Using the   FOR STAGING   clause, staging tables can be created as ...
Read more

Oracle 23ai — Track Table and Partition Scan Access

By -
Image
  In Oracle 23ai, a new view named   [dba|all|user]_table_access_stats   has been introduced, enabling users to view the access history of tables and partitions. This view shows how many times each table or partition has been scanned in each instance and the last time a table was accessed. SQL > create table jadval(id number, name varchar2( 100 ), last_name varchar2( 100 )); Table created. SQL > insert into jadval values ( 1 , 'payan' , 'rafat' ); 1 row created. SQL > select TABLE_NAME, PARTITION_NAME, INSTANCE_ID, READ_COUNT, LAST_ACCESSED_TIME from user_table_access_stats; no rows selected SQL > select * from jadval; ID NAME LAST_NA ---------- ------- ------- 1 payan rafat SQL > select TABLE_NAME, PARTITION_NAME, INSTANCE_ID, READ_COUNT, LAST_ACCESSED_TIME from user_table_access_stats; TABLE_NAME PARTITION_NAME INSTANCE_ID READ_COUNT LAST_ACCESSED_TIME ---------- --------------- ----------- --------...
Read more