在X3850上给客户装的是一套10g r2的RAC,在安装CRS的过程中出现了如下错误:

wKioL1LiWe_Q8S95AAOozZyiqPg213.jpg

详细信息如下:

信息: 开始执行 Configuration Assistant

信息: Command = C:\Windows\system32\cmd /c call C:\oracle\product\10.2.0\crs/install/crssetup.config.bat


Successfully accumulated necessary OCR keys.

Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.

node <nodenumber>: <nodename> <private interconnect name> <hostname>

node 1: win2008n1 win2008n1_priv win2008n1

node 2: win2008n2 win2008n2_priv win2008n2

Creating OCR keys for user ‘administrator’, privgrp ”..

Operation successful.

Now formatting voting device: \\.\votedsk1

Format of 1 voting devices complete.


Step 1:  checking status of CRS cluster

Step 2:  creating directories (C:\oracle\product\10.2.0\crs)

Step 3:  configuring OCR repository

Step 4:  configuring safe mode for CRS stack

Step 5:  Starting up CRS stack on all nodes

win2008n2             failed to startup service OracleCSService, err(1075)

win2008n1             service OracleCSService in improper PENDING state, err(1075)


Command = C:\Windows\system32\cmd /c call C:\oracle\product\10.2.0\crs/install/crssetup.config.bat has failed


信息: Configuration Assistant “Oracle Clusterware Configuration Assistant” 失败

—————————————————————————–

*** Starting OUICA ***

Oracle Home set to C:\oracle\product\10.2.0\crs

Configuration directory is set to C:\oracle\product\10.2.0\crs\cfgtoollogs. All xml files under the directory will be processed

信息: “C:\oracle\product\10.2.0\crs\cfgtoollogs\configToolFailedCommands” 脚本包含所有失败的, 跳过的或取消的命令。可使用此文件在 OUI 外运行这些 Configuration Assistant。请注意, 执行此脚本前, 您可能需要用口令 (如果有) 来更新此脚本。

—————————————————————————–

信息: Created a new file C:\oracle\product\10.2.0\crs\cfgtoollogs\configToolFailedCommands

信息: Since the option is to overwrite the existing C:\oracle\product\10.2.0\crs\cfgtoollogs\configToolFailedCommands file, backing it up

信息: The backed up file name is C:\oracle\product\10.2.0\crs\cfgtoollogs\configToolFailedCommands.bak

严重: OUI-25031: 一些 Configuration Assistant 失败。强烈建议您此时重试这些 Configuration Assistant。如果任何 “推荐” 的 Assistant 没有成功运行, 都将意味着无法正确配置系统。

1. 检查 Configuration Assistant 屏幕上的“详细资料”面板, 查看导致出现失败的错误。

2. 修复导致这些失败的错误。

3. 选择发生失败的 Assistant, 然后单击 ‘重试’ 按钮进行重试。

信息: 所选用户: 是(Y)/确定


通过日志发现有crssetup.config.bat has failed的报错,通过metalink查到有一个文章是解决该问题的。

—————————————————————————————————————————————————————————

CRS on Windows: How To Reinitialize (Accidentally Deleted) OCR and Vote Disk (without a full reinstall of Oracle Clusterware) [ID 557178.1]

In this Document

Goal
Solution
1.  Stop all CRS managed resources
2.  Stop all CRS services
3.  Reformat ALL partitions for OCR and voting disk files
4.  Set TEMP and TMP variables
5.  Start the OracleObjectService on all nodes
6.   Locate the crssetup.config.bat script
7.  Execute racgons from $CRS_HOME\bin
8.  Run oifcfg to configure public and cluster_interconnect
9.  Run  Virtual IP Configuration Assistant (VIPCA)
10.  Run Cluster Verification Uitility (cluvfy)
11.  Create an export copy of the OCR file
12.  Check for Oracle Process Manager
13.  Reboot all nodes in the cluster, if possible.  
14.  Run netca to create listener
15.  Recreate all necessary CRS managed resources
16.  Start all CRS managed resources
17.  Run crs_stat -t
References


