AGENDA
Presentation approximately 45 minutes
Q&A Session approximately 15 minutes
Web attendees can ask questions via Q&A panel
Phone attendees can ask questions via Q&A panel or
phone (operator assisted)
AGENDA
Presentation approximately 45 minutes
Q&A Session approximately 15 minutes
Web attendees can ask questions via Q&A panel only
Phone attendees can ask questions via Q&A panel or phone
(operator assisted)
Q&A panel
2
Ask: ALL PANELLIST leave default!
10
11
12
Agenda
Why Upgrade?
What Is An Upgrade?
10 Best Practices
Common Issues
Real World Examples
Q&A
13
Why Upgrade?
14
R2
January 2015
August 2015
August 2012
R2
January 2018
July 2013
January 2012
January 2009
Sustaining Support
Premier Support
Extended Support
R2
July 2010
t
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
15
What is upgrade?
Upgrade is the process of changing the data dictionary contents of a
database to reflect a newer release of the server.
Upgrades and downgrades supported from a specific set of versions.
Upgrading from 10.2 to 11.2 is a major release upgrade.
Upgrading from 11.2.0.1 to 11.2.0.3 is a patch set upgrade.
16
7.3.4
9.2.0.8
R2
9.2.0.4
8.0.6
R2
8.1.7.4
10.1.0.5
10.2.0.2
9.0.1.4
R2
"Empty" arrows mean: no specific patch release required
17
10 Best Practices
18
Best Practice #1
19
Documentation
Note 250.1 Upgrade Advisors
20
Documentation
Note:251.1 Database Upgrades from 10.2 to 11.2
21
Documentation
Note:785351.1 Upgrade Companion 11g Release 2
22
References
Note264.1 : Database Upgrades from 9.2 to 11.2
Note785351.1: Upgrade Companion 11g Release 2
Note 837570.1 : Complete Checklist for Manual Upgrades to 11g
Release 2
Note 421191.1: Complete checklist for manual upgrades from X
to Y
Upgrade Guides:
http://download.oracle.com/docs/cd/E11882_01/server.112/e108
19/toc.htm
OTN Upgrade Page:
http://www.oracle.com/technetwork/database/upgrade/index.html
Upgrade Blog: www.blogs.oracle.com/UPGRADE
23
Best Practice #2
Use the Upgrade Planner in My Oracle Support
24
Best Practice #3
Install the latest 11gR2 patch set into a new
ORACLE_HOME to upgrade database
Download patch set 11.2.0.x from support.oracle.com
The latest patch set are listed in the following note:
Note 753736.1 :Quick Reference to Patchset Patch
Numbers
Apply latest available CPU/PSU patch to your new
$ORACLE_HOME before upgrade
Apply recommended patch bundles and one-off patches
25
26
Best Practice #4
Pre-upgrade sanity operations
Oracle provided invalid objects.
Database components .
Duplicate objects .
Gather Dictionary Statistics.
Pre-Process AUD$ record.
Purge recycle bin.
Remove obsolete, deprecated and hidden parameters .
27
28
29
30
31
Sanity operations :
Pre-Process AUD$ record or Truncate SYS.AUD$ (if not required)
Note 1329590.1 : How to Pre-Process SYS.AUD$ Records PreUpgrade From 10.1 or later to 11gR1 or later. OR
SQL> truncate SYS.AUD$;
32
Best Practice #5
Always run the pre-upgrade script regardless of using the
DBUA or Manual Upgrade process
Always implement the recommendation suggested by pre-upgrade
script .
Stored in: $OH_11g/rdbms/admin OR Download the newest
version of the pre-upgrade check script utlu112i.sql:
Note 884522.1: How to Download and Run Oracle's Database
Pre-Upgrade Utility
Download and run dbupgdiag.sql script before & after upgrade
Note 556610.1: Script to Collect DB Upgrade/Migrate Diagnostic
Information (dbupgdiag.sql)
dbupgdiag script as an information gathering script. It does not
replace the utlu112i.sql it complements it.
33
Pre-Upgrade Checks
Upgrade information script: utlu112i.sql
Run in the environment of the source database
Spool the output into a file:
Checks all init parameters and displays warnings for obsolete and
deprecated parameters
Does checks for:
Components status
Tablespace SYSAUX
Character set
Time zone file version
Cluster
34
With Oracle Grid Infrastructure 11.2, ASM and Oracle Clusterware are
installed into a single home directory, which is referred to as the Grid
Infrastructure home.
35
36
37
38
Best Practice #6
Leave COMPATIBLE at the original value for a week before changing to
11.2.
COMPATIBLE has to be at least 10.1.0 for an 11g database
No way back once >= 11.2.0 has been enabled
Supported release downgrade to 10.1.0.5, >=10.2.0.2, >=11.1.0.6
No ALTER DATABASE RESET COMPATIBILITY command anymore
39
Best Practice #7
Test fallback strategy
In any case: Take a backup!!!
Always:
Create a valid and complete online backup with RMAN
Test the restore and the recovery at least once!!!
Make sure your fallback strategy covers both cases:
Problems encountered during the upgrade
Problems found days, weeks after the upgrade
If anything unforeseen happens and you'll have to step back, will you
be allowed to lose data (i.e. changes done to the data in the system
after the upgrade): YES or NO?
If YES: restore a backup, flashback (since 10g)
If NO: export/import, downgrade, Oracle Streams, Oracle Golden
Gate
2012 Oracle Corporation Proprietary and Confidential
40
41
42
Best Practice #8
Choose Upgrade PATH
43
44
45
Best Practice #9
Verify upgrade
The DBUA has "spool" and "echo" on by default, Find the logs at:
For DBUA
$ORACLE_HOME/cfgtoollogs/dbua/<dbname>/upgrade<n>/
For manual method logs can be found at spooled location.
Recompiling invalid objects
SQL> @?/rdbms/admin/utlrp.sql
Post-upgrade tool/utility
Check if all components are valid: utlu112s.sql or query
DBA_REGISTRY view for current status
Dbupgdiag.sql output (run and check script to collect DB
Upgrade/Migrate Diagnostic Information Note 556610.1)
Check alert<sid>.log
46
Always create an editable init.ora from the current SPFILE after the
upgrade has been finished
Prevents rewrite in case of setting wrong parameters or forced edit
Keep in mind:
The SPFILE is binary file!!! Don't edit it!! Default since Oracle 9.0
It simply will exist after using DBUA or DBCA
Parameter can be changed by:
SQL> create pfile='/tmp/initDB.ora' from spfile;
SQL> startup force pfile=/tmp/initDB.ora
SQL> create spfile from pfile;
SQL> alter system set PARAMETER=VALUE scope=both;
47
Common issues
ORA-00904: "TZ_VERSION": invalid identifier
48
TimeZone Patch
Cause : Source database is using TZ version files higher than defaultTZ
version files shipped with Oracle 11gR2.
Solution: Apply the TZ version patch on the Oracle 11gR2 home to
match the TZ version files at source.
49
Cause: You have set the compatible to the higher release and now try to
open or downgrade the database with lower release binaries .
Solution: Restore the database using backup and then open the with
lower release binaries .
50
51
52
53
54
55
Q&A panel
2
Ask: ALL PANELLIST leave default!
56
57
58
59
THANK YOU
60