Enterprise Manager 12c 'Database Lifecycle Management' provides automation and standardization into the complex process of upgrading Oracle Databases across versions. Leverage EM12c automation capability to upgrade to Oracle Database 12c.

1. 1 Copyright © 2011, Oracle and/or its affiliates. All rights
reserved.
Automate Database Upgrades using Enterprise
Manager 12c
Hari Srinivasan
Product Management

2. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 122
Oracle 11.2.0.4
Upgrade Options across releases via EM12c
Oracle 11.1
Oracle 11.2.0.1/2
Oracle 10.2
Oracle 11.2.0.3
HW
Oracle 12.1.0.1
HW
Oracle 11.1.0.7
Oracle 10.2.0.5
Patchset Upgrades
HW Not across hardware

3. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 123
Complete Database Upgrade
Upgrade in Scale, exercise flexibility
 Upgrade different Database
family of products.
 Supports:
– Complete stack : Upgrade
Clusterware/GI + RAC DB in a
cluster
– Flexibility: Upgrade GI only and
then Upgrade RAC DBs
– In Scale: Upgrade one or
many/all DBs at the same time.

4. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 124
Comprehensive Pre Upgrade Checks
 Comprehensive Pre Upgrade Checks
– Runs checks at both GI and Database
layers.
– Executes RAC Check,
Cluster Verification Utility (CVU), Pre-
upgrade utility.
– Automated downloaded of latest version of
the tools.
– Includes automated fix-up(s) for issues that
could be resolved without intervention.
– Provides diff. report on re-runs for RAC
check.
Integrated pre-check tools and fix-ups

5. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 125
Comprehensive Pre Upgrade Checks
 Comprehensive Pre Upgrade Checks
– Runs checks at both GI and Database
layers.
– Executes RAC Check,
Cluster Verification Utility (CVU), Pre-
upgrade utility.
– Automated downloaded of latest version of
the tools.
– Includes automated fix-up(s) for issues that
could be resolved without intervention.
– Provides diff. report on re-runs for RAC
check.
Integrated pre-check tools and fix-ups

6. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 126
Effectively manage Downtime
Stage Software
Run pre-requisite checks
Run fix-ups
Any other manual intervention
Phase and Parallelize Upgrade
Upgrade Database(s)
Upgrade Grid Infra. (Rolling)
Downtime
• Set Break points to phase the upgrade
• Upgrade Databases in Parallel
• Multiple RAC DBs at the same time across
the nodes.
Deploy Software
Breakpoints

7. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 127
Back up and Restore
 Restore available for both Software
and Database.
– Downgrade Grid Infrastructure
– Restore DB from Backup
 Pick a backup option.
– Inline backup of the Database
before the upgrade process.
– Ignore, if you want to
handle with separately.
 Generic error handling
options available for
failures.
Handling Failures and Recovery

8. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 128
Upgrade Data Guard Databases
 Supports upgrade of primary and
its multiple standby databases in
rolling mode.
 Upgrade GI OH (in case of RAC)
or deploy DB OHs before the
process starts.
 Uses Active Data Guard on the
primary database and the
physical standby database to
perform the rolling upgrade.
Automated rolling transient logical standby database upgrades

9. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 129
Database Upgrades – Feature Summary
Automation in Scale
 Upgrade Standalone, RAC, and Data guard (Primary-
Standby) Databases from older versions to higher versions
(supports DB12c)
 RAC Database Upgrades:
 Full stack upgrade covering Grid Infrastructure and RAC DBs
 Flexibly upgrade to suit the operational and testing needs (GI
only, Few RAC DBs or All RAC DBs)
 Minimize downtime by upgrading software and Database
separately
 Comprehensive pre-requisite checks including RAC
checks, cluster verify (CVU) checks , can be updated directly
from MOS
 Integrated back up and restore policies
 Rolling Upgrade using Transient logical standby for Data
Guard based Primary and Standby Databases
 Support upgrading multiple standby environments
Oracle Data Guard

10. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 1210
Demo

11. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 1211
11
Commonly Asked Questions
How do I reduce downtime? Can I speed up my upgrade process?
Can this process be made standard and repeatable ?
How do I best manage my upgrade process across many clusters?
What happens in failure? Can EM help in handling or recovering?
How can I best use this automation across multiple datacenter locations?
Can EM handle the "ROOT steps" in the process?

12. 12
Reduce Downtime and Increase Speed
Best Practice Recommendation 1
Use Breakpoints to phase out the
process:
Run Pre-requisites & Deploy
Software (No Downtime)
Upgrade Cluster (Rolling)
Upgrade Database (Downtime)
Switch to upgrade in ‘Parallel’ for
multiple Databases:
Upgrade databases in parallel
within an Oracle Home.

13. 13
Make Upgrade Process Repeatable & Standard
Best Practice Recommendation 2
Lock the input values
Save the procedure with its
inputs and publish it to other
DBAs. This defaults all values
leaving just to pick the target to
upgrade.

14. 14
Automate or Pause at ‘root’ steps
Best Practice Recommendation 3
Automate ‘root’ steps - Create named credentials for ‘root’ user via SUDO/PBRUN.
(foo – sudo to – root)
OR
Skip Root to Pause at ‘root’ steps with approp. Command to run offline.

15. 15
Handling Failures and Recovery
Best Practice Recommendation 4
Failures: Procedure activity enables tracking upgrade in real time.
Upon failure, user can review the Log details of every micro step.
Some failures can be handled with ‘retry’ or ‘ignore’.
Restore: Automated restore of Grid Infrastructure back to the old release.
Restore DB from the back up. (Select atleast an incremental backup before upgrade)

16. 16
Upgrade at Scale
Best Practice Recommendation 5
Create a Change Activity Plan (CAP) to track upgrade across datacenter.
Aditionally, scriptize using EM Command Line Interface (EMCLI).

17. 17
Upgrade across Datacenters
Best Practice Recommendation 6
Reduce software sharing and transport cost by creating local software library
components in the remote datacenter.
NFS based reference option:
• Copy s/w library to NFS location
• Replicate storage and copy to
other sites
• Recreate the components with
metadata from master s/w library
Agent based reference option:
• Copy s/w library to location in
agent host
• Replicate it to other EM’s agent
locations
• Reference and create
components in other s/w library

18. Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 1218
Resources
Lifecycle Management on OTN
http://tinyurl.com/em12lcm