Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1956669.1
Update Date:2015-01-08
Keywords:

Solution Type  Problem Resolution Sure

Solution  1956669.1 :   12C Database reports KFOD Error During Oracle Exadata Database Machine Discovery : "DiscoveryWarning: kfod returns status 126"  


Related Items
  • Oracle Platinum Services
  •  
  • Exadata Database Machine X2-2 Full Rack
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Exadata>DB: Exadata_EST
  •  


kfod returns status 126; KFOD Error; OSSCONF; 12c ;Oracle Exadata Database Machine Discovery; Database Machine Discovery; DiscoveryWarning: kfod returns status 126;

Applies to:

Exadata Database Machine X2-2 Full Rack - Version All Versions to All Versions [Release All Releases]
Oracle Platinum Services - Version N/A to N/A
Information in this document applies to any platform.

Symptoms

 Following error is reported during Oracle Exadata Database Machine Discovery on 12C database.

<Machine1> : KFOD Error>DiscoveryWarning: kfod returns status 126. Please check the OSSCONF environment variable and make sure that cellinit.ora and cellip.ora are readable by the EM agent.


Cell Discovery issue



Cause

 This is a known bug in the kfod wrapper script: Unpublished BUG 19682778 - 121021GIPSU: KFOD FILE IN RAC HOME NOT CORRECT AFTER APPLYING GIPSU


Solution

 Workaround:

------------------

- Change the first line in the kfod wrapper script "$OHOME/bin/kfod.bin"

       OHOME=%ORACLE_HOME%

       to

       OHOME=<DB_Home>      Eg. OHOME=/gmioracle/ora_base/product/12.1.0.2


References

<BUG:19682775> - 121021GIPSU: KFOD FILE IN RAC HOME NOT CORRECT AFTER APPLYING GIPSU
<BUG:19682778> - 121021GIPSU: KFOD FILE IN RAC HOME NOT CORRECT AFTER APPLYING GIPSU

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback