ORA-00600 : [kfdvfGetCurrent_baddsk] While Adding Failed Disk into Voting Diskgroup
(Doc ID 2081484.1)
Last updated on MARCH 23, 2023
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
There was storage level issue ,resulting offlining voting disk from ASM diskgroup level.
while adding disk into voting diskgroup ,it failed and crashed the cluster .
Sat Oct 24 10:52:59 2015
WARNING: Disk CRS_0001 in mode 0x7f is now being offlined
Sat Oct 24 10:52:59 2015
NOTE: Attempting voting file refresh on diskgroup CRS
WARNING: Read Failed. group:1 disk:1 AU:0 offset:0 size:4096 <<----------------
NOTE: Refresh completed on diskgroup CRS
. Found 2 voting file(s).
NOTE: Voting file relocation is required in diskgroup CRS
NOTE: Attempting voting file relocation on diskgroup CRS
File_name :: rp6000215_ alert_+ASM1_20151025.log
+ Looks like disk went offline at "Sat Oct 24 10:52:59 2015".
This resulted to move voting disk relocation on CRS diskgroup.
and below state of the disk in ASM level.
Disk was dropped due to external issue (storage/IO subsystem),
+ When it was tried to add it back ,which exposed degenerated PST which took place due to disk access issue earlier.
and to keep consistency of the system ,it brought down the cluster with ORA-600.
NOTE: Attempting voting file relocation on diskgroup CRS
Errors in file /app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_rbal_26730.trc (incident=136148):
ORA-00600: internal error code, arguments: [kfdvfGetCurrent_baddsk], [], [], [], [], [], [], [], [], [], [], []
Incident details in: /app/oracle/diag/asm/+asm/+ASM2/incident/incdir_136148/+ASM2_rbal_26730_i136148.trc
Mon Oct 26 12:20:26 2015
Dumping diagnostic data in directory=[cdmp_20151026122026], requested by (instance=2, osid=26730 (RBAL)), summary=[incident=136148].
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
ERROR: ORA-600 thrown in RBAL for group number 1
Errors in file /app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_rbal_26730.trc:
ORA-00600: internal error code, arguments: [kfdvfGetCurrent_baddsk], [], [], [], [], [], [], [], [], [], [], []
Errors in file /app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_rbal_26730.trc:
ORA-00600: internal error code, arguments: [kfdvfGetCurrent_baddsk], [], [], [], [], [], [], [], [], [], [], []
RBAL (ospid: 26730): terminating the instance due to error 488
Mon Oct 26 12:20:26 2015
opiodr aborting process unknown ospid (14913) as a result of ORA-1092
System state dump requested by (instance=2, osid=26730 (RBAL)), summary=[abnormal instance termination].
System State dumped to trace file /app/oracle/diag/asm/+asm/+ASM2/trace/+ASM2_diag_26667_20151026122028.trc
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 |
| Cause |
| Solution |