How to Upgrade Oracle Database from 19C to 21C step by step activity Guide

 Dear All,

In this post i am going to share , How to Upgrade 19C database to 21C Database step by step .

you can perform a direct upgrade to Oracle database release 21c from the following releases:

Any 19c
Any 18c
12.1.0.2 or 12.2.0.1
11.2.0.3 or  11.2.0.4

Source Database server details :   19C 

192.168.56.127  testdb.localdomain

Target Server details : 21C 

192.168.56.128  stand.localdomain 

Prechecks :  

Install 21C database on same or different server follow this link to install the s/w.

https://www.youtube.com/watch?v=LucXkSAmchw

Need to Put the source pdb in read only mode than ..

Source Database : 

Note : Important Changes / Updates  in 21C Database 

• In Oracle Database 21c, when the COMPATIBLE initialization parameter is not set in your parameter file, the COMPATIBLE parameter value defaults to 21.0.0

• Starting with Oracle Database 21c, Database Upgrade Assistant (DBUA) is replaced by the AutoUpgrade utility

• Starting with Oracle Database 21c, the default network administration directory changes from the previous default in the local Oracle home, Oracle_home/network (for example, //u01/app/oracle/product/19.0.0/db_1/network/admin), to a new location

• The new default location is the shared Oracle Base Home, in the path ORACLE_BASE/ homes/HOME_NAME/network/admin ( example /u01/app/oracle/homes/OraDB21Home1/network/admin/listener.ora )

• Starting with Oracle Database 21c, an Oracle Database installation configures all Oracle Database homes in read-only mode by default ...

Note last what is being changed about security and parameters:

• Starting with Oracle Database 21c, the data types DBMS_CRYPTO_TOOLKIT_TYPES and package DBMS_CRYPTO_TOOLKIT are DE-supported

• The init.ora parameters UNIFIED_AUDIT_SGA_QUEUE_SIZE, UNIFIED_AUDIT_SGA_QUEUE_SIZE, AUDIT_FILE_DEST, AUDIT_SYS_OPERATIONS, AUDIT_SYSLOG_LEVEL and AUDIT_TRAIL have been DE supported

• DE supported of IGNORECASE parameter for passwords
  Starting in Oracle Database 21c, the IGNORECASE parameter for the orapwd file is DE supported and all newly created password files are case-sensitive

• DE-supported of DISABLE_DIRECTORY_LINK_CHECK
  The DISABLE_DIRECTORY_LINK_CHECK parameter is DE-supported, with no replacement

Unplug Source PDB1 From 19c database :

Copy this PDB1 data to 21C database : 

check the backup files received on Target database : 

Create new PDB on 21C database using 19c PDB data / backup

Check the status of the PDB and startup with upgrade option .

Wait for some time in this step ..  this will take around 20 to 30 mins depends on server capacity and database size and other parameter .. 

SQL> show pdbs

    CON_ID CON_NAME                       OPEN MODE  RESTRICTED

---------- ------------------------------ ---------- ----------

         2 PDB$SEED                       READ ONLY  NO

         3 PDB                            READ WRITE NO

         4 PDB1                           MOUNTED

SQL> select count(*) from dba_objects where status='INVALID';

  COUNT(*)

----------

         0

Database Upgrade Completed  ..  we need to validate the invalids and then we need to compile those invalids if anything  .

Check the PDB level Violations errors if anything  : 

select * from pdb_plug_in_violations where name='PDB1';

This Concludes our database upgrade completed successfully from 19C to 21C .

Thanks,

Srini