Archiving Destination Full Causing ORA-600   and Instance Crash
(Doc ID 748885.1)
Last updated on JANUARY 30, 2022
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.3 to 10.2.0.4 [Release 10.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
In the alert log the following error is reported:
ORA-00600: internal error code, arguments: , , , , , , , 
and the instance is crashed:
DBW0: terminating instance due to error 471
Just before the ORA-600 error there are a lot of errors showing the database is having problems with archiving due to archiving destination became full:
ORA-19502: write error on file <archived redo log file name>, blockno <block number> (blocksize=<block size>)
ORA-27063: number of bytes read/written is incorrect
SVR4 Error: 28: No space left on device
Additional information: -1
Additional information: 1048576
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