We Can't Use A Disk That Has Been Added To The Asm Disk Group Ora-17505
(Doc ID 401026.1)
Last updated on APRIL 24, 2018
Applies to:Oracle Server - Enterprise Edition - Version: 10.2.0.2
This problem can occur on any platform.
One disk has been wrongly added to an ASM diskgroup as follows:
1. the disk was actually a LUN created with the LVM
2. permissions on the LUN were ok (owner: oracle.dba, mode: 660).
3. permissions on the physical disk were not ok (owner: root)
Permissions are changed as they should on the base disk (owner: oracle.dba, mode: 660). Nevertheless, the disk figures as CANDIDATE in v$asm_disk and apparently cannot be dropped or readded. free_mb is 0 and looks as if the rebalance starts but never completes.
Adding the disk fails with:
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15029: disk '/dev/asmef/dsk009' is already mounted by this instance
kfed on the disk shows that it has a null header, ie: there is no ASM information.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!