8103941RAC and Oracle Clusterware Best Practices and Starter Kit.docx

1、8103941RAC and Oracle Clusterware Best Practices and Starter KitRAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent) ID 810394.1Modified07-FEB-2012TypeBULLETINStatusPUBLISHEDIn this DocumentPurposeScope and ApplicationRAC and Oracle Clusterware Best Practices and Starter

2、Kit (Platform Independent)RAC Platform Specific Starter Kits and Best PracticesRAC Platform Generic Load Testing and System Test Plan Outline RACcheck - RAC Configuration Audit ToolTop 11 Things to do NOW to Stabilize your RAC Cluster EnvironmentDesign ConsiderationsInstallation ConsiderationsPatchi

3、ng ConsiderationsUpgrade ConsiderationsDatabase Configuration Considerations for RACDiagnostics and TroubleshootingApplies to:Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.3 - Release: 10.2 to 11.2Oracle Server - Enterprise Edition - Version: 10.2.0.1to11.2.0.3Release: 10.2 to 11.

4、2Information in this document applies to any platform.PurposeThe goal of the Oracle Real Application Clusters (RAC) series of Best Practice and Starter Kit notes is to provide customers with quick knowledge transfer of generic and platform specific best practices for implementing, upgrading and main

5、taining an Oracle RAC system. This document is compiled and maintained based on Oracles experience with its global RAC customer base.This Starter Kit is not meant to replace or supplant the Oracle Documentation set, but rather, it is meant as a supplement to the same. It is imperative that the Oracl

6、e Documentation be read, understood, and referenced to provide answers to any questions that may not be clearly addressed by this Starter Kit.All recommendations should be carefully reviewed by your own operations group and should only be implemented if the potential gain as measured against the ass

7、ociated risk warrants implementation. Risk assessments can only be made with a detailed knowledge of the system, application, and business environment.As every customer environment is unique, the success of any Oracle Database implementation, including implementations of Oracle RAC, is predicated on

8、 a successful test environment. It is thus imperative that any recommendations from this Starter Kit are thoroughly tested and validated using a testing environment that is a replica of the target production environment before being implemented in the production environment to ensure that there is n

9、o negative impact associated with the recommendations that are made.Scope and ApplicationThis article applies to all new and existing RAC implementations as well as RAC upgrades.RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent)RAC Platform Specific Starter Kits and Bes

10、t PracticesWhile this note focuses on platform independent (generic) RAC Best Practices, the following notes contain detailed platform specific best practices including Step-By-Step installation cookbooks.Document 811306.1RAC and Oracle Clusterware Best Practices and Starter Kit (Linux)Document 8112

11、80.1RAC and Oracle Clusterware Best Practices and Starter Kit (Solaris)Document 811271.1RAC and Oracle Clusterware Best Practices and Starter Kit (Windows)Document 811293.1RAC and Oracle Clusterware Best Practices and Starter Kit (AIX)Document 811303.1RAC and Oracle Clusterware Best Practices and St

12、arter Kit (HP-UX)RAC Platform Generic Load Testing and System Test Plan OutlineAcritical task of any successful implementation, particularly mission critical Maximum Availability environments, is testing. For a RAC environment, testing should include both load generation and fault injection testing.

13、 Load testing will allow for measurement of how the system reacts under heavy load while fault injection testing will help ensure that the system reacts as designed when those inevitable hardware and/or software failures occur. The following documents will provide you with guidance in performing thi

14、s crucial testing.Clickherefor a White Paper on available RAC System Load Testing ToolsClickherefor a platform generic RAC System Test Plan Outline for 10gR2 and 11gR1Clickherefor a platform generic RAC System Test Plan Outline for 11gR2These documents are to be used to validate your system setup an

15、d configuration, and also as a means to practice responses and establish procedures in case of certain types of failures.RACcheck - RAC Configuration Audit ToolRACcheck is a RAC Configuration Audit tool designed to audit various important configuration settings within Real Application Clusters (RAC)

