ODA Troubleshooting ODA Core Key Generation and Application Problems
(Doc ID 1638577.1)
Last updated on JANUARY 11, 2018
Applies to:Oracle Database Appliance X5-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance X6-2 HA Hardware - Version All Versions to All Versions [Release All Releases]
Oracle Database Appliance Software - Version 188.8.131.52 to 184.108.40.206 [Release 2.1 to 12.1]
Information in this document applies to any platform.
ODA, Oracle Database Appliance, OAK, oakcli , Core Key, Core Count, Core Key generation,
The Oracle Database Appliance (ODA) also known as the ODA HA (High Availability) uses a Capacity On-Demand CPU software licensing feature. ODA Capacity On-Demand allows you to easily scale up to 48 processor cores without incurring the costs and downtime usually associated with hardware upgrades as ALL cores already exist within the ODA hardware. Each ODA server (2 servers per ODA) uses a Core Key to set the proper licensed count.
This document provides guidance on common questions and problems regarding the ODA Core Key generation and application process. This note does not apply to the ODA Lite series which includes Small, Medium and Large (S/M/L) single server versions.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|What is the current Core Key Count|
|Describing the Core Key Problem |
|Core Key Diagnostic Data Collection|
|Examples of Core Key Diagnostic Collection|
|Supplemental Core Key Symptom Quick Reference Matrix|