ORA-03113: end-of-file on communication channel on DB startup

 
ORA-03113 could be
signaled for any of these scenarios:

  •  Server machine crashed
  • Your server process was killed at O/S level
  •  Network problems
  •  Oracle internal errors / aborts on the server
  • Client incorrectly handling multiple connections

                
[oracle@RHEL ~]$ . rhel.env
[oracle@RHEL ~]$ sqlplus / as sysdba
sqlplus / as sysdba
SQL*Plus: Release 11.2.0.4.0 Production on Sat Aug 4 09:44:17 2018
Copyright (c) 1982, 2013, Oracle. 
All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 
626327552 bytes
Fixed Size                                  2255832 bytes
Variable Size                           234882088 bytes
Database Buffers    381681664 bytes
Redo Buffers                             7507968 bytes
Database mounted.
ORA-03113: end-of-file on communication channel

Process ID: 3727

Session ID: 125 Serial number: 5
We can use Automatic Diagnostic Repository (ADRCI)
OS
command:
[oracle@RHEL ~]$ adrci
ADRCI: Release 11.2.0.4.0 – Production on Sat Aug 4 09:46:57 2018
Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
ADR base = “/u01/app/oracle”
Show all Homes:
adrci> show homes
ADR Homes:
diag/rdbms/rhel3/RHEL3
diag/rdbms/actcl/ACTCL
diag/rdbms/rhel2/RHEL2
diag/rdbms/intercl/ITERCL
diag/rdbms/intercl/INTERCL
diag/rdbms/bkpcl/BKPCL
diag/rdbms/rhelext/RHELEXT
diag/clients/user_oracle/host_2186336506_80
diag/clients/user_oracle/host_1270808414_80
diag/tnslsnr/RHELEXT/intercl
diag/tnslsnr/RHELEXT/rhelext
diag/tnslsnr/RHEL/rhel3
diag/tnslsnr/RHEL/rhel
diag/tnslsnr/RHEL/actcl
diag/tnslsnr/RHEL/rhel2
diag/tnslsnr/RHEL/intercl
diag/tnslsnr/RHEL/bkpcl
Set the Alertlog File Home
Location
adrci> set home diag/rdbms/rhel3/RHEL3
Check the Alert Log File:
adrci> show alert -tail 100
2018-08-04 09:44:20.572000 +05:30
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.4.0 – 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application
Testing options.
ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_3
System name:Linux
Node name:RHEL.localhost.com
Release:2.6.32-431.el6.x86_64
Version:#1 SMP Sun Nov 10 22:19:54 EST 2013
Machine:x86_64
VM name:VMWare Version: 6
Using parameter settings in server-side spfile
/u01/app/oracle/product/11.2.0/dbhome_3/dbs/spfileRHEL3.ora
System parameters with non-default values:
  processes                = 150
  sga_target               = 600M
  control_files            = “/u01/app/oracle/control05.ctl”
  db_block_size            = 8192
  compatible               = “11.2.0.4.0”
  log_archive_format       = “%t_%s_%r.dbf”
  db_recovery_file_dest    =
“/u01/app/oracle/fast_recovery_area”
  db_recovery_file_dest_size=
4086M
  undo_tablespace          = “UNDOTBS1”
  remote_login_passwordfile=
“EXCLUSIVE”
  db_domain                = “”
  dispatchers              = “(PROTOCOL=TCP)
(SERVICE=RHEL3XDB)”
  shared_servers           = 5
  local_listener           = “LISTENER_RHEL3”
  audit_file_dest          =
“/u01/app/oracle/admin/RHEL3/adump”
  audit_trail              = “DB”
  db_name                  = “RHEL3”
  open_cursors             = 300
  pga_aggregate_target     = 199M
  diagnostic_dest          = “/u01/app/oracle”
PMON started with pid=2, OS id=3679
PSP0 started with pid=3, OS id=3681
2018-08-04 09:44:21.684000 +05:30
VKTM started with pid=4, OS id=3683 at elevated priority
GEN0 started with pid=5, OS id=3687
VKTM running at (1)millisec precision with DBRM quantum (100)ms
DIAG started with pid=6, OS id=3689
DBRM started with pid=7, OS id=3691
DIA0 started with pid=8, OS id=3693
MMAN started with pid=9, OS id=3695
DBW0 started with pid=10, OS id=3697
LGWR started with pid=11, OS id=3699
CKPT started with pid=12, OS id=3701
SMON started with pid=13, OS id=3703
RECO started with pid=14, OS id=3705
MMON started with pid=15, OS id=3707
MMNL started with pid=16, OS id=3709
starting up 1 dispatcher(s) for network address
‘(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))’…
starting up 5 shared server(s) …
ORACLE_BASE from environment = /u01/app/oracle
ALTER DATABASE   MOUNT
2018-08-04 09:44:25.929000 +05:30
Successful mount of redo thread 1, with mount id 1943908661
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE  
MOUNT
ALTER DATABASE OPEN
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=24, OS id=3729
2018-08-04 09:44:27.161000 +05:30
ARC0: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
ARC1 started with pid=25, OS id=3731
ARC2 started with pid=26, OS id=3733
ARC3 started with pid=27, OS id=3735
ARC1: Archival started
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/rhel3/RHEL3/trace/RHEL3_ora_3727.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 4284481536 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.
************************************************************************
ARCH: Error 19809 Creating archive log file to ‘/u01/app/oracle/fast_recovery_area/RHEL3/archivelog/2018_08_04/o1_mf_1_97_%u_.arc’
Errors in file
/u01/app/oracle/diag/rdbms/rhel3/RHEL3/trace/RHEL3_ora_3727.trc:
ORA-16038: log 1 sequence# 97 cannot be archived
ORA-19809: limit exceeded for recovery files
ORA-00312: online log 1 thread 1:
‘/u01/app/oracle/oradata/RHEL3/redo01.log’
USER (ospid: 3727): terminating the instance due to error 16038
System state dump requested by (instance=1, osid=3727),
summary=[abnormal instance termination].
System State dumped to trace file
/u01/app/oracle/diag/rdbms/rhel3/RHEL3/trace/RHEL3_diag_3689_20180804094427.trc
Dumping diagnostic data in directory=[cdmp_20180804094427],
requested by (instance=1, osid=3727), summary=[abnormal instance termination].
Instance terminated by USER, pid = 3727

 

SQL> startup nomount
ORACLE instance started.
Total System Global Area 
626327552 bytes
Fixed Size                                  2255832 bytes
Variable Size                           234882088 bytes
Database Buffers    381681664 bytes
Redo Buffers                             7507968 bytes
SQL> alter system set db_recovery_file_dest_size = 12G
scope=both;
System altered.
SQL> shut immediate
ORA-01507: database not mounted
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 
626327552 bytes
Fixed Size                                  2255832 bytes
Variable Size                           234882088 bytes
Database Buffers    381681664 bytes
Redo Buffers                             7507968 bytes
Database mounted.
Database opened.

  • October 4, 2018 | 109 views
  • Comments