Analysis of crs-4000 errors in oracle11.2.0.4 RAC construction

On a server with a system environment of rhel6.5, set up a two-node RAC with a database version of oracle11.2.0.4 and encountered the following error when installing the grid:

(Note: Vote, data, and flash-back disks 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 would destroy any previous cluster

Configuration.

Failed to create voting files on disk group VOTE.

Change to configuration failed, but is 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 you cannot create a voting file on the disk group vote. Failed to change configuration, but rolled back successfully.

Voting file added failed, failed to add voting disk in/g01/11ggrid/app/11.2.0/grid/crs/install.

It is very strange to encounter this mistake or the first one. Because the previous use of the asmlib, there is no problem, but the installation of the problem, there is no way to continue.

Check asm for alert.log log discovery:

Error:could not create voting files. It spans across 161 AUs (Max supported is 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 being created in DiskGroup crsvote due to small Allocation Unit size

Continue to check the size of the following block problem, found some information:

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

# more *block_size

::::::::::::::

Logical_block_size

::::::::::::::

512

::::::::::::::

Physical_block_size

::::::::::::::

4096

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

So how do we solve this problem? Query Oracle's official website for solutions that are:

1. Oracle bug 11780656 is already fixed on 11.2.0.3 with compatible.asm = 11.2.0.3 but OUI does not allow to specify "comp Atible.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 b Lock size is 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 Oracleasm-support-2.1.8-1 package, or you can also select the ASM disk, use the

/dev/oracleasm/disks/* the path to resolve this issue.

You can also enter the/etc/sysconfig directory, modify the Oracleasm file under it, and change the Oracleasm_use_logical_block_size=false to True

Note: Oracle provides configuration parameters to enable Asmlib to continue using the correct logical block size feature to avoid this problem.

The problem is resolved with the above processing, and the grid is finally installed successfully.

This article is from the "Hollows Jie Sun" blog, be sure to keep this source http://xjsunjie.blog.51cto.com/999372/1585627

Analysis of crs-4000 errors in oracle11.2.0.4 RAC construction