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-1561250.1
Update Date:2013-06-17
Keywords:

Solution Type  Problem Resolution Sure

Solution  1561250.1 :   JBOD Nickname is incorrectly set to : Oracle Database Appliance - ... E1  


Related Items
  • Oracle Database Appliance Software
  •  
  • Oracle Database Appliance
  •  
  • Oracle Database Appliance X3-2
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST
  •  


Installation is failing for the new X3-2 V2 ODA with the following error WARNING :   JBOD Nickname is incorrectly set to : Oracle Database Appliance - E1 due to bad or incorrect cabling of the storage shelf

Applies to:

Oracle Appliance Kit - Version 2.5.0.0 to 2.6.0.0 [Release 2.5 to 2.6]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

You are using ODA X3-2 v2 

When running oakcli validate -c storagetopology during ODA setup you see the following warning:

oakcli validate -c storagetopology

INFO    :        Check JBOD Nickname              
WARNING :   JBOD Nickname is incorrectly set to : Oracle Database Appliance - E1
INFO    :       Above details can also be found in log file=/opt/oracle/oak/log/oak1/storagetopology/StorageTopology-2

 

Changes

 New install

Cause

This usually represent a cabling problem with the X3-2 ODA v2 to one of the JBODs storage shelf

  • Loose cable
  • Bad Cable
  • Incorrect cabling

The source of this problem is most likely to occur during an initial installation of the X3-2

This problem should not exist for the ODA v1 X4370M

Solution

If you are getting that error, please check the cabling

If you are sure the cabling is correct, then:

1)    execute Topology_Validation.sh –deploy     as root

  /opt/oracle/oak/bin/stordiag/Topology_Validation.sh –deploy


2)    Run the validate again

         oakcli validate –c storagetopology


     Check to ensure the warning is gone -- if you make it this far then:

3)    Continue with deployment

 

If not, try switching the cabling or as possible switch and replace each cable one at a time and test with a known good cable using the same steps

--    If this also fails please open an SR with EEST / ODA support

 


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