This discussion is archived
6 Replies Latest reply: May 16, 2013 3:17 AM by ArniG RSS

Getting ORA-03113: end-of-file on communication channel Process ID Error

ArniG Newbie
Currently Being Moderated
I am using oracle 11g version 11.2.0.1.0. I am getting the below error during startup of database:

C:\Users\Arnab>sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed May 15 13:00:54 2013

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Connected to an idle instance.

SQL> show parameter memeory;
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

SQL> startup
ORACLE instance started.

Total System Global Area 1636814848 bytes
Fixed Size 2176248 bytes
Variable Size 1140853512 bytes
Database Buffers 486539264 bytes
Redo Buffers 7245824 bytes

Database mounted.

ORA-03113: end-of-file on communication channel
Process ID: 1380
Session ID: 191 Serial number: 3


I am pasting the content of the alert log.

ALERT LOG:
__________

ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 1343274407
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Wed May 15 13:01:33 2013
ALTER DATABASE OPEN
LGWR: STARTING ARCH PROCESSES
Wed May 15 13:01:34 2013
ARC0 started with pid=20, OS id=5556
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
FAST_START_MTTR_TARGET 40 is set too low, using minimum achievable MTTR 94 instead.
Wed May 15 13:01:35 2013
ARC1 started with pid=21, OS id=4160
Wed May 15 13:01:35 2013
ARC2 started with pid=22, OS id=3260
Wed May 15 13:01:35 2013
ARC3 started with pid=23, OS id=8080
Errors in file c:\app\arnab\diag\rdbms\orcl\orcl\trace\orcl_ora_1380.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 4294967296 bytes is 100.00% used, and has 81920 remaining bytes available.
ARC1: Archival started
************************************************************************
ARC2: Archival started
You have following choices to free up space from recovery area:
ARC3: Archival started
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
ARC0: STARTING ARCH PROCESSES COMPLETE
then consider changing RMAN ARCHIVELOG DELETION POLICY.
ARC1: Becoming the 'no FAL' ARCH
2. Back up files to tertiary device such as tape using RMAN
ARC1: Becoming the 'no SRL' ARCH
BACKUP RECOVERY AREA command.
ARC2: Becoming the heartbeat ARCH
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
Errors in file c:\app\arnab\diag\rdbms\orcl\orcl\trace\orcl_arc1_4160.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 4294967296 bytes is 100.00% used, and has 81920 remaining bytes available.
DELETE EXPIRED commands.
************************************************************************
************************************************************************
You have following choices to free up space from recovery area:
Errors in file c:\app\arnab\diag\rdbms\orcl\orcl\trace\orcl_ora_1380.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 41580544 bytes disk space from 4294967296 limit
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
ARCH: Error 19809 Creating archive log file to 'C:\APP\ARNAB\BACKUPS\ORCL\ARCHIVELOG\2013_05_15\O1_MF_1_178_%U_.ARC'
then consider changing RMAN ARCHIVELOG DELETION POLICY.
Errors in file c:\app\arnab\diag\rdbms\orcl\orcl\trace\orcl_ora_1380.trc:
ORA-16038: log 1 sequence# 178 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: 'C:\APP\ARNAB\ORADATA\ORCL\REDO01.LOG'
2. Back up files to tertiary device such as tape using RMAN
USER (ospid: 1380): terminating the instance due to error 16038
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
Instance terminated by USER, pid = 1380


My Database instance is not connectable.Please HELP!!!

Thanks
Arni

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points