My Oracle Support Banner

ORA-600 [4819] Or ORA-600 [17090] Followed By ORA-308/ORA-27037 Errors (Doc ID 752813.1)

Last updated on SEPTEMBER 10, 2013

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.6 and later
Information in this document applies to any platform.
***Checked for relevance on 11-Sep-2013***

Symptoms

You are getting an ORA-600 [4819] or ORA-600 [17090] error followed by ORA-308 and ORA-27037 errors reported in the alert log after having switched the database out of archive log mode, e.g.:

ORA-00600: internal error code, arguments: [4819], [], [], [], [], [], [], []
ORA-00308: cannot open archived log '<log file name>'
ORA-27037: unable to obtain file status

 

Changes

The database was switched into NOARCHIVELOG mode from ARCHIVELOG mode.

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

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.