740 likes | 919 Views
RAC on Windows 2003. Julian Dyke Independent Consultant. Web Version. juliandyke.com. Introduction. This presentation describes Windows specific RAC configuration issues including: Installation Pre installation steps Installing Oracle Clusterware Installing Oracle Database Software
E N D
RAC on Windows 2003 Julian Dyke Independent Consultant Web Version juliandyke.com
Introduction • This presentation describes Windows specific RAC configuration issues including: • Installation • Pre installation steps • Installing Oracle Clusterware • Installing Oracle Database Software • Patches • Post installation steps • Administration • Services • Networking
Warning • This presentation is intended to supplement information in the Oracle documentation • It is NOT intended to replace the Oracle documentation • Most of the information contained in this presentation was correct for Oracle 10.2 • Some information applies to earlier releases • Where appropriate this is highlighted in the slides
Overview • Oracle RAC is available on Windows in • Standard Edition • Enterprise Edition • Standard Edition must use Automatic Storage Management (ASM) • Enterprise Edition can use • Automatic Storage Management (ASM) • Oracle Cluster File System (OCFS)
Shared Oracle Home • Oracle Clusterware (CRS) MUST be installed in a local directory on each node • Oracle Database Software can be installed in a shared Oracle home on the cluster file system
Pre-Installation Steps • Pre-Installation tasks include: • Check public interface is first in bind order • Disable Windows Media Sensing for TCP/IP • Disable Write Caching on Shared Storage • Enable Auto-mounting • Local drives must be accessible from all nodes • Environment variables • System clocks must be synchronized
Public Interface Bind Order • The public interface must be the first in the bind order • To check this • Start Windows Explorer • Right click on My Network Places and choose Properties • In the Advanced menu click Advanced Settings... • In the Adapters and Bindings tab • If the public interface is not the first name listed • Click the arrow to move it to the top of the list • Click OK to save the setting
Windows Media Sensing for TCP/IP • Windows Media Sensing for TCP/IP must be disabled • To check this • Run REGEDT32.EXE • Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters • Add the following registry entry: • Right click on right hand pane and select • New -> DWORD value Value Name: DisableDHCPMediaSenseValue: 1 • NOTE- It is recommended that you backup the registry before making changes usingREDEDT32.EXE / REGEDIT.EXE
Write Caching • Write Caching must be disabled on shared storage • To disable write caching at operating system level: • Start->Settings->Control Panel->Administrative Tools-> Computer Management->Device Manager->Disk Drives • Expand the disk drives list • Double-click the first drive listed • On the Disk Properties tab uncheck the write cache enabled option • Repeat for all remaining disk drives • Not necessary if using HP Array Manager as write caching is automatically disabled at operating system level
Disk Manager • To start the Disk Management tool: • Start->Administrative Tools->Computer Management->Storage->Disk Management • Alternatively the Disk Management tool can be started from the command line using: C:> DISKMGMT.MSC
Auto-Mounting • Auto-mounting must be enabled when using • RAC with raw partitions • RAC with cluster file system • Oracle Clusterware • Logical drives for ASM • Auto-mounting must be enabled on each node in the cluster • To check if auto-mounting is enabled use: C:> DISKPARTDISKPART> AUTOMOUNT Automatic mounting of new volumes disabled
Auto-Mounting • To enable auto-mounting use: C:> DISKPARTDISKPART> AUTOMOUNT ENABLE Automatic mounting of new volumes enabledDISKPART> EXIT • Repeat on each node in the cluster • Restart all nodes after configuring this setting
Local Drive Accessibility • Local drives must be accessible from all nodes • To check local drive accessibility: • For each node • For each local drive to be used by the Oracle installation • Use NET USE command to confirm accessibility • For example if Oracle will be installed on E$ in a two-node cluster containing nodes RAC1 and RAC2 • On RAC1: NET USE \\RAC2\E$ • On RAC2: NET USE \\RAC1\E$
Environment Variables • On each node the following environment variables must be set • TEMP • TMP • By default these are set to • %USERPROFILE%\Local Settings\Temp • Oracle recommends these are redefined as follows • TEMP=C:\TEMP • TMP=C:\TMP • These settings should be the same on each node
Time Synchronization • It is recommended that the system clocks are synchronized between all nodes in the cluster • appears to be less important in Oracle 10g Release 2 than in previous RAC versions • To synchronize the system clocks enable the Windows Time Service on one node • The current time server for a node can be discovered using: NET TIME /QUERYSNTPThe current SNTP server is: node2 • The current time server for a node can be set using: NET TIME /SETSNTP:<hostname> • For example: NET TIME /SETSNTP:SGHRAC1
Time Synchronization • The current time on a node can be discovered using NET TIME \\NODE1 Current time at \\NODE1 is 20/02/2006 10:50 • To initially synchronize the time use NET TIME \\NODE1 /SETCurrent time at \\NODE1 is 20/02/2006 10:56 The current local clock is 20/03/2006 10:54Do you want to set the local computer's time to match the time at \\node1? (Y/N) [Y]: yThe command completed successfully.
Oracle Clusterware Installation • To install Oracle Clusterware • Login as Local Administrator only • The documentation states that Clusterware can be installed using Domain Administrator • Installation currently fails when attempting to start Clusterware services
Oracle Clusterware Installation • In Oracle 10.1 Oracle Clusterware was called Cluster Ready Services (CRS) • In Oracle 10.1 to set up CRS run CRS/SETUP.EXE • DO NOT run CRS/INSTALL/SETUP.exe • This will cause the installation to fail. • See Metalink Note 277688.1 - CRS Install: Failed to locate service OracleCSSService on second node • Also make sure that the install path does not include any spaces • In Oracle 10.2 there is only one SETUP.EXE program
Oracle Clusterware Installation • During installation the OracleClusterPreInstService is installed on each node to provide a list of available drives • This service uses ORACLECLUSTERPREINSTSERVICE.EXE
Oracle Clusterware Installation • To manually delete a failed clusterware installation: • Stop and delete all Oracle services. For example: SC STOP OracleCRServiceSC DELETE OracleCRService • Delete contents of Oracle Clusterware home directory • If required delete Oracle inventory directory • C:\Program Files\Oracle • Use REGEDIT to remove Oracle keys from registry • HKEY_LOCAL_MACHINE\Software\Oracle • Use Oracle Object Manager to delete links to OCR and Voting disk
Oracle Object Manager • If using raw devices • Oracle Object Manager is used to create links for • OCR • Voting Disk • Pathname is • %ORACLE_HOME%\bin\GUIObjectOBJManager • Link names are: • ocrcfg • votedsk1 • Executed automatically by the OUI during installation • Must be executed manually during manual deinstallation
Oracle Object Manager • For example
Database Installation • The script %ORACLE_HOME%\bin\SelectHome.bat must be executed on all remote nodes to activate the following products: • Oracle Data Provider for .NET • Oracle Provide for OLE DB • Oracle Objects for OLE • Oracle Counters for Windows Performance Monitor • Oracle Administration Assistant
Automatic Storage Management • ASM disks must be stamped before they can be used by ASM • Can be stamped • Using ASMTOOL command line utility • Using ASMTOOLG GUI utility • During ASM instance creation process in DBCA
Cluster File System • If selected in the Oracle Universal Installer (OUI) session then the Oracle Cluster File System is installed automatically • It is not necessary to download OCFS separately (as would be the case in Linux for example)
Cluster File System • To create partitions use OCFSFORMAT • Recommended block sizes are: • For example: OCFSFORMAT /l R:/C 1024 /V REDO
Patches • In addition to normal patch sets additional cumulative patches are issued for Oracle on Windows platforms • For example • 10.1.0.3 Patch 5 • 10.2.0.1 Patch 3 • Install the latest cumulative patch for the platform • For example in Oracle 10.2 available patches include • 10.2.0.1.0 Patch 2 (10.2.0.1.2P) Patch 4751342 • 10.2.0.1.0 Patch 3 (10.2.0.1.3P) Patch 4751539 • 10.2.0.1.0 Patch 4 (10.2.0.1.4P) Patch 4923768 • At the time of writing Patch 4 was recommended
Patches • Current Windows patch sets are documented on Metalink • For Oracle 10.1 • See Metalink Note 276548.1 - 10.1.0.x Oracle Database and Networking Patches for Microsoft Platforms • For Oracle 10.2 • See Metalink Note 342443.1 10.2.0.x Oracle Database and Networking Patches for Microsoft Platforms • Both reference • Note 161549.1 - Oracle Database Server and Networking Patches for Microsoft Platforms
Patch Set Installation • Installing Oracle 10.1.0.3 Patch 5 • The patch set should be installed in both the Clusterware home and the Oracle database home Run Setup.exe in the Oracle database home • After installing the CRS Patch on each node stop all CRS services (Service Management) • OracleCRService • OracleEVMService • OracleCSService • OracleClusterVolumeService • Run C:\Oracle\product\10.1\crs\install\patch10103.bat • After installing Oracle database software patch on one node, run $ORACLE_HOME\bin\SelectHome.bat on remaining nodes
Patch Set Installation • Installing Oracle 10.2.0.1 Patch 3 • The patch set should only be installed in the Oracle database home and does not affect CRS • Patch is installed using OPATCH • OPATCH should be upgraded to 10.2.0.1.1 or above • Patch# : 4898608 • Stop all services using %ORACLE_HOME% • Install 10.2.0.1.3 using OPATCH APPLY
Patch Set Installation • Installing Oracle 10.2.0.1 Patch 4 • The patch set should be installed in both the Clusterware and RDBMS home directories • Patch 4: 4923768 • Patch is installed using OPATCH • OPATCH should be upgraded to 10.2.0.1.1 or above in both Clusterware and RDBMS home directories • Patch# : 4898608 • Stop all services using %ORACLE_HOME% • Install 10.2.0.1 Patch 4 using OPATCH APPLY
Post Installation • Post installation tasks include: • Make files node-specific (Shared Oracle home only) • Create ORA_DBA group on remaining nodes • Set Log on as a Batch Job privilege for Enterprise Manager users
Make Files Node-Specific • If using shared Oracle Home on OCFS file system • After database creation using DBCA the HC files must be made node-specific. • Applies to Oracle 10.1 (at least) • On each host these files have the pathname: %ORACLE_HOME%\DATABASE\HC_<instance_name>.DAT • For example on instance RAC1 %ORACLE_HOME%\DATABASE\HC_RAC1.DAT
Make Files Node-Specific • For example on node node1: srvctl stop instance -d RAC -i RAC1 ocfsutil /c NodeSpecificFile /o create /m h: /p oracle\product\10.1.0\db\database\hc_rac1.dat srvctl start instance -d RAC -i RAC1 • Repeat for remaining instances
Log on as a batch job • Users must have the Log on as a batch job privilege for Enterprise Manager to work correctly • Start->Administrative Tools->Local Security Policy-> • Security Settings->Local Policies-> • User Rights Assignment->Log on as a batch job • Assign privilege for each administrative users • Repeat on each node • There is a description of this problem in Metalink • Note 279765.1 "Error Message 'RemoteOperationException: ERROR: Wrong password for users' when trying to startup or shutdown the database from the Enterprise Manager console" • There is a description of the resolution in Metalink • Note 109188.1 How to Set "Logon as a Batch Job" Privileges on Windows 2000 Systems
ORA_DBA Group • Administrators must be members of this group on each node in order to use / AS SYSDBA • By default ORA_DBA group is only created on installation node • Not created on remaining nodes • Must be created manually • See Metalink Notes • 177354.1 RAC: Connect AS SYSDBA Fails with ORA-01031 • 77665.1 - Guide to setup/enable OS authentication to Connect using OS user account
ORA_DBA Group • To create new ORA_DBA group and add users • Start->Administrative Tools->Computer Management-> • System Tools->Local Users and Groups->Groups • Right click and select New • Name is ORA_DBA • Description is Oracle DBA Group • Add user e.g. XYZDOM\abc.admin
Environment Variables • Environment variables are stored in the registry • Can be set using: • Start -> Control Panel -> System -> • Advanced-> Environment Variables
Registry Keys • Oracle registry entries are stored in • HKEY_LOCAL_MACHINE\Software\Oracle • The inventory location is defined in • HKEY_LOCAL_MACHINE\Software\Oracle\inst_loc • The default inventory location is: • C:\Program Files\Oracle\Inventory • The Oracle Cluster Repository location is stored in • HKEY_LOCAL_MACHINE\Software\Oracle\OCR\ocrconfig_loc
Registry • By default CRS-related keys are stored in • HKEY_LOCAL_MACHINE\Software\Oracle\KEY_OraCr10g_home • For example • ORA_CRS_HOME • ORACLE_HOME • By default database keys are stored in • HKEY_LOCAL_MACHINE\Software\Oracle\KEY_OraDb10g_home • For example • ORACLE_BASE • ORACLE_HOME • ORACLE_SID