Maximizing Oracle Database availability with Oracle RAC One Node

Learn why Oracle RAC One Node is the “always-on” single instance database, how it can improve service levels in your environment and make it easier for you to respond to the change. Learn how to efficiency consolidate your environment and eliminate planned and unplanned outages.

Transcript

1. SIOUG Conference 2011 Maximizing Oracle Database Availability with Oracle RAC One Node 1 Svetoslav Gyurov CNSys PLC 19 September 2011 Portorož, Slovenia
2. About me Senior DBA at CNSys PLC Responsible for system and database integrations. Working with Linux for 12 years, started with Slackware 3.6, Kernel 2.0.34 2 Slackware 3.6, Kernel 2.0.34 Working with HP-UX for 6 years Started with Oracle 10g Oracle Certified Professional DBA 9i, 10g HP-UX Certified System Expert 11iv2, 11iv3
3. Agenda • Overview • Deployment • High Availability • Consolidation 3 • Demo
4. Agenda • Overview • Deployment • High Availability • Consolidation 4 • Demo
5. RAC One Node • New option to the Oracle Database 11.2 EE. • Unlike the Oracle RAC feature, RON is not available with SE. • The only new database addition with this release. • Introduced first with 11.2.0.1 • Apply 9004119 to get the text based utilities. 5 • Apply 9004119 to get the text based utilities. • RAC One -- Changes in 11.2.0.2 [ID 1232802.1] • OUI and DBCA aware from 11.2.0.2. • Oracle RAC One Node is a single instance of an Oracle RAC enabled database.
6. RAC One Node • RAC One Node is an option of Oracle 11.2 EE. • $10,000 per processor. • Eligible for upgrade to full RAC. • All nodes on which RAC One Node is installed must be licensed for RAC One Node 6 be licensed for RAC One Node • RAC One node is eligible for 10-day rule in a calendar year. • Oracle RAC One Node can be online upgraded to full Oracle RAC (license!). • Supported on all platforms on which Oracle RAC is certified! • No additional certifications for RON.
7. The “Always on” single instance database • Solution to reduce planned downtime. • Online database relocation. • Online storage and server replacement. • Online OS and DB patching. 7 • Solution to reduce unplanned downtime. • Database Cold Failover. • Better storage and server resource utilization. • Instance caging and ASM.
8. Agenda • Overview • Deployment • High Availability • Consolidation 8 • Demo
9. Create RAC One Node 11.2.0.2 database • Install and configure 11.2.0.2 GI on all nodes. • Install 11.2.0.2 DB software by selecting RAC One in all nodes. • Create a RAC One Node database using DBCA. 9 • Create service – setup TAF or FAN correctly.
10. Database installer 11.2.0.2 10
11. Database Configuration Assistant 11.2.0.2 11
12. Typical deployment Server1 DB1 DB2 Server 2 DB3 instance 1 instance 1 instance 2 12 DB1 DB2 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3
13. Agenda • Overview • Deployment • High Availability • Consolidation 13 • Demo
14. High availability • Oracle RAC One Node targets the failover market • But differs from other cold failover solutions. • Install rolling patches (no downtime). • Easy and online scale-out to multi-node RAC. 14 • RAC includes RAC One Node features. • OMotion - online migration of a database.
15. High availability • RAC One Node Support in Grid Control 11.1 [ID 1308490.1]. • Oracle RAC One Node is supported with Oracle Data Guard 11.2.0.2 • Dataguard Broker is RAC One aware. 15 • Dataguard Broker is RAC One aware. • Oracle RAC One Node is supported with Oracle Goldengate [1320094.1].
16. Online Database Relocation Server1 DB1 DB2 Server 2 DB3 instance 1 instance 1 instance 2 Client connections 16 DB1 DB2 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3
17. Online Database Relocation Server1 DB1 DB2 Server 2 DB3 instance 1 instance 1 instance 2 Client connections DB2 instance 2 Omotion 17 DB1 DB2 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 Omotion
18. Online Database Relocation Server1 DB1 DB2 Server 2 DB3 instance 1 instance 1 instance 2 New client connections DB2 instance 2 Client connections Omotion 18 DB1 DB2 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 Omotion
19. Online Database Relocation Server1 DB1 DB2 Server 2 DB3 instance 1 instance 1 instance 2 New client connections DB2 instance 2 Client connections Omotion 19 DB1 DB2 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 Omotion
20. Online Database Relocation Server1 DB1 DB2 Server 2 DB3 instance 1 instance 1 instance 2 New client connections DB2 instance 2 Omotion 20 DB1 DB2 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 Omotion
21. Online Database Relocation Server1 DB1 Server 2 DB3 instance 1 instance 2 Client connections DB2 instance 2 21 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2
22. Online DB Patching Server1 DB1 Server 2 DB3 instance 1 instance 2 Client connections DB2 instance 2 22 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2
23. Online DB Patching Server1 DB1 Server 2 DB3 instance 1 instance 2 Client connections DB2 instance 2 Apply patch 23 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2
24. Online DB Patching Server1 DB1 Server 2 DB3 instance 1 instance 2 Client connections DB2 instance 2 DB2 instance 1 Omotion 24 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 DB2 DB_HOME 2 Omotion
25. Online DB Patching Server1 DB1 Server 2 DB3 instance 1 instance 2 Client connections DB2 instance 2 DB2 instance 1 Omotion New client connections 25 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 DB2 DB_HOME 2 Omotion
26. Online DB Patching Server1 DB1 Server 2 DB3 instance 1 instance 2 Client connections DB2 instance 2 DB2 instance 1 Omotion New client connections 26 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 DB2 DB_HOME 2 Omotion
27. Online DB Patching Server1 DB1 Server 2 DB3 instance 1 instance 2 DB2 instance 2 DB2 instance 1 Omotion New client connections 27 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 DB2 DB_HOME 2 Omotion
28. Online DB Patching Server1 DB1 Server 2 DB3 instance 1 instance 2 DB2 instance 1 Client connections Apply patch 28 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB_HOME 2 DB2 DB_HOME 2
29. Database Cold Failover Server1 DB2 Server 2 DB3 instance 1 instance 2 Client connections 29 DB2 DB3 Shared storage ASM DB_HOME 2 DB_HOME 3
30. Database Cold Failover Server1 DB2 Server 2 DB3 instance 1 instance 2 Client connections 30 DB2 DB3 Shared storage ASM DB_HOME 2 DB_HOME 3
31. Database Cold Failover Server1 DB2 Server 2 DB3 instance 1 instance 2 Client connections DB2 instance 1 31 DB2 DB3 Shared storage ASM DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2
32. Database Cold Failover Server1 DB2 Server 2 DB3 instance 1 instance 2 DB2 instance 1 Client connections 32 DB2 DB3 Shared storage ASM DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2
33. Online upgrade to RAC Server1 DB1 Server 2 DB3 instance 1 instance 2 DB2 instance 1 Client connections Use srvctl to upgrade to RAC 33 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2
34. Online upgrade to RAC Server1 DB1 Server 2 DB3 instance 1 instance 2 DB2 instance 2 DB2 instance 1 RAC Client connections 34 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 DB2 DB_HOME 2 RAC
35. Online upgrade to RAC Server1 DB1 Server 2 DB3 instance 1 instance 2 DB2 instance 2 DB2 instance 1 RAC Client connections New client connections 35 DB1 DB3 Shared storage ASM DB_HOME 1 DB_HOME 2 DB_HOME 3 DB2 DB_HOME 2 DB2 DB_HOME 2 RAC
36. Agenda • Overview • Deployment • High Availability • Consolidation 36 • Demo
37. Better consolidation • GI and ASM are running all the time on all nodes • Storage capacity is shared. • Disk groups are mounted all the time on all nodes • No volume migration during relocation or failover. • Instance caging 37 • Instance caging • Better workload and resource utilization. • Dynamic parameter (CPU_COUNT). • Two approaches - over-provisioning and partitioning. • RON can be admin or policy managed database
38. Instance caging - partitioning Server1 DB1 DB2 Server 2 DB3 38 DB1 DB2 DB3 Shared storage DB1 DB2 8 CPUs 4 CPUs
39. Instance caging - over-provisioning Server1 DB1 DB2 Server 2 DB3 39 DB1 DB2 DB3 Shared storage DB1 DB2 8 CPUs 8 CPUs
40. Oracle RAC One Node 40
41. Conclusion • Oracle RAC One Node pros: • Single vendor solution. • Faster Failover of database. • Easy and online scale-out to multi-node RAC. • Tolerate planned and unplanned outages. 41 • Tolerate planned and unplanned outages. • Lower license cost than full RAC. • Oracle RAC One Node cons: • Several MOS notes and no docs! • Not available to SE. • Almost ½ from RAC price.
42. Q&A Thank you! 42 Thank you! Email: s.gyurov@cnsys.bg Blog: http://sve.to Twitter: sgyurov