ORA-15030 When Creating Diskgroup and Diskgroup Name Already Referenced in ASM_DISKGROUPS Parameter
(Doc ID 1536701.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Information in this document applies to any platform.
The following errors were seen when trying to create a diskgroup that had previously been removed (due to corruption). The examples in this note use the diskgroup name 'FRA01' as the name of the diskgroup that we want to be created.
Tue Feb 26 13:30:32 2013
SQL> alter diskgroup FRA01 add disk '/dev/oracleasm/disks/ASMFRA01','/dev/oracleasm/disks/ASMFRA02','/dev/oracleasm/disks/ASMFRA03'
ORA-15032: not all alterations performed
ORA-15001: diskgroup "FRA01" does not exist or is not mounted
The kfed data showed that the disks were not part of any diskgroup. This is the entire kfed entry. Note that fields such as "kfdhdb.dsknum:", "kfdhdb.grptyp:", "kfdhdb.grpname:", etc. are not displayed. These would be expected to be populated if the disks were part of a diskgroup.
kfbh.endian: 0 ; 0x000: 0x00
kfbh.hard: 0 ; 0x001: 0x00
kfbh.type: 0 ; 0x002: KFBTYP_INVALID
kfbh.datfmt: 0 ; 0x003: 0x00
kfbh.block.blk: 0 ; 0x004: blk=0
kfbh.block.obj: 0 ; 0x008: file=0
kfbh.check: 0 ; 0x00c: 0x00000000
kfbh.fcn.base: 0 ; 0x010: 0x00000000
kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
kfbh.spare1: 0 ; 0x018: 0x00000000
kfbh.spare2: 0 ; 0x01c: 0x00000000
A diskgroup with the same name had been removed, due to corruption.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document