Oracle Database Appliance
 

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

In this Document

Symptoms

Cause

Solution

References

Applies to:

Symptoms

 Applies to ODA X5-2, X4-2,X3-2 V1 and ODA X6-2 HA
 Does not apply to ODA X6-2 S/M/L aka ODA Lite

Unable to generate a Core Key on My Oracle Support after multiple attempts leading to the creation of an SR to provide a new ODA Core Key

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

Cause

 There are various reasons a manually generated Core Key may be required for an ODA.

Examples

• Bug 21180277 : MOS Asset UI Pulldown for X5-2 ODA Core Key tops off at 18. Expected 36 p/server
• Purchasing a new Engineered System and wanting to use / move existing license to the new unit
• MOS timing out or receiving 'try again later' prompts after several attempts
• Applying a Core Key after support has ended for the Core Key Generation ( usually 1 or 2 years after purchase unless renewed)
• Other issues as appropriate

Solution

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

 The easiest method for ODA information is:

1. oakcli show server                    << both nodes -- This should include the SYSTEM SERIAL NUMBER for the ODA X5-2 and is required to manually create the ODA Core Key.
2. oakcli show core_config_key      < Mandatory for pre-existing Core Counts
3. oakcli show env_hw                   < Provides the HW Model and if ODA VP or Bare Metal

Example: # oakcli show server

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:

• All ODAs for the single SR must have the identical CSI# - you cannot mix and match these
• Information must be provided as previously stated for each ODA.
• No more than four ODAs per SR
• 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

Once the SR is created 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 Core License Key for X*-2 : SR#3-.........  ;  ## cores total

In the email body include the following:

• SR#
• Account Name
• CSI

The customer needs to complete the following which should also exist in the SR:

• 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 to get ODA required information:

1. oakcli show server                  << both nodes -- This should include the SYSTEM SERIAL NUMBER for the ODA X5-2 and is required to manually create the ODA Core Key.
2. oakcli show core_config_key  < Mandatory for pre-existing Core Counts
3. oakcli show env_hw               < Provides the HW Model and if ODA VP or Bare Metal

References

This solution has no attachment