My Oracle Support Banner

ASM Disk Shows PROVISIONED On One RAC Node, UNKNOWN On Other Node, Cannot Add To Disk Group (Doc ID 1468642.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Server - Standard Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.

Symptoms

A new LUN was created and made visible to two nodes. Then as root user a partition was created with fdisk, then made visible to the kernel by partprobe/partx on both nodes. Then multipath was configured the same on both nodes. Once that was done, the following commands were run.

On Node 1:
$ sudo /etc/init.d/oracleasm createdisk ASMFS02 /dev/mapper/<device_name>
$ /etc/init.d/oracleasm listdisks

Then on Node 2:

$ sudo /etc/init.d/oracleasm scandisks
$ /etc/init.d/oracleasm listdisks

The listdisks on both nodes showed that the ASM disk ASMFS02 was created and visible.

Also, on both nodes, the command "/etc/init.d/oracleasm querydisk ASMFS02" gave the message:

'Disk "ASMFS02" is a valid ASM disk'

In spite of all that, in SQLPLU, querying the view GV$ASM_DISK shows that HEADER_STATUS=PROVISIONED on INST_ID=1, but HEADER_STATUS=UNKNOWN on INST_ID=2. And, when the following command was executed from instance +ASM1:

ALTER DISKGROUP ASMFS ADD DISK 'ORCL:ASMFS02' SIZE 81917 M REBALANCE POWER 8;

It failed with the following error messages:

ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15075: disk(s) are not visible cluster-wide

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.