Home » Infrastructure » Linux » ORA-03113: end-of-file on communication channel (oracle 11.2 linux)
ORA-03113: end-of-file on communication channel [message #543053] Mon, 13 February 2012 00:20 Go to next message
nehhaverma
Messages: 34
Registered: September 2009
Location: JAIPUR
Member
Hi

my flash recovery area was full so i did shutdown immediate but it takes about 1 hr so i did shutdown abort and remove some files from flash_recovery_area now I ran the cmd startup but database is not going to up it is now mount mode and error comes:

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 9174
Session ID: 191 Serial number: 3

Please do help it is really very very urgent

Regards//Neha
Re: ORA-03113: end-of-file on communication channel [message #543055 is a reply to message #543053] Mon, 13 February 2012 00:33 Go to previous messageGo to next message
Kamran Agayev
Messages: 145
Registered: February 2009
Location: Azerbaijan, Baku
Senior Member

Post what you have in your alert.log file
Re: ORA-03113: end-of-file on communication channel [message #543061 is a reply to message #543053] Mon, 13 February 2012 01:11 Go to previous messageGo to next message
Michel Cadot
Messages: 59425
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
Please do help it is really very very urgent


Nothing is urgent in a forum but YOU to read the OraFAQ Forum Guide.

Use SQL*Plus and copy and paste your session, the WHOLE session.

Before, read How to use [code] tags and make your code easier to read.
Make sure that lines of code do not exceed 80 characters when you format.
Indent the code, use code tags and align the columns in result.
Use the "Preview Message" button to verify.
Also always post your Oracle version, with 4 decimals.

ORA-03113 => Have a look at alert.log and trace files.

Regards
Michel

Re: ORA-03113: end-of-file on communication channel [message #543074 is a reply to message #543055] Mon, 13 February 2012 01:31 Go to previous messageGo to next message
nehhaverma
Messages: 34
Registered: September 2009
Location: JAIPUR
Member
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 2978281830
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Sun Feb 12 23:53:14 2012
ALTER DATABASE OPEN
LGWR: STARTING ARCH PROCESSES
Sun Feb 12 23:53:14 2012
ARC0 started with pid=20, OS id=10513
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Sun Feb 12 23:53:15 2012
ARC1 started with pid=21, OS id=10519
Sun Feb 12 23:53:15 2012
ARC2 started with pid=22, OS id=10523
ARC1: Archival started
Sun Feb 12 23:53:15 2012
ARC3 started with pid=23, OS id=10527
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
Errors in file /u01/app/oracle/diag/rdbms/tssgd/TSSGD/trace/TSSGD_ora_10509.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 8388608000 bytes is 100.00% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
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.
************************************************************************
Errors in file /u01/app/oracle/diag/rdbms/tssgd/TSSGD/trace/TSSGD_ora_10509.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 46773248 bytes disk space from 8388608000 limit
ARCH: Error 19809 Creating archive log file to '/u01/app/oracle/flash_recovery_area/TSSGD/archivelog/2012_02_12/o1_mf_1_199_%u_.arc'
Errors in file /u01/app/oracle/diag/rdbms/tssgd/TSSGD/trace/TSSGD_ora_10509.trc:
ORA-16038: log 1 sequence# 199 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/u02/oradata/TSSGD/redo01.log'
USER (ospid: 10509): terminating the instance due to error 16038
Instance terminated by USER, pid = 10509
Sun Feb 12 23:56:01 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Using LOG_ARCHIVE_DEST_1 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =27
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
Using parameter settings in server-side spfile /u01/app/oracle/product/11.2.0/db_1/dbs/spfileTSSGD.ora
System parameters with non-default values:
processes = 150
memory_target = 1584M
control_files = "/u02/oradata/TSSGD/control01.ctl"
control_files = "/u01/app/oracle/flash_recovery_area/TSSGD/control02.ctl"
db_block_size = 8192
compatible = "11.2.0.0.0"
log_archive_format = "%t_%s_%r.dbf"
db_recovery_file_dest = "/u01/app/oracle/flash_recovery_area"
db_recovery_file_dest_size= 8000M
undo_tablespace = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain = "dpcellc.com"
global_names = FALSE
dispatchers = "(PROTOCOL=TCP) (SERVICE=TSSGDXDB)"
shared_servers = 1
local_listener = "LISTENER_TSSGD"
audit_file_dest = "/u01/app/oracle/admin/TSSGD/adump"
audit_trail = "DB"
db_name = "TSSGD"
open_cursors = 300
diagnostic_dest = "/u01/app/oracle"
Sun Feb 12 23:56:02 2012
PMON started with pid=2, OS id=10606
Sun Feb 12 23:56:02 2012
VKTM started with pid=3, OS id=10610
VKTM running at (100ms) precision
Sun Feb 12 23:56:02 2012
GEN0 started with pid=4, OS id=10616
Sun Feb 12 23:56:02 2012
DIAG started with pid=5, OS id=10620
Sun Feb 12 23:56:02 2012
DBRM started with pid=6, OS id=10624
Sun Feb 12 23:56:02 2012
PSP0 started with pid=7, OS id=10628
Sun Feb 12 23:56:02 2012
DIA0 started with pid=8, OS id=10632
Sun Feb 12 23:56:02 2012
MMAN started with pid=9, OS id=10636
Sun Feb 12 23:56:02 2012
DBW0 started with pid=10, OS id=10640
Sun Feb 12 23:56:02 2012
LGWR started with pid=11, OS id=10644
Sun Feb 12 23:56:02 2012
CKPT started with pid=12, OS id=10657
Sun Feb 12 23:56:02 2012
SMON started with pid=13, OS id=10661
Sun Feb 12 23:56:02 2012
RECO started with pid=14, OS id=10665
Sun Feb 12 23:56:02 2012
MMON started with pid=15, OS id=10669
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
Sun Feb 12 23:56:02 2012
MMNL started with pid=16, OS id=10673
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u01/app/oracle
Sun Feb 12 23:56:02 2012
Completed: ALTER DATABASE MOUNT
Mon Feb 13 00:00:09 2012
alter database open
Mon Feb 13 00:00:09 2012
LGWR: STARTING ARCH PROCESSES
Mon Feb 13 00:00:09 2012
ARC0 started with pid=20, OS id=10828
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Mon Feb 13 00:00:10 2012
ARC1 started with pid=21, OS id=10834
Mon Feb 13 00:00:10 2012
ARC2 started with pid=22, OS id=10838
ARC1: Archival started
Mon Feb 13 00:00:11 2012
ARC3 started with pid=23, OS id=10842
ARC2: Archival started
ARC2: Becoming the 'no FAL' ARCH
ARC2: Becoming the 'no SRL' ARCH
ARC1: Becoming the heartbeat ARCH
Errors in file /u01/app/oracle/diag/rdbms/tssgd/TSSGD/trace/TSSGD_ora_10712.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 8388608000 bytes is 100.00% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
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.
************************************************************************
Errors in file /u01/app/oracle/diag/rdbms/tssgd/TSSGD/trace/TSSGD_ora_10712.trc:
ORA-19809: limit exceeded for recovery files
ORA-19804: cannot reclaim 46773248 bytes disk space from 8388608000 limit
ARCH: Error 19809 Creating archive log file to '/u01/app/oracle/flash_recovery_area/TSSGD/archivelog/2012_02_13/o1_mf_1_199_%u_.arc'
Errors in file /u01/app/oracle/diag/rdbms/tssgd/TSSGD/trace/TSSGD_ora_10712.trc:
ORA-16038: log 1 sequence# 199 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1: '/u02/oradata/TSSGD/redo01.log'
USER (ospid: 10712): terminating the instance due to error 16038
Instance terminated by USER, pid = 10712

just for the day I stop archive log and start the database for use.
But what I should do now to open database in archivelog mode.
Re: ORA-03113: end-of-file on communication channel [message #543088 is a reply to message #543074] Mon, 13 February 2012 02:03 Go to previous messageGo to next message
John Watson
Messages: 4690
Registered: January 2010
Location: Global Village
Senior Member
You say you have removed files from the fast recovery area, so now you have to tell Oracle that you have removed them. From an RMAN prompt:
crosscheck archivelog all;
crosscheck backupset;
crosscheck copy;
delete expired;

I would strongly advise you to shutdown your database immediately, put it back into archivelog mode, do the above, and perform a backup. Do this NOW! At the moment, you are vulnerable to loss of data, and for a DBA, this is more important that anything else. ANYTHING else.


Re: ORA-03113: end-of-file on communication channel [message #543130 is a reply to message #543088] Mon, 13 February 2012 03:22 Go to previous messageGo to next message
nehhaverma
Messages: 34
Registered: September 2009
Location: JAIPUR
Member
Hi
Thanks John. My database is working now in archive mode successfully. I follow all the steps given by you and my problem is solved now.
One more question is that I would like to configure my retention policy for 7 days. After 7 days all archives less then 7 days should be deleted.

What steps I do follow for that?

Regards//Neha
Re: ORA-03113: end-of-file on communication channel [message #543136 is a reply to message #543130] Mon, 13 February 2012 03:29 Go to previous message
John Watson
Messages: 4690
Registered: January 2010
Location: Global Village
Senior Member
Quote:
What steps I do follow for that?
Reading the manuals would be a good start Smile
Previous Topic: How to executea pro c script from Linux
Next Topic: text for all objects
Goto Forum:
  


Current Time: Fri Oct 24 09:44:42 CDT 2014

Total time taken to generate the page: 0.08602 seconds