Applies to:

Oracle Server – Enterprise Edition – Version: 10.1.0.2 to 11.1.0.7 – Release: 10.1 to 11.1
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
Oracle Server Enterprise Edition – Version: 10.1.0.2 to 11.1.0.7

Goal

Step by step approach to reinitialize the OCR and Vote Disks without performing a full reinstallation of the Oracle Clusterware binaries for RAC on Windows platforms.  These steps may be necessary in a few different scenarios:

1.  To troubleshoot an installation where the Cluster Configuration Assistant (which calls crssetup.config.bat ) has errored out

OR

2.  For a cluster that was running fine, but the OCR and/or Vote disks have become damaged or unusable

Please note that some of the listed steps (such as stopping the clusterware services) may not be relevant to installation troubleshooting.

Solution

Note:  If you have an OracleCRSToken service configured in this environment, it is advised to remove that service before implementing these steps, then recreate that service once these steps have been completed.  Knowledge Document Note 338000.1 explains OracleCRSToken services including how and why to create them and how to delete them.

1.  Stop all CRS managed resources

Ensure all CRS resources are stopped using the ‘crs_stat -t’ utility to check the status and the “srvctl” utility to stop as required.

In particular before step 2 below make sure that you stop nodeapps.

srvctl stop nodeapps -n <nodename>

Note: Failure to stop the nodeapps with the above command will result in an error since just stopping the services (as per step 2) does not stop the ons.exe and that will prevent the crssetup.config.bat script from running.

2.  Stop all CRS services

Stop all services running from the CRS home and set them to MANUAL from the Windows Services panel:

Stop OracleCRService and set to “Manual”on ALL nodes
Stop OracleEVMService and set to “Manual”on ALL nodes
Stop OracleCSService and set to “Manual” on ALL nodes
Stop OracleClusterVolumeService and set to “Manual” on ALL nodes
Stop Oracle Object Service and set to “Manual” on ALL nodes

3.  Reformat ALL partitions for OCR and voting disk files

All partitions that you will reuse for OCR and voting disk information should be reformatted in preparation for their recreation.

Example where OCR and Voting disks are stored on RAW partitions:  

a.  invoke the guioracleobjmanager.exe utility from $CRS_HOME\bin and note the assigned symbolic link names for ALL of the configured OCR and Voting disk partitions, example:

b.

-  Go to a command prompt
-  navigate to $CRS_HOME\bin
-  run logpartformat /q <link name as shown to you in guioracleobjmanager tool>

E:\oracle\product\10.2.0\crs\BIN>logpartformat /q \\.\ocrcfg
E:\oracle\product\10.2.0\crs\BIN>logpartformat /q \\.\votedsk1

Example where OCR and Voting disks are stored on OCFS partition(s):

a.  to locate your ocr partition(s) look to the following key by invoking ‘regedit’

HKEY_LOCAL_MACHINE\Software\Oracle\ocr\ocrconfig_loc

b.  to locate your voting disk partition(s), use the following command:

$CRS_HOME\bin> crsctl query css votedisk

c.  create backups of the existing ocr and voting disk files AND create new ‘placeholder’ files for the replacement ocr and voting disk files

Example:

Rename O:\cdata\clustername\votedsk.ocr to O:\cdata\clustername\votedsk.ocr.old
Rename O:\cdata\clustername\ocrcfg.ocr to O:\cdata\clustername\ocrcfg.ocr.old
notepad O:\cdata\clustername\votedsk.ocr
notepad O:\cdata\clustername\ocrcfg.ocr

d.

- Go to a command prompt
- navigate to $CRS_HOME\bin
- run logpartformat /q <drive letter to OCFS partition>

E:\oracle\product\10.2.0\crs\BIN>logpartformat /q F:
E:\oracle\product\10.2.0\crs\BIN>logpartformat /q G:

4.  Set TEMP and TMP variables

Open a Windows command prompt and set TEMP and TMP to use c:\temp

set temp=c:\temp
set tmp=c:\temp

5.  Start the OracleObjectService on all nodes


Note:

As a guide for Steps 6-9 utilize the commands listed in:

$CRS_HOME\cfgtoollogs\configtoolallcommands
OR
$CRS_HOME\cfgtoollogs\configtoolallcommands.bak

Whichever is correctly populated for your environment.

6.   Locate the crssetup.config.bat script

From node1 (or whichever node was used to apply the latest patchset to this cluster), locate the crssetup.config.bat script, check that the contents of this .bat file are correct for your environment, and execute this file.

Example:  assuming your CRS_HOME is e:\oracle\product\10.2.0\crs

cd e:\oracle\product\10.2.0\crs\install

OR

if you have already applied a patchset:

Example:
e:\oracle\product\10.2.0\crs\install\prepatch10204\install

Again, execute whichever crssetup.config.bat script is correctly populated for your environment.


E:\oracle\product\10.2.0\crs\install\prepatch10204\install>crssetup.config.bat
Step 1:  checking status of CRS cluster
Step 2:  creating directories (E:\oracle\product\10.2.0\crs)
Step 3:  configuring OCR repository
Successfully accumulated necessary OCR keys.
Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.
node <nodenumber>: <nodename> <private interconnect name> <hostname>
node 1: racnode1 racnode1-p racnode1
node 2: racnode2 racnode2-p racnode2
Creating OCR keys for user ’administrator’, privgrp ”..
Operation successful.
Now formatting voting device: \\.\votedsk1
Format of 1 voting devices complete.
Step 4:  configuring safe mode for CRS stack
Step 5:  Starting up CRS stack on all nodes
Successfully completed configuration of 2 nodes


Optionally – perform a check to confirm the CRS version as per the OCR file as follows:

E:\oracle\product\10.2.0\crs\BIN>crsctl query crs softwareversion
Oracle Clusterware version on node [racnode1] is [10.2.0.4.0]

E:\oracle\product\10.2.0\crs\BIN>crsctl query crs activeversion
Oracle Clusterware active version on the cluster is [10.2.0.4.0]


It is important that this step be executed while logged on as the OS user account that you have selected to be the owner of the CRS installation.   In most cases, this will be the same account that did the original installation.

If you are attempting to change the OCR to run under a different account, you must ensure that you are logged on to the OS under that new account prior to running crssetup.config.bat.  This step will create the OCR and set permissions on certain resources for the account that runs the crssetup.config.bat command.   If that OS user account is deleted in the future, or if that account’s access permissions change, then the steps in this note will need to be re-run under a valid user account.  Therefore, using temporary accounts for the installation of CRS should be avoided where possible.


Upon completion of this step, Oracle Clusterware services should have started automatically.

7.  Execute racgons from $CRS_HOME\bin

This step configures / ensures that all nodes are configured with the same port for the ONS

racgons.exe add_config <node1>:<port#> <node2>:<port#>

Example:

E:\oracle\product\10.2.0\crs\BIN>racgons.exe add_config racnode1:6200 racnode2:6200

8.  Run oifcfg to configure public and cluster_interconnect

Example: as oracle user:

oifcfg setif -global <if_name>/<subnet>:public
oifcfg setif -global <if_name>/<subnet>:cluster_interconnect


Example:

E:\oracle\product\10.2.0\crs\BIN>oifcfg.exe setif -global “Public”/10.143.137.0:public “Private”/10.10.10.0:cluster_interconnect

9.  Run  Virtual IP Configuration Assistant (VIPCA)

VIPCA must be run to recreate the nodeapp resources:

a.  to use VIPCA in GUI mode simply type:  ‘vipca’ at the $CRS_HOME\bin prompt

OR

b.  to run VIPCA in silent mode, use the command as listed in the configtoolallcommands file

Example:

E:\oracle\product\10.2.0\crs\BIN>E:\oracle\product\10.2.0\crs/bin/vipca.bat -silent -nodelist “racnode1,racnode2″ -nodevips
“racnode1/racnode1-vip/255.255.255.0/Public,racnode2/racnode2-vip/255.255.255.0/Public”

Creating VIP application resource on (2) nodes…
Creating GSD application resource on (2) nodes…
Creating ONS application resource on (2) nodes…
Starting VIP application resource on (2) nodes…
Starting GSD application resource on (2) nodes…
Starting ONS application resource on (2) nodes…

Done.

Once this step is complete, the output of ‘crs_stat -t’ should show vip, ons, and gsd resources for all nodes.

E:\oracle\product\10.2.0\crs\BIN>crs_stat -t
Name             Type        Target State  Host
————————————————————
ora.racnode1.gsd application ONLINE ONLINE racnode1
ora.racnode1.ons application ONLINE ONLINE racnode1
ora.racnode1.vip application ONLINE ONLINE racnode1
ora.racnode2.gsd application ONLINE ONLINE racnode2
ora.racnode2.ons application ONLINE ONLINE racnode2
ora.racnode2.vip application ONLINE ONLINE racnode2

10.  Run Cluster Verification Uitility (cluvfy)

Run Cluster Verification Uitility (cluvfy) to confirm post crs installation

cluvfy.bat stage -post crsinst -n “<node1>,<node2>”

Example:

E:\oracle\product\10.2.0\crs\BIN>E:\oracle\product\10.2.0\crs/bin/cluvfy.bat stage -post crsinst -n “racnode1,racnode2″

Performing post-checks for cluster services setup

Checking node reachability…
Node reachability check passed from node “racnode1″.

Checking user equivalence…
User equivalence check passed for user “Administrator”.

Checking Cluster manager integrity…

Checking CSS daemon…
Daemon status check passed for “CSS daemon”.

Cluster manager integrity check passed.

Checking cluster integrity…

Cluster integrity check passed

Checking OCR integrity…

Checking the absence of a non-clustered configuration…
All nodes free of non-clustered, local-only configurations.

Uniqueness check for OCR device passed.

Checking the version of OCR…
OCR of correct Version “2″ exists.

Checking data integrity of OCR…
Data integrity check for OCR passed.

OCR integrity check passed.

Checking CRS integrity…

Checking daemon liveness…
Liveness check passed for “CRS daemon”.

Checking daemon liveness…
Liveness check passed for “CSS daemon”.

Checking daemon liveness…
Liveness check passed for “EVM daemon”.

Checking CRS health…
CRS health check passed.

CRS integrity check passed.

Checking node application existence…

Checking existence of VIP node application (required)
Check passed.

Checking existence of ONS node application (optional)
Check passed.

Checking existence of GSD node application (optional)
Check passed.

Post-check for cluster services setup was successful.

11.  Create an export copy of the OCR file

ocrconfig -export c:\tmp\ocrdump_base.out

12.  Check for Oracle Process Manager

Ensure the “Oracle Process Manager” service is set to “Automatic” on ALL nodes

Oracle Support highly recommends configuring Oracle Process Manager (OPMD) to run in all Windows RAC environments.  Reference Note 358156.1 for full details.

13.  Reboot all nodes in the cluster, if possible.

A reboot of all nodes will ensure that the clusterware services (including Oracle Process Manager service) are working as expected.

14.  Run netca to create listener

a. rename $ORACLE_HOME/network/admin/listener.ora

(ASM HOME and/or RDBMS ORACLE_HOME) to any other name on all nodes

AND

b. From the command prompt, invoke netca from the ASM and/or RDBMS home (on just one node)

E:\oracle\product\10.2.0\db_1\bin\netca


Note:
Be sure to select ‘Cluster Configuration’ and to create a listener with the default name LISTENER

