Master Note: Troubleshooting ORA-03113
(Doc ID 1506805.1)
Last updated on AUGUST 25, 2021
Applies to:Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 9.2 to 12.1]
Oracle Net Services - Version 184.108.40.206 to 220.127.116.11 [Release 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 11-Jan-2016***
An ORA-3113 "end of file on communication channel" error is a general error usually reported by a client process connected to an Oracle database. The error basically means 'I cannot communicate with the Oracle shadow process'. As it is such a general error more information must be collected to help determine what has happened - this error by itself does not indicate the cause of the problem. For example, ORA-3113 could be signalled for any of these following scenarios:
- Server machine crashed
- Your server process was killed at the O/S level
- Network problems
- Oracle internal errors (ORA-600 / ORA-7445) / aborts on the server
- Client incorrectly handling multiple connections
- etc.. etc.. etc.. - a lot of possible causes !!
This article describes what information to collect for an ORA-3113 error. It is common for this error to be accompanied by other errors such as:
- ORA-1041 internal error. hostdef extension doesn't exist
- ORA-3114 not connected to ORACLE (This error is reported before the ORA-3113 when PL/SQL is used)
- ORA-1012 not logged on
These are all symptomatic of being disconnected from Oracle.
This note is an updated version of archived
<Note 17613.1> - ORA-03113 on Unix - What Information to Collect
For older information, please refer to <Note 17613.1>
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
|(A) ORA-3113 when attempting to STARTUP Oracle|
|A1) Errors connecting as SYSDBA or on startup nomount|
|A2) Errors Mounting the database|
|A3) Errors on RECOVER DATABASE|
|A4) Errors on ALTER DATABASE OPEN|
|(B) ORA-3113 attempting to connect to the database using Oracle Net |
|(C) Client sees ORA-3113 running SQL / PLSQL|
|(D) Server trace reports ORA-3113|
|(E) Additional Checks / Information|