Professional Documents
Culture Documents
Home Knowledge Systems & Projects Certifications Patches & Updates Service Request Dashboard Support Customer GRP
Browse | Subscriptions | Authoring Wizard | Documents In Progress | Query By Attribute
Filter Search By Keyword ID Adv Search Alt Search Recent Docs Recent Searches Sun Part # Search Last Hit List
Knowledge > Browse > Advanced Search > Search Results > Document Display
Next Steps
ASM disk group mount fails with ORA-15036: disk <name> is truncated (Doc ID 1077175.1)
Modified 05-OCT-2011 Type PROBLEM Status PUBLISHED(EXTERNAL) Priority 3 To Bottom
In this Document
Symptoms
Changes
Cause Add Comment
Solution View Document Statistics
References
Rate Article Now
Excellent
Applies to:
Good
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.1 [Release: 10.2 to 11.2] Poor
Information in this document applies to any platform. Did this resolve the problem?
NOTE: kfed is an Oracle internal utility and should not be used unless advised by Oracle Support. Interpreting kfed output is outside of the scope of this article. Yes
No
Symptoms
Just Browsing
Was this easily located?
This problem can be seen in a both single instance and RAC and in any ASM version.
Very Easy
Attempt to mount ASM disk group (DG1) fails with the following errors: Somewhat Easy
Not Easy
Changes
Added two disks, ORCL:DATA09 and ORCL:DATA10 to ASM disk group DG1.
Resized the disks at the OS level.
Cause
System/storage administrator presented two new LUNs, 65530 MB each, to the OS to be used by ASM.
ASM administrator/DBA created ASMLIB disks DATA09 and DATA10 with those LUNs and added the disks to disk group DG1.
As the disks were incorrectly sized, the system/storage admin resized the disks to the intended size - 61530 MB. But they did not advise ASM administrator/DBA about this
change, so noALTER DISKGROUP RESIZE DISK was performed at the ASM level.
Next time the disk group mount was attempted, the above errors were received and the disk group could not be mounted.
Solution
1. Verify that the issue is just with the disk size mismatch between ASM metadata and the actual disk size. To do that, make use of ASM utility kfed
and OS utility fdisk.
1.1. The affected disks (ORCL:DATA09 and ORCL:DATA10) are ASMLIB disks:
$ ls -l /dev/oracleasm/disks
brw-rw---- 1 oracle dba 8, 2 Mar 14 11:25 DATA01
...
brw-rw---- 1 oracle dba 8, 161 Mar 14 11:25 DATA09
brw-rw---- 1 oracle dba 8, 177 Mar 14 11:25 DATA10
That shows the ASM disk header looks fine. Do the same for disk DATA10...
That shows that both disk headers have the disk size as 65530 MB.
1.4. Check the disk size of the associated LUNs (sd devices):
# fdisk -l /dev/sdk
# fdisk -l /dev/sdl
Above shows that both disk partitions (/dev/sdk1 and /dev/sdl1) are 61530 MB.
2. Using kfed utility correct the disk size info by updating the ASM disk headers for disks DATA09 and DATA10.
2.1. Read the ASM disk header and save the output into a file:
2.2. Using a text editor (e.g. vi) edit file /tmp/DATA09_header.kfed, to modify the following line:
Modify:
kfdhdb.dsksize: 65530 ; 0x0c4: 0x0000fffa
to
kfdhdb.dsksize: 61530 ; 0x0c4: 0x0000f05a
3. Mount the disk group and update the disk size info at the ASM level
$ sqlplus / as sysdba (or 'sqlplus / as sysasm' in ASM version 11.1 and above)
3.3. Dismount and mount the disk group to verify that it mounts with no errors.
References
@ NOTE:284646.1 - Creating and using the kfed utility to view ASM disk header
▼Related
Products
Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition > STORAGE > ASM Administration, Errors
Knowledge Categories
ASM
DISK GROUP
Errors
ORA-15036
ORA-15032
▼Document Attributes