Top Issues Related to KFED Report
(Doc ID 2247594.1)
Last updated on JANUARY 24, 2020
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Purpose of this document is to provide summary of top issues reported while using KFED utility / reports.
This document is intended for Oracle Clusterware/ASM Administrators and Oracle support engineers.
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
|Issue #1: KFED.PL for diagnosing - ORA-15063 ORA-15042 ORA-15020 ORA-15033|
|Issue #2: KFED - ERROR!!! could not initialize the diag context|
|Issue #3: KFED Reports “KFBTYP_INVALID” & OS Metadata [EFI PART] In ASMLIB Disk /ASM disk Member (ASM Disk Overlapping : Scenario #1)|
|Issue #4: KFED Reports “ *** Unknown Enum ***” & OS Metadata [AIX LVCB..raw...] In ASMLIB Disk /ASM disk Member (ASM Disk Overlapping : Scenario #4)|
|Issue #5: KFED Is Reporting KFED-00322 [Invalid OSM block type] On Healthy ASM Member Disks|