Shulou(Shulou.com)06/01 Report--

This article introduces the relevant knowledge of "the causes and solutions of crs-4000 errors in oracle11.2.0.4 rac construction". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

On a server whose system environment is rhel6.5, build a two-node RAC with database version oracle11.2.0.4, and encounter the following error when installing GRID:

(note: vote, data, and flash drives are all on the storage device)

ASM created and started successfully.

Disk Group VOTE mounted successfully.

Clscfg:-install mode specified

Clscfg: EXISTING configuration version 5 detected.

Clscfg: version 5 is 11g Release 2.

Successfully accumulated necessary OCR keys.

Clscfg: Arguments check out successfully.

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

-force is destructive and will destroy any previous cluster

Configuration.

Failed to create voting files on disk group VOTE.

Change to configuration failed, but was successfully rolled back.

CRS-4000: Command Replace failed, or completed with errors.

Voting file add failed

Failed to add voting disks at / g01/11ggrid/app/11.2.0/grid/crs/install/crsconfig_lib.pm line 6930.

/ g01/11ggrid/app/11.2.0/grid/perl/bin/perl-I/g01/11ggrid/app/11.2.0/grid/perl/lib-I/g01/11ggrid/app/11.2.0/grid/crs/install / g01/11ggrid/app/11.2.0/grid/crs/install/rootcrs.pl execution failed

This error means that the voting file could not be created for the diskgroup VOTE. Failed to change the configuration, but rolled back successfully.

Failed to add voting file and failed to add voting disk in / g01/11ggrid/app/11.2.0/grid/crs/install.

This is the first time I have encountered this mistake, and it is very strange. Because there was no problem with using ASMLIB hanging disk before, but there was this problem with the installation, and it was impossible to continue.

Check the alert.log log of ASM and find that:

ERROR: Could not create voting files. It spans across 161AUs (max supported is 64 AUs)

ERROR: Voting file allocation failed for group VOTE

Errors in file / g01/11ggrid/app/11.2.0/grid/diag/asm/+asm/+ASM1/trace/+ASM1_ora_7321.trc:

ORA-15303: Voting files could not be created in diskgroup VOTE due to small Allocation Unit size

Check the DM corresponding to the arbitration disk of the corresponding GRID

# multipath-ll

Sc_vote (360a980003830302d712b46586276736b) dm-11 NETAPP,LUN

Size=5.0G features='4 queue_if_no_path pg_init_retries 50 retain_attached_hw_handle' hwhandler='0' wp=rw

`- +-policy='round-robin 0' prio=2 status=active

`- 17 virtual 0 sdax 015 0 active ready running 67:16

Continue to check the size of the DM-11 block and find some information:

# cd / sys/block/dm-11/queue

# more * block_size

:

Logical_block_size

:

five hundred and twelve

:

Physical_block_size

:

4096

The reason is that it shows different logical and physical block sizes. In most cases, the physical and logical blocks are the same size as "512".

So how to solve this problem? Check the official website of ORACLE and the solution is:

1. Oracle bug 11780656 is already fixed in 11.2.0.3 with compatible.asm = 11.2.0.3 but OUI does not allow to specify "compatible.asm" attribute to create OCRVOTE diskgroup.

-Bug 11780656-ASM MANAGED VOTING FILES CANNOT BE MORE THAN 64X AU SIZE

2. Oracle bug 13999609 indicates that ASMLib driver only works with the expectation that logical block size and physical block size are 512/512 bytes.

-Bug 13999609-PHYSICAL BLOCK SIZE REPORTED CAN CAUSE ISSUES WITH 10G DATABASES

SOLUTION

1] Possible workaround is to use'/ dev/oracleasm/disks/*' path instead of "ORCL:*" when creating OCRVOTE diskgroup in OUI.

OR

2] Install the new "oracleasm-support-2.1.8-1" ASMLIB RPM package (which contains the permanent fix) as described in note 1500460.1

According to the above tips, we can install the package of oracleasm-support-2.1.8-1, or we can use the

The path to / dev/oracleasm/disks/* to resolve this problem. According to the above tips to solve the problem, it is found that GRID still can not be installed successfully.

Repeated several times, did not find a solution. Since the backend uses NETAPP storage, go to NETAPP's official website to find the CASE case of this problem. It is found that it gives the following solution:

For details and caveats regarding this workaround, see the Oracle Alert.

Additionally, Oracle has provided a patch and configuration parameter to enable ASMlib to continue to function using the correct logical block size.

# ORACLEASM_USE_LOGICAL_BLOCK_SIZE: 'true' means use the logical block size

# reported by the underlying disk instead of the physical. The default

# is' false'

(oracle settings)

NetApp has also provided a workaround in versions 8.0.5, 8.1.3 and 8.2 of Data ONTAP 7-Mode. The workaround allows specified LUNs to continue to not report the logical blocks per physical block value. This work around should only be applied to LUNs used by Oracle ASMlib with the symptoms described in this article.

From the Data ONTAP 7-Mode CLI, enter the following commands:

Lun set report-physical-size disable (netapp storage settings)

According to this prompt, then go to the / etc/sysconfig directory, modify the oracleasm file under it, and change the

[oracle@rac1 ~] $cat / etc/sysconfig/oracleasm

#

# This is a configuration file for automatic loading of the Oracle

# Automatic Storage Management library kernel driver. It is generated

# By running / etc/init.d/oracleasm configure. Please use that method

# to modify this file

#

# ORACLEASM_ENABLED: 'true' means to load the driver on boot.

ORACLEASM_ENABLED=true

# ORACLEASM_UID: Default user owning the / dev/oracleasm mount point.

ORACLEASM_UID=grid

# ORACLEASM_GID: Default group owning the / dev/oracleasm mount point.

ORACLEASM_GID=asmadmin

# ORACLEASM_SCANBOOT: 'true' means scan for ASM disks on boot.

ORACLEASM_SCANBOOT=true

# ORACLEASM_SCANORDER: Matching patterns to order disk scanning

ORACLEASM_SCANORDER= ""

# ORACLEASM_SCANEXCLUDE: Matching patterns to exclude disks from scan

ORACLEASM_SCANEXCLUDE= ""

# ORACLEASM_USE_LOGICAL_BLOCK_SIZE: 'true' means use the logical block size

# reported by the underlying disk instead of the physical. The default

# is' false'

ORACLEASM_USE_LOGICAL_BLOCK_SIZE=false

Change ORACLEASM_USE_LOGICAL_BLOCK_SIZE=false to true

And modify the storage setting parameters on NETAPP accordingly

Note: Oracle provides configuration parameters to enable ASMLib to continue to use the correct logical block size to avoid this problem. )

Through the above treatment, the problem was resolved and GRID was finally installed successfully.

This is the end of the content of "causes and Solutions of crs-4000 errors in oracle11.2.0.4 rac Building". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.