It is necessary to recreate the listener using NETCA at this point, as that is the only way to furnish the reinitialized OCR with .lsnr resource information.


Once these steps are completed, ‘crs_stat -t’ should show a ‘.lsnr’ resource for all nodes

E:\oracle\product\10.2.0\crs\BIN>crs_stat -t
Name             Type        Target State  Host
————————————————————
ora….E1.lsnr   application ONLINE ONLINE racnode1
ora.racnode1.gsd application ONLINE ONLINE racnode1
ora.racnode1.ons application ONLINE ONLINE racnode1
ora.racnode1.vip application ONLINE ONLINE racnode1
ora….E2.lsnr   application ONLINE ONLINE racnode2
ora.racnode2.gsd application ONLINE ONLINE racnode2
ora.racnode2.ons application ONLINE ONLINE racnode2
ora.racnode2.vip application ONLINE ONLINE racnode2

15.  Recreate all necessary CRS managed resources

Run the ‘srvctl add’ command to add asm, database, instance and services resources back into the OCR

For full syntax usage, please execute:

srvctl add asm -h
srvctl add database -h
srvctl add instance -h
srvctl add service -h (if needed)


For example: as oracle user:

srvctl add asm -n <node_name> -i <asm_inst_name> -o <oracle_home>
srvctl add database -d <db_name> -o <oracle_home>
srvctl add instance -d <db_name> -i <inst_name> -n <node_name>
srvctl modify instance -d <db_name> -i <inst_name> -s <asm_name>

*** srvctl modify instance -d racdb -i racdb3 -s asm3 ***

<== repeat as needed to make the database instance resources dependent on their corresponding ASM instance resources in the OCR


Please note, assuming that you are using ASM the asm_inst_name can only be +ASM1, +ASM2 and so on.
Failure in providing the correct name could cause an OCR corruption.

16.  Start all CRS managed resources

Once all necessary resources have been registered, start them via srvctl commands

For example: as oracle user:

srvctl start asm -n <node_name>
srvctl start instance -d <db_name> -i <inst_name>

17.  Run crs_stat -t

Check ‘crs_stat -t’ output, it should show all resources with TARGET and STATUS of ONLINE for all resources on ALL nodes

References

NOTE:358156.1 - Automatic Startup of Cluster Services May Hang or Fail on Windows
NOTE:399482.1 - How to recreate OCR/Voting disk accidentally deleted

—————————————————————————————————————————————————————————

但是通过测试发现在对OCR和VOTING做格式化后手动启动CSS还是失败。

通过在搜索问题解决问题的过程中发现了无数类似的问题求助,但就是不见有解决方案。

在寻求答案的过程中看到这样一个网友的回复:

在虚拟环境下建rac的大都有这个经历,而真实环境下的一般没事,也难怪有人把矛头指向vmvare 。
问题的源头在哪里?共享磁盘,对,就是共享磁盘引起的,为什么?这是网上另外一个误导引起的,你用类似vmware-vdiskmanager.exe -c -s 200Mb -a ide -t 0 disk.vmdk(网上一篇文章《在两台Vmware机器中添加共享磁盘》)来做的共享磁盘吧,恭喜,中招了,这篇文章什么都好,就是用在RAC上坏事了,关键在-t 0这个参数上,当然你用-t 2也不行,为什么我也说不清楚,看看英文的介绍:
Disk types of VMWare:
0 : single growable virtual disk
1 : growable virtual disk split in 2GB files
2 : preallocated virtual disk
3 : preallocated virtual disk split in 2GB files
4 : preallocated ESX-type virtual disk
5 : compressed disk optimized for streaming
正确的:vmware-vdiskmanager.exe -c -s 6Gb -a lsilogic -t 4 disk.vmdk
你创建ide盘或scsi盘都行。
你必须要-t 4才可以,这就是err(997)出现的根源,可悲是的在用-t 0做的虚拟盘在挂接、建立逻辑分区、创建逻辑驱动器、安装clusterware前期若干配置阶段一点问题都没有,到了安装clusterware结束,进入配置向导检查时突然报err(997)错误,委实让人摸不着头脑。


