I am getting error ORA-03113 at the time of startup database. I removed some old archive log files as per solution I got on google. But still I am unable to startup db. But, I am able to connect other database (dbname: CTS) on same server. Please suggest solution on this

Please find below current OS and DB configuration details and received errors.

**DB version is : 11g
Linux version : Linux ctsvm.oraclexpert.com 2.6.18-194.el5PAE #1 SMP Mon Mar 29 20:19:03 EDT 2010 i686 i686 i386 GNU/Linux**

Error I received is as below:- Disconnected from Oracle Database 11g Enterprise Edition Release - Production With the Partitioning, OLAP, Data Mining and Real Application Testing options

[oracle@ctsvm dbs]$ cd
[oracle@ctsvm ~]$ export ORACLE_SID=DBAYOG
[oracle@ctsvm ~]$ sqlplus '/as sysdba'
SQL*Plus: Release Production on Sun Oct 27 00:52:39 2013
Copyright (c) 1982, 2010, Oracle.  All rights reserved.
Connected to an idle instance.

SQL> startup
ORACLE instance started.
Total System Global Area  422670336 bytes
Fixed Size                  1344616 bytes
Variable Size             339741592 bytes
Database Buffers           75497472 bytes
Redo Buffers                6086656 bytes
Database mounted.
ORA-03113: end-of-file on communication channel
Process ID: 4293
Session ID: 1 Serial number: 5
  • 2
    Look in the alert log.
    – DCookie
    Commented Oct 26, 2013 at 15:16
  • Hi DCookie, I check alert log and removed old archives from dir.[oracle@ctsvm archivelog]$ ls -lrth total 24K drwxr-x--- 2 oracle oinstall 4.0K Oct 21 01:30 2013_10_21 drwxr-x--- 2 oracle oinstall 4.0K Oct 23 21:50 2013_10_23 drwxr-x--- 2 oracle oinstall 4.0K Oct 24 00:00 2013_10_24 drwxr-x--- 2 oracle oinstall 4.0K Oct 24 03:35 2013_10_19 drwxr-x--- 2 oracle oinstall 4.0K Oct 24 03:36 2013_10_14 drwxr-x--- 2 oracle oinstall 4.0K Oct 27 00:15 2013_10_27
    – Yogeish
    Commented Oct 26, 2013 at 16:50
  • Did you find any ORA-0600 or 7445 errors in the alert log?
    – Jon Heller
    Commented Oct 26, 2013 at 21:00
  • 2
    Not archive log, ALERT log.
    – DCookie
    Commented Oct 26, 2013 at 23:52
  • 2
    --> Cleanup archives with rman. put database in mount. backup archivelog all delete input; or delete archivelog all;
    – Munchi
    Commented Oct 28, 2013 at 7:59

3 Answers 3


In your case, it seems that database can not pass from mounted to open state, for any reason. Please check alert log and any generated file in your trace directories. EDIT: I removed comment about ORA-00600 (I wrongly read your post 1st time...)

  • Hi Igr, in alert.log i cant see ORA-00600 error. Please let me know the solutions on error ORA-03113.
    – Yogeish
    Commented Oct 27, 2013 at 15:26
  • I just had the same issue. Thank for pointing out that we should check alert log. I saw that it was ORA-19809: limit exceeded for recovery files I just followed this which recommends to increase size of flash_recovery_area with ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=<put the new value here> SCOPE=BOTH;
    – Jason Krs
    Commented Aug 19, 2017 at 11:51

Please utilize oraenv to make sure you have all environment variables set before startup.

. oraenv (don't forget the dot)
--> input the SID
sqlplus / as sysdba
startup force --performs a shutdown abort + startup
  • Dear Guys, now i am getting error ORA-01034 oracle not available. please suggest.
    – Yogeish
    Commented Oct 30, 2013 at 6:21
  • Please post output from: cat /etc/oratab set | grep ORA Commented Oct 30, 2013 at 14:35
  • Hi,plz find the o/p :- # This file is used by ORACLE utilities. It is created by root.sh # $ORACLE_SID:$ORACLE_HOME:<N|Y>: # Multiple entries with the same $ORACLE_SID are not allowed.
    – Yogeish
    Commented Nov 3, 2013 at 17:25
  • and... #set | grep ORA ? Commented Nov 3, 2013 at 20:07
  • 1
    Please update your question with relevant information. I want "echo $PATH", "set |grep TWO_TASK", "set | grep ORA", "whereis sqlplus", "set |grep TNS". Then with your oracle os account fire up the db. I would like to see all these steps in your output. Tip: Sometimes I use strace on sqlplus to see what is going on. Commented Nov 25, 2013 at 21:16

The archive log backups are failing hence the archive logs are getting accumulated on the mount points making the DB to get into hung state. Increase the size of the db_recovery_file_dest_size parameter and open the database and check. It should work.

alter database mount;  
alter system set db_recovery_file_dest_size=<>G scope=both;  
alter database open;  

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.