Use the following command to check the database invalids. If downtime is not allowed for database, complete RMAN level0 backup.ġ.5 Check invalid objects and run utlrp.sql script if you have any invalids We always prefer consistant RMAN level0 backup if the downtime is offordable. Oracle Workspace Manager VALID 12.1.0.2.0ġ.2 Disable the custom triggers that would fire before/after DDL and enable them after the upgrade is complete.īased on your exisint backups strategy, complete the level0 backup. Oracle Real Application Clusters OPTION OFF 12.1.0.2.0 Oracle Database Packages and Types VALID 12.1.0.2.0 Oracle Database Java Packages VALID 12.1.0.2.0
Oracle Database Catalog Views VALID 12.1.0.2.0 Oracle Application Express VALID 4.2.5.00.0 JServer JAVA Virtual Machine VALID 12.1.0.2.0 SQL> select substr(comp_name,1,40) comp_name, status, substr(version,1,10) version from dba_registry order by comp_name Use the following command to list the Database components status along with version. We have another post that describes the Database Vault and Oracle Label Security considerations when upgrading a database.įor reference, note the direct upgrade path. We also assume that Oracle Database Vault and Oracle Label Security are not enabled in this database. We assume for this post, that we already have a Non-CDB database 12.1.0.2 up and running on linux OS.
#Remove owm oracle workspace manager oracle manual#
I have few other posts where I explained manual upgrade process. The purpose of this post is to give you the introduction to the process of database upgrade. Those points really vary from environment to environment. Though the upgrade using DBUA is simple, we need to consider many other points based on your environment. In this post, we will discuss about Oracle Database 18c upgrade from 12.1.0.2 to 18.0.0.0.
0 kommentar(er)