我正是使用-t 2这样的参数去创建的共享磁盘,但是困惑的是在LINUX下这样创建是没有问题的,但由于现在手头上WINDOWS环境的问题没法重划共享盘对该可行性进行验证,所以也不能给出一个明确的答案,期待以后的工作中能补上这块空白!

2012年7月12日

通过利用openfiler搭建iscsi存储,CRS还是出错,报错如下:

已通过 Configuration Assistant “Oracle Clusterware Configuration Assistant” 生成输出:

Command = C:\Windows\system32\cmd /c call C:\oracle\product\10.2.0\crs/install/crssetup.config.bat

Successfully accumulated necessary OCR keys.

Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.

node <nodenumber>: <nodename> <private interconnect name> <hostname>

node 1: rac1 rac1-priv rac1

node 2: rac2 rac2-priv rac2

Creating OCR keys for user ‘administrator’, privgrp ”..

Operation successful.

Now formatting voting device: \\.\votedsk1

Format of 1 voting devices complete.

Step 1:  checking status of CRS cluster

Step 2:  creating directories (C:\oracle\product\10.2.0\crs)

Step 3:  configuring OCR repository

Step 4:  configuring safe mode for CRS stack

Step 5:  Starting up CRS stack on all nodes

rac1                  service OracleCSService in improper PENDING state, err(0)

rac2                  service OracleCSService in improper PENDING state, err(0)


Configuration Assistant “Oracle Clusterware Configuration Assistant” 失败

—————————————————————————–

“C:\oracle\product\10.2.0\crs\cfgtoollogs\configToolFailedCommands” 脚本包含所有失败的, 跳过的或取消的命令。可使用此文件在 OUI 外运行这些 Configuration Assistant。请注意, 执行此脚本前, 您可能需要用口令 (如果有) 来更新此脚本。—————————————————————————–已通过 Configuration Assistant “Oracle Clusterware Configuration Assistant” 生成输出:

Command = C:\Windows\system32\cmd /c call C:\oracle\product\10.2.0\crs/install/crssetup.config.bat

clscfg: EXISTING configuration version 3 detected.

clscfg: version 3 is 10G Release 2.

Successfully accumulated necessary OCR keys.

Using ports: CSS=49895 CRS=49896 EVMC=49898 and EVMR=49897.

node <nodenumber>: <nodename> <private interconnect name> <hostname>

node 1: rac1 rac1-priv rac1

node 2: rac2 rac2-priv rac2

clscfg: Arguments check out successfully.


NO KEYS WERE WRITTEN. Supply -force parameter to override.

-force is destructive and will destroy any previous cluster

configuration.

Step 1:  checking status of CRS cluster

Step 2:  creating directories (C:\oracle\product\10.2.0\crs)

Step 3:  configuring OCR repository

Oracle Cluster Registry already initialized

Step 4:  configuring safe mode for CRS stack

Step 5:  Starting up CRS stack on all nodes

rac1                  service OracleCSService in improper PENDING state, err(0)

rac2                  service OracleCSService in improper PENDING state, err(0)


Configuration Assistant “Oracle Clusterware Configuration Assistant” 失败

—————————————————————————–

“C:\oracle\product\10.2.0\crs\cfgtoollogs\configToolFailedCommands” 脚本包含所有失败的, 跳过的或取消的命令。可使用此文件在 OUI 外运行这些 Configuration Assistant。请注意, 执行此脚本前, 您可能需要用口令 (如果有) 来更新此脚本。—————————————————————————–


由于该问题只有在10g下有,经测试,11g R2能正常安装,这让我不得不怀疑是否是ORACLE 10g下的一个BUG,非常可疑哦!