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-2350446.1
Update Date:2018-05-30
Keywords:

Solution Type  Problem Resolution Sure

Solution  2350446.1 :   Exachk Version 12.2.0.1.4_20171212 Execution Fails On Exalogic With October 2017 & later PSU's With "An unexpected error occurred" Error  


Related Items
  • Oracle Exalogic Elastic Cloud Software
  •  
  • Oracle Exalogic Elastic Cloud Software
  •  
  • Exalogic Elastic Cloud X6-2 Hardware
  •  
Related Categories
  • PLA-Support>Eng Systems>Exalogic/OVCA>Oracle Exalogic>MW: Exalogic Core
  •  




Created from <SR 3-16643131561>

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.2.160719 and later
Exalogic Elastic Cloud X6-2 Hardware - Version X6 to X6 [Release X6]
Linux x86-64

Symptoms

Note: Applicable to both Exalogic Physical and Virtual Racks. 

On Exalogic running with October 2017 & later PSU's, executing Exachk Version 12.2.0.1.4_20171212 fails with "An unexpected error occurred" error as shown below.

Do you want to continue running on this node? y
Running exachk on exl2test01
Enter IP address for spine infiniband switch : 10.x.x.x
An unexpected error occurred. Please check '/u01/common/general/exachk_12.2.0.4/exachk011318_090446_error.log' for more information. Run 'exachk' again with -debug and upload the resulting debug log to an Oracle Support Service Request.

 

Changes

 Using Exachk version to 12.2.0.1.4_20171212.

Cause

This is known Bug 27397002 with the Exachk version 12.2.0.1.4_20171212.

Solution

This known issue is fixed in latest Exachk version 18.2.0_20180518.

To fix this known issue download and use latest Exachk version available from below MOS Note.

<Note 1449226.1>: Exachk Health-Check Tool for Exalogic

INTERNAL NOTE TO SUPPORT

In any case Customer cannot use the latest Exachk version and has to continue with Exachk version 12.2.0.1.4_20171212, the workaround for this issue is to run Exachk using "-legacy" argument at the end of "./exachk" as shown below

./exachk -legacy 

 

References

<BUG:27397002> - EXACHK FAILURE AFTER UPGRADING PSU AND EXACHK TO EXACHK 12.2.0.1.4
<BUG:27272040> - PQA: EXACHK 12.2.0.1.4 NOT WORKING
<NOTE:1449226.1> - Exachk Health-Check Tool for Exalogic
<NOTE:1478378.1> - Exalogic Exachk Health-Check Tool Known Issues
<NOTE:2286560.1> - Known Issues for Exalogic 2.0.6.3.X Patch Set Updates
<NOTE:2356715.1> - Exalogic Exachk Version 12.2.0.1.4_20171212 Guest vServers Checks Not Working
<NOTE:2355601.1> - Exalogic Exachk Version 12.2.0.1.4_20171212 "daemon" Feature Does Not Work As Expected

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