Upgrading Oracle Database to 220.127.116.11.0 Using DBUA
New FeaturesI will list out some of the new feature for upgrading your databases to 12c. You can review the complete details of the new feature by clicking the link in the references section.
- New Pre-Upgrade Information Tool- A new Pre-Upgrade Information Tool has been created for this release. The preupgrd.sql script replaces the utlu121s.sql script.
- Parallel Processing for Database Upgrade- In Oracle Database 12c, the catupgrd.sql Upgrade Utility has been replaced with the new catctl.pl Parallel Upgrade Utility.
- DBUA Can Be Restarted During the Upgrade Process- In this release, there are more options for recovering from failures during upgrade and for restarting the upgrade from the point where the failure occurred.
- Enhanced Pre-Upgrade and Post-Upgrade Summary Report- DBUA generates HTML reports before and after the upgrade.
Make sure you have a full valid database backup.
- Make sure your database is in archivelog mode
- Take a full backup using RMAN.
Pre-Upgrade Information Tool
Copy SQL scripts preupgrd.sql and utluppkg.sq
- $cd <12c_home>/rdbms/admin
- $cp preupgrd.sql /home/oracle/scripts/
- $cp utluppkg.sql /home/oracle/scripts/
- Under your ORACLE_HOME/cfgtoollogs or ORACLE_BASE/cfgtoollogs create directory <db_unique_name>/preupgrade
Execute Pre-Upgrade Scripts
- Login to the database you want to upgrade with SYS account
- Execute the preupgrd.sql script from the location where you copied the file.
Review Fixup and Log Files
Example Output from Preupgrade.log
After you have reviewed the scripts, Oracle recommends that you execute preupgrade_fixups.sql on the source database. The preupgrade_fixups.sql script will attempt to resolve issues reported by the preupgrade process.
Execute the preupgrade_fixups.sql before upgrading your database.
Make any manual changes to your database as needed based on the output from the preupgrade.log
Pre-Upgrade Information Tool Warnings and Recommendations for Oracle Database
Upgrade Database Using DBUA
2. Select upgrade Oracle database click next
3. Select the source Oracle home and the database to be upgraded click next.
4. Prerequisite checks will begin
5. Prerequisite check dialog will show any issue encounter during the checks and will have the option to fix it the validation is fixable. Click next
6. There is an option now to have the upgrade run in parallel so select the upgrade parallelism. Upgrade options can be set to recompile invalid objects during post upgrade. There are other options for Timezone, gather stats and set user tablespace to read-only during upgrade. There is options to change file location if needed. In the custom SQL scripts tab you can set a before and after custom SQL script to be executed.
7. Managment options can be set to configure EM Express of Cloud Control click next
In my case I left both unchecked.
In my case I left blank as I did not need to move my datafiles.
In my case the database dbtest2 that I am upgrading is already registered to my default listener.
In my case I choose RMAN backup with existing RMAN backup.
12.1 Click the activity log button to review the detail progress
13. When upgrade is complete click upgrade results
14. Review results if there were any issues here you would have the option of restoring the database. Click close
15. Database has been upgraded
Once you feel that your upgraded database is good change the compatible to 18.104.22.168.0
SQL>alter system set compatible='22.214.171.124.0' scope=spfile;
Require Post Upgrade Task
Recommend and Best Practices to Complete After Upgrade