16、, Oracle Clusterware (CRS), Automatic Storage Management (ASM) and Grid Infrastructure environments. This utility is to be used to validate the Best Pracices and Success Factors defined in the series of Oracle Real Application Clusters (RAC) Best Practice and Starter Kit notes which are maintained b

17、y the RAC Assurance development and support teams. At present RACcheck supports Linux (x86 and x86_64), Solais SPARC and AIX (with the bash shell) platforms. Those customers running RAC on the RACcheck supported platorms are strongly encouraged to utilize this tool identify potential configuration i

18、ssues that could impact the stability of the cluster.Document 1268927.1RACcheck - RAC Configuration Audit ToolNote: Oracle is constantly generating and maintaining Best Practices and Success Factors from the global customer base. As a result the RACcheck utility is frequently updated with this infor

19、mation. That said, it is recommended that you ensure you are using the version of RACcheck prior to execution.Top 11 Things to do NOW to Stabilize your RAC Cluster EnvironmentAs a proactive measure to prevent cluster instability due to commonly know issues, the Oracle RAC Proactive Support team has

20、compiled a list of the top 11 issues that can impact the stability of a RAC cluster. Though all of these recommendations are contained within the series of of Best Practice and Starter Kit notes, we do strongly recommend the following note be reviewed as we do feel these are key success factors.Docu

21、ment 1344678.1Top 11 Things to do NOW to Stabilize your RAC Cluster EnvironmentDesign ConsiderationsThe following Design Considerations are to provide guidance and best practice information around the infrastructure (Platform Independent) to support an Oracle RAC implementation. This information not

22、 only pertains to new installations and upgrade but will also provide useful information for those supporting existing RAC implementations.General Design Considerations To simplify the stack and simplify vendor interactions, Oracle recommends avoiding 3rd party clusterware, unless absolutely necessa

23、ry. Automatic Storage Management (ASM) is recommended for database storage. Additional information regarding ASM can be found inDocument 265633.1. Check the support matrix to ensure supportability of product, version and platform combinations or for understanding any specific steps which need to be

24、completed which are extra in the case of some such combinations.Document 337737.1 Check with the Disk Vendor that the Number of Nodes, OS version, RAC version, CRS version, Network fabric, and Patches are certified, as some Storage/San vendors may require special certification for a certain number o

25、f nodes. Plan and document capacity requirements. Work with server vendor to produce detailed capacity plan and system configuration, but consider: Use normal capacity planning process to estimate number of CPUs required to run workload. Both SMP and RAC clusters have synchronization costs as the nu

26、mber of CPUs increase. SMPs normally scale well for small number of CPUs, RAC clusters normally scale better than SMPs for large number of CPUs. Typical synchronization cost: 5-20%. Eliminate any single points of failure in the architecture. Examples include (but are not limited to): Cluster interco

27、nnect redundancy (NIC bonding etc), multiple access paths to storage, using 2 or more HBAs or initiators and multipathing software, and Disk mirroring/RAID. Additional details are found in the subsequent sections. Use proven Maximum Availability strategies. RAC is one component in the overall Maximu

28、m Availability Architecture. Review Oracles Maximum Availability Architecture blueprint found at Having a system test plan to help plan for and practice unplanned outages is crucial. The following paper discusses Best Practices for Optimizing Availability During Unplanned Outages Using Oracle Cluste

29、rware and Oracle Real Application Clusters: In addition, this note has an attached sample System Test Plan Outline, to guide your system testing to help prepare for potential unplanned failures. It is strongly advised that a production RAC instance does not share a node with a DEV, TEST, QA or TRAIN

30、ING instance. These extra instances can often introduce unexpected performance changes into a production environment. Along the same lines, it is highly recommended that testing environments mirror production environments as closely as possible. Having a step-by-step plan for your RAC project implem

31、entation is invaluable. The following OTN article contains a sample project outline: Avoid SETTING ORA_CRS_HOME environment variable (on all platforms). Setting this variable can cause problems for various Oracle components, and it is never necessary for CRS programs because they all have wrapper scripts.Networking Considerations Underscores are not be used in a host or domain name according toRFC952- DoD