ODA X5-2 MOS Core Key GUI Not Able To Generate a Core Key Above 18 per server. MOS Pull-down Only Goes up to 18 vs. Up to 36
(Doc ID 2252677.1)
Last updated on JANUARY 09, 2024
Applies to:
My Oracle Support - Version 6 to 6 [Release 6]Oracle Database Appliance X5-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
Symptoms
- Using X5-2 ODA Bare Metal
- The ODA X5-2 is registered in My Oracle Support (MOS)
Note: ODA Virtualized Platform (ODAVP) does not use Core Keys:
Any conversion of ODA Bare Metal to ODA VP requires removing the Core Keys Before deploying the ODA as a virtualized platform.
Refer to NOTE:1559091.1 - ODA (Oracle Database Appliance): How To Reset the license core keys before re-image to the Virtualized Platform option
Any conversion of ODA Bare Metal to ODA VP requires removing the Core Keys Before deploying the ODA as a virtualized platform.
Refer to NOTE:1559091.1 - ODA (Oracle Database Appliance): How To Reset the license core keys before re-image to the Virtualized Platform option
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
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |