ODA Oracle Database Appliance Manual Core Key Generation Request Procedure for X5-2, X4-2 X3-2 and V1
(Doc ID 2254456.1)
Last updated on JANUARY 07, 2024
Applies to:
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]Information in this document applies to any platform.
Symptoms
When unable to generate a Core Key on My Oracle Support or using existing method leading to the creation of an SR to provide a new ODA Core Key
Applies to:
- Bare Metal configurations (Only)
- ODA X5-2, X4-2,X3-2 V1 and early ODA versions on X6-2 HA
This Core Key procedure does not apply to the following ODA configuration
- ODA on DCS Stack - DCS uses a self-generated and applied key using the new ODA*CLI command local to the server
For any system on the DCS stack refer to the Documentation for commands: e.g. odacli update-cpucore -c <core number> - ODAVP* for any hardware version
- See Doc ID 1559091.1 when converting from ODA BM to ODAVP -- ODA (Oracle Database Appliance): How To Reset the license core keys before re-image to the Virtualized Platform option
* KVM implementation is not discussed in this note
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
Changes
New Core Key generation is failing:
This can be for a change in the previous Core Key count or for new usage.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |