How to resolve error ORA-15032,ORA-15031,ORA-15025,ORA-15056 when adding a disk to asm.

SQL> ALTER DISKGROUP ASM_FRA ADD DISK '/dev/dm-51';
ALTER DISKGROUP ASM_FRA ADD DISK '/dev/dm-51'
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15031: disk specification '/dev/dm-51' matches no disks
ORA-15025: could not open disk "/dev/dm-51"
ORA-15056: additional error message
Linux-x86_64 Error: 13: Permission denied
Additional information: 42
Additional information: 1927546192

I wanted to add  the following disk: (/dev/dm-51,/dev/dm-52,/dev/dm-53)
First check the permissions on this files after the Unix admin has provision it.
$ls -lrt /dev/dm*
brw-rw---- 1 root disk 253, 19 Jan 31 13:46 /dev/dm-19
brw-rw---- 1 root disk 253, 53 Mar 2 21:04 /dev/dm-53
brw-rw---- 1 root disk 253, 52 Mar 2 21:04 /dev/dm-52
brw-rw---- 1 root disk 253, 51 Mar 2 21:04 /dev/dm-51
brw-rw---- 1 root disk 253, 46 Mar 2 21:12 /dev/dm-46
brw-rw----+ 1 root disk 253, 42 Mar 3 04:26 /dev/dm-42
brw-rw----+ 1 root disk 253, 39 Mar 3 04:26 /dev/dm-39
brw-rw----+ 1 root disk 253, 44 Mar 3 04:26 /dev/dm-44
brw-rw----+ 1 root disk 253, 35 Mar 3 04:26 /dev/dm-35
brw-rw----+ 1 root disk 253, 36 Mar 3 04:26 /dev/dm-36
brw-rw----+ 1 root disk 253, 43 Mar 3 04:26 /dev/dm-43
brw-rw----+ 1 root disk 253, 37 Mar 3 04:26 /dev/dm-37
brw-rw----+ 1 root disk 253, 38 Mar 3 04:26 /dev/dm-38


Notice that /dev/dm-51,52,53 does not have the + appended to it's permission as the currently used disk in asm has.
So when you try to add the disk to the asm with the below command, you will get below error:
SQL> ALTER DISKGROUP FLYTXT_FRA ADD DISK '/dev/dm-51';
ALTER DISKGROUP FLYTXT_FRA ADD DISK '/dev/dm-51'
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15031: disk specification '/dev/dm-51' matches no disks
ORA-15025: could not open disk "/dev/dm-51"
ORA-15056: additional error message
Linux-x86_64 Error: 13: Permission denied
Additional information: 42
Additional information: 1927546192

Solution is to request the unix admin to change the owner:group to the oracle software owner/installation owner. or add the + sign called (Access Control List, ACL). When the owner of the /dev/dm-51,52,53 files has changed, it appeared like below:

brw-rw----  1 root      disk     253, 19 Jan 31 13:46 /dev/dm-19
brwxrwxrwx  1 oracle oinstall 253, 53 Mar  2 21:04 /dev/dm-53
brwxrwxrwx  1 oracle oinstall 253, 52 Mar  2 21:04 /dev/dm-52
brwxrwxrwx  1 oracle oinstall 253, 51 Mar  2 21:04 /dev/dm-51

brw-rw----  1 root      disk     253, 46 Mar  2 21:12 /dev/dm-46
brw-rw----+ 1 root      disk     253, 36 Mar  3 05:03 /dev/dm-36
brw-rw----+ 1 root      disk     253, 38 Mar  3 05:15 /dev/dm-38
brw-rw----+ 1 root      disk     253, 39 Mar  3 05:15 /dev/dm-39
brw-rw----+ 1 root      disk     253, 42 Mar  3 05:30 /dev/dm-42
brw-rw----+ 1 root      disk     253, 35 Mar  3 05:31 /dev/dm-35
brw-rw----+ 1 root      disk     253, 43 Mar  3 05:40 /dev/dm-43
brw-rw----+ 1 root      disk     253, 44 Mar  3 05:44 /dev/dm-44
brw-rw----+ 1 root      disk     253, 37 Mar  3 05:45 /dev/dm-37

Once this was done, it went successfully as shown below:
SQL> select instance_name, status from v$instance;

INSTANCE_NAME    STATUS
---------------- ------------
+ASM             STARTED

SQL> ALTER DISKGROUP ASM_FRA ADD DISK '/dev/dm-51';

Diskgroup altered.

SQL> ALTER DISKGROUP ASM_FRA ADD DISK '/dev/dm-52';

Diskgroup altered.

SQL> ALTER DISKGROUP ASM_FRA ADD DISK '/dev/dm-53';

Diskgroup altered.

SQL> alter diskgroup ASM_FRA rebalance power 11;

Diskgroup altered.

You can also check the status after the addition, it will appear inside asm.

set pages 1000 lines 300
col PATH for a30
select DISK_NUMBER,MOUNT_STATUS,HEADER_STATUS,MODE_STATUS,STATE,
PATH FROM V$ASM_DISK;

Comments

Popular posts from this blog

How to resolve - ORA-09925: Unable to create audit trail file

How to repair a disk in a diskgroup