3This is a Safe Harbor Front slide, one of two Safe Harbor Statement slides included in this template.One of the Safe Harbor slides must be used if your presentation covers material affected by Oracle’s Revenue Recognition PolicyTo learn more about this policy,For internal communication, Safe Harbor Statements are not required. However, there is an applicable disclaimer (Exhibit E) that should be used, found in the Oracle Revenue Recognition Policy for Future Product Communications. Copy and paste this link into a web browser, to find out more information. For all external communications such as press release, roadmaps, PowerPoint presentations, Safe Harbor Statements are required. You can refer to the link mentioned above to find out additional information/disclaimers required depending on your audience.
4Program Agenda1Why Upgrade ? Overview and Concept Upgrade Tools and Best Practices Useful References for Upgrade234
5Why Upgrade To 12c Release 1 ? Benefits of upgrading the databaseNew FeaturesUseful and Desirable FeaturesImprove PerformancePotential Cost SaverEasy AdministrationIncrease Support LengthPremier Support until July 2018Extended Support until July 2021Premier SupportSave Extended Support FeePatchset, PSU,SPU and other Bug fixes are available
6Upgrade Vs MigrationUPGRADEThe process of changing the data dictionary contents of a database to reflect a newer releaseNo User or Application data will be touched or modifiedIndependent of the size of the databaseMajor Release Upgrade : Upgrading from 11.2 to 12.1Patchset Upgrade :Upgrading from toMIGRATIONMove to new OS ,hardware and character set conversation.Dependent on the size of the database
15Install the latest Software Reduce patching downtime:Install the LATEST PATCHSET or BASE RELEASEPatchset is complete installation software from OnwardsInstall the Binaries in new Oracle home . Recommended: OUT OF PLACEApply the latest PATCH SET UPDATE for Unix and BUNDLE PATCH for WindowsThe first PSU for will be released on October 2014Apply Interim Patches for Known issueNote : Quick Reference to Patch Numbers for Database PSU, SPU(CPU), Bundle Patches and Patchsets
16Upgrade Grid Infrastructure Upgrade Grid Infrastructure BEFORE upgrading the Oracle DatabaseInstall the Grid Infrastructure in NEW Oracle home ( Out-of Place Upgrade)Oracle Grid Infrastructure HomeOracle Database Server HomeNote How to Upgrade to Oracle Grid Infrastructure 12c Release 1 and Known Issues
17Pre Upgrade Checklist Source Oracle home VALIDATEInvalid database OBJECTS in SYS and SYSTEM schemaInvalid database COMPONENTSSYS and SYSTEM does not have DUPLICATE OBJECTSCLUSTER_DATABASE is set to FLASEREMOVEHIDDEN parameter and EVENTSDEPRECATED parameterOBSOLETE database COMPONENTSRECYCLE BIN objectsCREATEGather StatisticsPreserve StatisticsBackup of the Database
18New Pre-Upgrade Information Tool :preupgrd.sql Upgrade SQL Automationpreupgrd.sql is introduced in 12c R1It has replaced utlu<nnn>i.sqlRuns in the source DatabaseGenerates Fix up scriptspreupgrade_fixups.sqlpostupgrade_fixups.sql
19Prepare Source database Run Preupgrade Tool on the Source DatabaseExecute preupgrd.sqlLocation: $ORACLE_BASE/cfgtoollogs/<SID>/preupgradeLogs generated by preupgrd.sqlCopy preupgrd.sql &Utluppkg.sqlSource DBTarget DBpreupgrade.logpreupgrade_fixups.sql- postupgrade_fixups.sql
20Preupgrade Checks Compatible Parameter Check OCM user existence check $ORACLE_BASE/cfgtoollogs/<SID>/preupgrade/preupgrade.log$ORACLE_BASE/cfgtoollogs/<SID>/preupgrade/preupgrade_fixups.sqlCompatible Parameter CheckOCM user existence checkGather dictionary statistics
21Remove Obsolete Components Enterprise Manager Database Control Repository is superseded in 12c By EM ExpressRemove EM repositoryIt will be automatically removed during the catuppst.sql post-upgrade phase.$emctl stop dbcontrol?/rdbms/admin/emremove.sqlRemove Oracle UltraSearch before doing the upgradeOracle UltraSearch does not exist in Oracle Database 11.2 and onwardsFor Oracle Database 10.2?/ultraserach/admin/wk0deinst.sql SYS password ‘‘ ‘‘
22Oracle Label SecurityEssential Step if Oracle Label Security and/or Database Vault was already in the database before upgradeExecute olspreupgrde.sql in source Database?/rdbms/admin/olspreupgrade.sqlPrepares the move of AUD$ table from SYSTEM to SYS.Processes the audit records to minimize downtime.Move records to an interim temporary table.
23Time Zone Version Pre or Post Upgrade Actions Default Time Zone Version 12c R1 is DST V18If Time Zone version at source database HIGHER than target databaseApply the Time Zone patch on target to match the source database versionIf Time Zone version at source database LOWER than target databaseTime Zone conversion need to be done post upgrade.Most Recent Time Zone version is DST V22Time Zone definitions in $OH/oracore/zoneinfoNote Scripts to automatically update the RDBMS DST (timezone) version in an 11gR2 or 12cR1 database
24Backup the DatabaseTake a backup of the Database.Always create a valid and complete online backup with RMANTest the restore and the recovery at least once.Make sure your fallback strategy covers during and after cases
25Compatible Parameter Compatible 11.0.0 or higher is MUST Minimum COMPATIBLE parameter for 12c isLeave COMPATIBLE at the original value for a week before changing toNo way back once COMPATIBLE set toCompatible or higher is MUSTDowngrade NOT possibleCompatible remain to 11.x.xDowngrade possibleDatabase restart is required to change the COMPATIBLE parameter laterSQL> alter system set compatible = '12.0.0' scope=spfile;SQL> Shutdown immediate ;SQL> conn / as sysdbaSQL> startup
26Diagnostic Collection Script (dbupgdiag.sql) Note : Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql)
27New Upgrade Utility : catctl.pl It is introduced in Oracle database server 12c R1It loads the data dictionary and components in PARALLELDefault Parallelism 4Maximum Parallelism 8catctl.pl supported options
2812c Upgrade Start the Database in UPGRADE mode using the 12c binaries Exit the sqlplus
2912c Upgrade ParallelismStart the upgrade on the Shell with catctl.pl with PARALLEL option .
3012c Upgrade Logs Default log location is current working directory Use –l parameter to specify the log locationOne log file for each threadUpgrade is running with 8 Parallel processesTotal DB components upgrade time
31Post Upgrade Checklist Target Oracle homeEXECUTE$ORACLE_HOME/rdbms/admin/utlrp.sql$ORACLE_HOME/rdbms/admin/utlu121s.sqlUPGRADETIMEZONE versionCREATESPFILE for PFILEGather STATISTICSBACKUP of the database
32Post Upgrade Fixups TimeZone Version Check $ORACLE_BASE/cfgtoollogs/<SID>/preupgrade/preupgrade.log$ORACLE_BASE/cfgtoollogs/<SID>/preupgrade/postupgrade_fixups.sqlTimeZone Version CheckGather Fixed Objects Statistics
33Verify Upgrade Logs Review Upgrade logs and traces DBUA logs $ORACLE_BASE /cfgtoollogs/DBUA/<SID>/upgrade<n>If ORACLE_BASE is set$ORACLE_BASE /cfgtoollogs/DBUA/<SID>/upgrade<n>If ORACLE_BASE is NOT set$ORACLE_HOME /cfgtoollogs/DBUA/<SID>/upgrade<n>Manual upgrade logsLocation Specified using - l parameter of catctl.plCurrent working directoryCheck alert_SID.logutlu121s.sql output
34Verify UpgradeNew successful upgrade status for CATALOG and CATPROC componentRun the utlrp.sql to change the status to VALID