This was presented at Oracle's 11g R2 Live seminars in June. It allowed customers and partners to view the benefits of implementing or upgrading to Oracle's latest version of it's database and Advanced Technology products such as Real Application Clusters, Real Application Testing and Enteprise Manager.

1. Morning Break

2. 11g Live Infrastructure
LIVESNAP
OEM 11g GC
LIVE
LIVESTBY

3. Real Application Testing - Replay
Database Replay

4. Select Database (live)

5. Select “Software and Support”

6. Select “Database Replay”

7. Select “Replay Workload”

8. Select “Use an existing
workload”
Click “Next”

9. Pull down the “Directory
Object”
Select “Rat_Replay”
Click “Next”

10. Select “Use the default
options”
Click “Next”

11. Click “Next”

12. Select “Add Replay Client
Hosts”

13. Select “onode3.au.oracle.com”
Click “Select”

14. Select “No” in the Configured
column

15. Database User Name :- system
Database password :- oracle
Client Oracle Home :- /u01/app/oracle/product/11.2.0/db
Client Replay Directory :- /home/oracle/rat_replay

16. Column Configured is “Yes”
Click “Next”

17. Wait until “Actual Number of Client
Connections” = 1
Click “Next”

18. Click “Submit”

19. Select “Targets”
Select “Databases”
Click on “livesnap” database
Click on “Workload Replay On”

20. Workload Replaying – Click on
“Refresh”

21. Covert Snapshot Standby Back to
Physical

22. Select Database (live)

23. Select Availability

24. Select “Setup and Manage”

25. Click “Convert”
Select
“livesnap”

26. Click
“Yes”

27. Converting from Snapshot
Standby to Physical Standby

28. Converted back to Physical
Standby

29. Active Data Guard Report
Offload

30. Select Database (live)

31. Select Availability

32. Select “Setup and Manage”

33. Select Real-time Query
“Disabled”

34. Select “Enable Real-time
Query”
Then “Apply”

36. Property changes have been
applied
Click on the “Data Guard” link

37. Active Data Guard enabled

38. Two Management Styles
for Oracle RAC
• Administrator Managed
– Specifically define where the database should run with a list
of servers
– Define where services should run within the database
• Policy Managed
– Define resource requirements of workload
– Enough instances are started to support workload
requirements
– Goal: To remove hard coding of a service to a specific
instance or node

39. Server Pool
• Logical division of the cluster into pools of servers
• Applications (including databases) run in one or more
server pools
• Managed by crsctl (applications), srvctl (Oracle)
• Defined by 3 attributes (min, max, importance) or a
defined list of nodes
– Min- minimum number of servers (default 0)
– Max – maximum number of servers (default 0 or -1)
– Importance – 0 (least important) to 1000

40. Server Pool Example – Instance View
public network
VIP1 VIP3 VIP4
Scan_LSNR Scan_LSNR Scan_LSNR
Listener Listener Listener
instance 1 cluster instance 1 instance 2
interconnect
ASM ASM ASM
Oracle Clusterware Oracle Clusterware Oracle Clusterware
Operating System Operating System Operating System
backoffice shared storage frontoffice
Min 1 Max 2 Imp 3 Min 1 Max 2 Imp 4
Redo / Archive logs all instances
Database / Control files
Managed by ASM
OCR and Voting Disks

41. Cluster Managed Services with Server
Pools
• One to one mapping
– (ie. a service can only run in one server pool )
• Services are
– uniform (run on all instances in the pool)
– singleton (runs on only one instance in the pool)

42. Pre Relocation
LIVE LIVESTBY
Front_Office Back_Office Back_Office Generic
Min 1 Max EC Imp 5 Min 1 Min 1 Max EC Imp 5
Max EC
Imp 2
OLTP OLTP REPORTS REPORTS REPORTS
1 2 3 1 2 3

43. Post Relocation
LIVE LIVESTBY
Front_Office Back_Office Generic
Min 1 Max EC Imp 5 Min 1 Max EC Imp 5
OLTP OLTP OLTP REPORTS REPORTS
1 2 3 1 2 3

44. Sever Pools Dynamic
Re-Allocation and
Active Data Guard

45. Driver Type : OCI JDBC Driver
“reports” is the connect string
Only select “Read Only”
transactions

46. Driver Type : OCI JDBC Thin
“oltp” is the service
Only select all transactions

47. Select Targets

48. Select Databases

49. Select Database (live)

50. Select “Server Pool(s)”

51. Login
Username – oracle
Password - oracle

52. Relocate Servers
Select ora.front_office
Note : Current Size 2

53. Click
“Move”
Click “onode6
(ora.back_office)

54. Onode6 now in “Selected
Servers”
Click “Submit”

55. Click on “Continue”
Click on “Force
Relocate”

56. Note : Current Size of
ora.front_office now 3

57. <Insert Picture Here>
Database Upgrade to 11g – Wrap Up

58. Lifetime Support Policy today
R2 January 2015
August 2012 August 2015
July 2010 July 2013
R2
January 2009 January 2012
Sustaining Support
Premier Support Extended Support
July 2007 July 2008 July 2010
R2
t
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2016
2015
http://www.oracle.com/support/lifetime-support-policy.html

59. Upgrade to 11g
≥
7.3.4 R2 ≥
9.2.0.4
≥
8.0.6
≥
8.1.7.4
R2
≥
9.1.0.4

60. Upgrade is easier!
• The upgrade to Oracle Database 11g is much easier
than any upgrades to earlier Oracle releases
• Size of Upgrade guides:
– 8.1.7 - 512 pages
– 9.0.1 - 484 pages – 111 steps for an RDBMS with 9 components
– 9.2.0 - 344 pages
– 10.1.0 - 170 pages - only 6 stepsl!!!
– 10.2.0 - 140 pages
– 11.1.0 - 186 pages - now detailed explanations and
information about new options included

61. Upgrade Length
• How long will the upgrade take
to complete?
– Independent of:
– Size of the database
– Used datatypes
– Dependent on:
– The number of objects needing upgrading and recompilation
– Thus: the number of installed options/components
– The number of synonyms – they‘ll get recompiled
– Valid and non-stale data dictionary statistics
– At a very low rate:
– Number of datafiles
– Size of redo logs

62. Documentation
• Documents to study before you start?
– Note 785351.1 – Oracle 11G R2 Upgrade Companion
– Note:837570.1 - Complete Checklist for Manual Upgrades to
11gR2
– Note: 421191.1 - Complete checklist for manual upgrades from
X to Y

63. Further information
• 11g References:
Customer adoption of 11g is steadily growing!
Commonwealth Bank of Australia
NRMA Motor Services
Virgin Mobile
CarSales.Com And more......

64. Guidelines
• Never ever change to many system components at once!
• Document all changes detailed and clearly into a change log!
• Always (!!!) use real word data for testing!
• Don't underestimate the test efforts. Reserve enough time and
resources for testing.
• ALWAYS collect as much performance data BEFORE the
upgrade will be started!!
• Create a fallback strategy!
• PLEASE test your fallback strategy - does it really work??
• Please remember:
Upgrade never has been easier - but you still have to test!!!

65. For More Information
http://search.oracle.com
oracle database 11g
or
www.oracle.com/database