ASM tools used by Support : KFOD, KFED, AMDU (Doc ID 1485597.1)

In this Document

---

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
Information in this document applies to any platform.

PURPOSE

This document is provided for educational purposes in order to have a general overview of ASM utilities: KFOD, KFED, AMDU .

Oracle Support may ask for additional or other specific information, depends on your case.

Note 1345068.1 - Files for Upload When Creating ASM/Storage Service Requests

SCOPE

 General overview of ASM utilities KFOD, KFED, AMDU usage.

DETAILS

1. KFOD - Kernel Files OSM Disk

KFOD utility is used to simulate the disk discovery from the operating system level and it can be found in $GRID_HOME/bin directory (or ASM_HOME/bin in older releases).

Note: 
1) KFOD is used at installation time as well (by OUI,DBCA or ASMCA) in order to perform disk discovery. 
2) In case of a failed installation (e.g no $GRID_HOME/bin existing yet) KFOD can be found under your stage folder: <stage_folder>/grid/stage/ext/bin/
In such cases you might need to set LD_LIBRARY_PATH to <stage_folder>/grid/stage/ext/lib.

Help screen can be seen using:

 
The usual syntax used for disk discovery is:

EXAMPLE

 

---

 2. KFED - Kernel Files metadata EDitor

KFED is a useful tool which allows to analyze ASM disk header information when ASM diskgroups can not be mounted.

Note 1180491.1 - KFED Tool For Windows OS. Note 1346190.1 - KFED.PL for diagnosing - ORA-15036 ORA-15042 ORA-15020 ORA-15033

NOTE:
KFED executable comes with installation from 11.1 onwards; for the older version you must build it.
But it is not included  the source of the software, therefore it is not available until GI installation completes.  
If you need to use it before GI being installed, please refer

Note 1505005.1 - Where to find kfed utility before Oracle Grid Infrastructure is installed

 

Help screen can be seen using:

 The usual syntax used for reading ASM disk header is: 

 EXAMPLE:

NOTES:

1) KFED returns a readable output only when devices are/were part of an ASM diskgroup.
Otherwise (if the device hasn't been added to a diskgroup yet or the disk is not valid anymore) the output looks like:

KFED-00322: Invalid content encountered during block traversal: [kfbtTraverseBlock][Invalid OSM block type][][0]

2) In case of a non-default AU size, you should specify it in the command:

$> kfed read <your_device> AUSZ=<au_size>

 

 

---

 3. AMDU - ASM Metadata Dump Utility

AMDU is an utility to extract all the available metadata from one or more ASM disks and/or generate formatted printouts of individual blocks.The utility does not require that any diskgroup to be mounted.

Oracle Support may ask you to provide AMDU output, especially when facing internal errors related to the ASM metadata

 

NOTE:
AMDU executable comes with installation from 11.1 onwards. Although this tool was released with 11g, it can be used with ASM 10g as well.

Note 553639.1 - Placeholder for AMDU binaries and using with ASM 10g  

The usual syntax used for dumping metadata related to a diskgroup is:

NOTE:

Every time AMDU is executed a directory is created on the current location, unless it is override by parameter -directory.  
The directory will have the format amdu_YYYY_MM_DD_HH24_MM_SS

 

The default command  will generate following files:

 

The report.txt file shows the header info of the disks belonging to diskgroup, like below:

EXAMPLE:

  

---

CAUTION: DO NOT USE the above tools with options which can damage your disks, without Oracle Support guidance.

 

 

REFERENCES

NOTE:1345068.1 - Files for Upload When Creating ASM/Storage Service Requests
NOTE:1346190.1 - KFED.PL for diagnosing - ORA-15063 ORA-15042 ORA-15020 ORA-15033





NOTE:553639.1 - Placeholder for AMDU binaries and using with ASM 10g
NOTE:1505005.1 - Where to find kfed utility before Oracle Grid Infrastructure is installed.
NOTE:1180491.1 - KFED Tool For Windows OS.