My Oracle Support
 
Oracle Database Appliance X5-2
 

PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST
 

ODA X5-2 has the capacity to license 36 cores for each server. MOS bugs 21180277 and 21835902 only allow the generation of up to 18 cores (per server). The current workaround is to create a SR with Oracle Support Services and the ODA Support team. Until such time as this bug is fixed support can request a manual ODA Core Key be generated to allow 20,22,24,26,28,30,32,24 and 36 cores (per server). This note provides required information to expedite creation of the X5-2 ODA Core Key.

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-14638447886>

Applies to:

Symptoms

• Using X5-2 ODA
• The ODA X5-2 is registered in My Oracle Support (MOS)

All assets are showing as populated under the MOS ODA CSI including:

  1 - System Identifier  ( ODA Shared system identifier confirmed using the command    oakcli show server )
  2 - First Server Serial Number
  3 - Second Server Serial Number
  4 - Storage Shelf Serial Number

( The Optional Second Storage Shelf is not relevant to this issue)

• After logging in the ODA My Oracle Support (MOS)  account with the proper Admin privileges
  
  

The MOS Core Key Generation GUI bug is that the Pull-down only shows up to 18 cores per server:

The expected pull-down ODA core values should also include choices for 20 up to 36 cores in increments of 2.

Changes

 ODA X5-2 and attempting to generate a Core Key above 18 per server using valid steps from ODA documentation or MOS note(s).

Cause

The problem is due to the following ODA X5-2 Core Key Generation MOS Asset Bugs

Bug 21180277 : MOS Asset UI Pulldown for X5-2 ODA Core Key tops off at 18. Expected 36 p/server

The bug is that the MOS Core Key pull-down stops at 18 vs. 36

Current pull-down values shown are:

    2,4,6,8,10,12,14,16,18

The MOS bugs prevent setting the Core Key Generation to the following values.

    20,22,24,26,28,30,32,34,36

Overview

NOTE: MOS generated Core Keys are applied in on both ODA Servers:
MOS Core Key choices are for a single-server
This value is then applied on EACH server

Core Key Choices are also based equal increments of two on each server.

Example:
   Generating a Core Key of 4 via MOS result in 8 total Cores being enabled ( 4 per server)

Solution

The current workaround is to create an SR with Oracle Support Services - Engineered Systems / ODA

See Note 2254456.1 ODA Manual Core Key Generation Request Procedure for X5-2, X4-2 X3-2 and V1 

Example:

Note: While SRs are designed to be single-problem, single-solution based, IF there is a need for more than one X5-2 ODA needing a CPU Core Key
we will allow each SR to have more than one ODA per SR with the following understanding:

1. All ODAs for the single SR must have the identical CSI# - you cannot mix and match these
2. Information must be provided as previously stated for each ODA.
3. No more than four ODAs per SR
4. The person requesting the Core Keys must be the valid CSI Admin as would be the case if the core key was generated on MOS.
   

FOR SUPPORT - Internal Steps

Send an email to...

chuck.lucas@oracle.com
and cc
jiong.dai@oracle.com
david.lapoint@oracle.com

with the following information to in the EMAIL Header       

Subject:   ODA License Key for X5-2 : SR#3-......... ## cores

In the email body include the following:

• SR#
• Account Name
• CSI

The customer needs to complete the following:

• Cores per server 
• Cores for the ODA      = 2x the number server number above
• ODA Serial#               -- Required to generate the Key
• HW Version                  --  X5-2
• Previous Core Count    -- (if any)
• Business justification:  -- Mandatory if requesting a decrease in core count or use the following due to MOS bug 21180277
  
  e.g. "We are unable to generate 20 Cores due to MOS bug 21180277  ..."

The easiest method is to get the outputs

• oakcli show server  < both nodes
  
  
  

References

This solution has no attachment