ODA: Version 1 (V1) Fails to Apply the Core Key Due to an Invalid Serial Number : Command "oakcli apply core_config_key" Failure (Doc ID 1503174.1)

Last updated on DECEMBER 15, 2015

Applies to:

Oracle Database Appliance Software - Version 2.3.0.0 to 2.4.0.0 [Release 2.3 to 2.4]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
While there can be several reasons for the Serial Number messages on the ODA Bug 14206882 - OAKVALIDATE ERROR: INVALID SYSTEM SERIAL NUMBER AFTER PATCH TO 2.3 only applies to ODA Hardware Version V1. The reason is that V1 is the ONLY ODA hardware version which goes back as far as 2.3. The release of the X3-2 ( ODA V2) started no earlier than 2.4 but was most commonly known as being 2.5 and higher. No ODA Patches from 2.3 or earlier can be applied on any of the newer ODA HW versions

Symptoms

Requires OAK version 2.3.0.0.0 and ODA Hardware Version V1 ( SUN FIRE X4370 M2 SERVER )

To confirm if using the V1 ODA issue the following as root

# fwupdate list sp_bios

Example

 

Symptoms

1. oakcli apply core_config_key fails with :           Failed to set core count due to invalid serial number

-OR-

2. oakcli validate -c SystemComponents  fails with 'Error: Invalid System Serial number'

 

Trying to fetch the serial number (which oakcli also uses internally to obtain the serial number) -- Only valid for the ODA V1 X4370 M2

[root@oak1 ~]# /usr/sbin/dmidecode -t1 |grep Serial


       Serial Number: Not Available

 

 

Changes

 Applied OAK version 2.3.0.0.0

-OR-

New ODA deployment with 2.3.0.0.0

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms