Back to Blog
Oracle workspace manager invalid 11g5/26/2023 To perform an upgrade in High Availability environment, there would be 16 steps : The primary server is named ODA-PRI (running DB1_RZA database) and the standby server is named ODA-STD (running DB1_RZB database). In this procedure I have been upgrading database named DB1 from 11.2.0.4 to 12.1.0.2 version. Although, I would expect that for any productive database, customer would have a similar test database on which he would perform a good testing. One of the advantage here would be to use the Standby Database as fallback in case there would be some application issue with new database version. High Availability using Data Guard for Oracle Enterprise Edition or dbvisit for Oracle Standard Edition 2. None of the fixed object tables have had stats collected.Through this blog, I would like to show, with a real customer case, how I have been migrating databases in High Availability environment on an ODA. (AUTOFIXUP) Gather statistics on fixed objects prior the upgrade. Recommends gathering dictionary statistics in the last 24 hours beforeįor information on managing optimizer statistics, refer to the 12.2.0.1Ģ. (AUTOFIXUP) Gather stale data dictionary statistics prior to databaseĮXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS ĭictionary statistics do not exist or are stale (not up-to-date).ĭictionary statistics help the Oracle optimizer find efficient SQLĮxecution plans and are essential for proper upgrade timing. Oracle Component Upgrade Action Current Status Report generated by Oracle Database Pre-Upgrade Information Tool Version View Preupgrade ~]$ cat /home/oracle/CID/preupgrade/preupgrade.log Log into the database and execute the postupgrade complete: ~]$Ĥ. Log into the database and execute the preupgrade After the upgrade: home/oracle/CID/preupgrade/postupgrade_fixups.sqlĮxecute fixup scripts as indicated below: home/oracle/CID/preupgrade/preupgrade.log /home/oracle/CID/preupgrade/preupgrade_fixups.sql The Oracle base has been set to ~]$ /u01/app/oracle/product/12.2.0/dbhome_1/jdk/bin/java -jar /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/preupgrade.jar FILE DIR /home/oracle/CID/preupgrade u01/app/oracle/product/12.2.0/dbhome_1/jdk/bin/java -jar /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/preupgrade.jar TERMINAL TEXT Set COMPATIBALE parameter value to 19.0.0 Copy init and password files from 12c to 19c dbs homeĢ7. Create Flashback Guaranteed Restore Pointġ5. Check Compatibility Before Upgrading Oracle Databaseġ3. Upgrade Oracle Database Manually from 12.2.0.1 to 19c (NON-CDB)Ġ. How to START/STOP PostgreSQL 13 on Linux.Install PostgreSQL 13 using yum Repository on Linux.Add Targets Manually on EM Cloud Control 13c.Rolling Upgrade With an Existing Physical Standby Database.Upgrade Oracle Database Manually from 12.2.0.1 to 19c.Upgrade Oracle Database from 12.2.0.1 to 19c using DBUA. ![]()
0 Comments
Read More
Leave a Reply. |