Precautions for installing 10gRAC for Windows

Virtual Machine: VMware 9.0

OS: Window Server 2003 Enterprise (32 Bit)

Clusterware: 10.2.0.1-> 10.2.0.4

Database: 10.2.0.1-> 10.2.0.5

I used to get used to building rac in the Linu environment. I tried to play it on Windows for the first time yesterday. Some people may feel very disdainful and feel that Windows platform has no practical value, who said no? Even so, it cannot be said that the windows production environment will not be used. In this case, as a DBA, we will become a versatile platform, No matter what platform we are dealing, you have to be aware of everything, so that you will not be flustered. Below I will share some problems encountered during the deployment process. I will not talk about the specific operation process, but will only list several issues that need attention:

1. Make sure that the administrator user is used for installation and the password is not allowed.

2. We recommend that you use Remote Desktop Connection, such as VNC.

3. Modify two environment variables.

TEMP = C: \ WINDOWS \ TEMP, TMP = C: \ WINDOWS \ TEMP

4. network configuration (important)

Primary network adapter (bridging), with a VIP address, with a gateway

Secondary NIC (Host Only) with PRIV address, no gateway required

PING and net use \ NODE1 \ C $ to test whether the network is connected. This is the basic guarantee for correctly installing RAC. In addition, because Windows is sensitive to network transmission, you must modify the Registry. In the HKLM \ SYSTEM \ CurrentControlSet \ Services \ Tcpip \ Parameters project, add a DoubleWord field, the value is 1. After the change, it will be used as a network connectivity test and a remote registry should be connected to see if the registry of Node 2 can be connected normally.

Finally, you must adjust the network adapter sequence to PUBLIC first and PRIVATE to the back. Otherwise, when installing OUI, execute to add nodes.-PRIVv is automatically added to the back of the corresponding node name, for example:

Originally in the % sysroot % \ DRIVERS \ ETC \ HOSTS file clearly written NODE-VIP NODE-PRIV will become NOD-PRIV NODE-VIP-PRIV NODE-PRIV-PRIV like this, even if you modify the file to be configured in the HOST, it is useless and cannot be changed to NEXT, so be sure to pay attention to it !!!

5. Run services. msc and close one of the services. The name is Distributed Tracation Coordinator.

6. Make sure that the time of the two nodes is the same. You can double-click the time in the taskbar, select "Internet time", and select the corresponding server for synchronization.

7. Configure shared disks (also important)

Not to mention, I can search for commands and methods on the internet, mainly to talk about my experience. If the configuration is poor, the two nodes cannot communicate normally, because the two important parts of the RAC environment, OCR and VOTINGDISK, must be placed on the shared disk. It is important to note that the disk size should be planned in advance, because once OCR and VOTINGDISK are determined, the disk will not be moved any more. In my experience, 10 Gb OCR will only be more than 100 MB, it is enough to give a M Disk, VOTINGDISK does not need to be given a lot, and m is enough. If it is 11g, give it more, 1g. In Windows, the disk viewing tool is DISKPART, which is quite useful. You can enter DISKPART directly without parameters and press enter to see help. We generally use bare disks for 10 Gb, do not format the file system or give the drive letter. just create a partition and a logical drive.

In addition, if you are using VMware, pay attention to the "node name ". add disk to the vmx file. locking = "FALSE", otherwise, when you start two virtual machines at the same time, a xx disk is locked and cannot be enabled properly.

8. After completing the above steps, you can clone a host as node 2, and then modify the host name, Nic IP address, and other information. The restart takes effect.

9. Before installing RAC, run the command to check whether there are any omissions in each configuration step. The command is as follows: runcluvfy. bat stage-pre crsinst-n node1, node2 [-verbose]

After the installation is complete, run this command to verify again: runcluvfy. bat stage-post hwos-n node1, node2 [verbose]

10. This problem has plagued me a day. I installed it four times before and after, that is, vipca in 10.2.0.1. Otherwise when you successfully installed RAC, happy to execute VIPCA that success, will be very sad, will report PRKH-1010 and PRKR-1062 error, no other solution, it is useless to manually start the SERVICE. The crsctl start crs is stuck, and there is no obvious ERROR message in the log. After the opmd is installed, all problems are solved, and the whole person is much easier, and the execution of VIPCA is normal.

Well, I 'd like to write so much about it first. I hope it will be helpful for you to play RAC on Windows later.

Finally, we will reference an official description of this bug solution:

Oracle BUG: 4537790 was logged for this issue, although the problem is more of an OS initialization problem than a CSS problem. the fix for BUG: 4537790 is to provide an executable called 'opmd.exe '. the opmd.exe allows the creation of a new service called the 'oracle Process Manager '. the Oracle Process Manager will control the startup of the clustering services to prevent the OracleCSService (or OracleCMService9i) from starting up before the rest of the OS services have started.

To resolve this problem, you must obtain the patchset for your release which contains the 'opmd.exe '. The following patches contain this utility:

For Oracle10g:
====================================

10.1.0.4 Patch 10 and higher will contain 'opmd.exe'
10.1.0.5 Patch 1 and higher will contain 'opmd.exe'
10.2.0.1 Patch 5 and higher will contain 'opmd.exe'
10.2.0.2 Patch 3 and higher will contain 'opmd.exe'

The command for installing the opmd Process Manager is as follows:

To uninstall opmd, add-uninstall.

Once opmd is installed, several services, such as OracleCRService, are immediately started (services. msc was previously executed and cannot be started manually)

Reference: Automatic Startup of Cluster Services May Hang or Fail on Windows (Document ID 358156.1)