Unable To Start RAC Database Instance On Exadata (ORA-3113)
(Doc ID 1342067.1)
Last updated on JANUARY 31, 2020
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle 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
Information in this document applies to any platform.
- Using 18.104.22.168 on Exadata having upgraded from 22.214.171.124
- Have one working Database instance, when trying to start a second Database instance it fails with these messages in the alert.log:
System State dumped to trace file /u01/app/oracle/diag/rdbms/<DB_NAME>/<INSTANCE_NAME>/trace/<INSTANCE_NAME>_diag_1784.trc
Mon Jul 25 14:15:29 2011
PMON (ospid: 1758): terminating the instance due to error 481
Dumping diagnostic data in directory=[cdmp_20110725141529], requested by (instance=2, osid=1758 (PMON)), summary=[abnormal instance termination].
Instance terminated by PMON, pid = 1758
- Trying to mount the instance in sqlplus failed with ORA-3113:
03113, 00000, "end-of-file on communication channel"
// *Cause: The connection between Client and Server process was broken.
// *Action: There was a communication error that requires further investigation.
// First, check for network problems and review the SQL*Net setup.
// Also, look in the alert.log file for any errors. Finally, test to
// see whether the server process is dead and whether a trace file
// was generated at failure time.
- Upgraded Exadata database to 126.96.36.199
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