ODA JBOD addition fails resulting in ORA-600 [KfOdaApplianceInit0], [2], [3], Traces and Errors referenced in one of the+ASM alert.logs
(Doc ID 1991118.1)
Last updated on SEPTEMBER 16, 2021
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Pre-requisites
- You are using the Oracle Database Appliance (ODA) (bare metal or ODAVP)
- The ODA version is pre 12.1.2.0.0
- You are in the process of adding a new / second Storage Shelf to either an X3-2 or X4-2
- The JBOD addition is incomplete or fails with errors*
- One ASM instance Alert.log shows ORA-600 [kfOdaApplianceInit0], [2], [3], traces
Other symptoms can include
- Unable to connect to ASM instance using SQLPLUS
- Commands from SQLPLUS on ASM fail including DESC or Simple Select
- Show SGA fails from one of the ASM instances
- One ASM instance may not start
- Oakd may not start on one Node
- The directory structure for one node may be near or at 100% Full
- You may find references to thousands of trace files in the alert.log or TRACE directory
COMMANDS
The following commands can be used to confirm the above prerequisites
Changes
Recently added or attempted to add a second JBOD to an X3-2 or X4-2 system
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! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |