This error can occur due to different problems.
Therefore check alert log file.
Hello, I will mention my problem.And we will try solve this problem together.
i have oracle 11 gR2 standalone database in Oracle linux OS. After I have rebooted the OS i can' t access my database .
Oracle database is starting in mount mode but it cant start open mode.
The following error message below in this mode:
ORA-03113: end-of-file on communication channel
I checked my alert
log Through OS text editor program. Online redo log files and their mirrors
in differ paths. The Database is in archive mode and online log file 3 can’ t archieved.
For solve this problem we will use PITR( Point in time
recovery) method via RMAN. I m not use
Catalog database.
Ok. We are connecting to RMAN below:
rman target /
RMAN>
We are checking
valid the recoverable backups.
RMAN> list backup
recoverable;
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------
---------------
22 Full 9.36M
DISK 00:00:04 01-MAY-12
BP Key: 22 Status: AVAILABLE Compressed: NO Tag: TAG20120501T001147
Piece Name:
+XFRA/xdb/autobackup/2012_05_01/s_782093507.299.782093509
SPFILE Included:
Modification time: 30-APR-12
SPFILE db_unique_name:
XDB
Control File Included: Ckp SCN:
1222523 Ckp time: 01-MAY-12
I signed that SCN is 1222523 when backup have been taken. I will
use this scn number.
I will Run command in RMAN
tool. You can execute more lines at one
time between Run {} command .
Finally, the folowing below:
If you want set until
time <date> inside of until scn .
I prefer Scn number.
RMAN> run {
2> set until scn 1222523;
3> restore database;
4> recover database;
5> }
channel ORA_DISK_1: restoring datafile 00001 to u01/app/oracle/oradata/XDB/datafile/system01.
dbf
channel ORA_DISK_1: restoring datafile 00002 to
/u01/app/oracle/oradata/XDB/datafile/sysaux01.
dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/XDB/datafile/undotbs01
.dbf
channel ORA_DISK_1: restoring datafile 00004 to
/u01/app/oracle/oradata/XDB/datafile/users01.d bf
channel ORA_DISK_1: reading from backup piece
+XFRA/xdb/backupset/2012_02_04/nnndn0_tag2012020
4t232950_0.275.774401393
channel ORA_DISK_1: piece handle=+XFRA/xdb/backupset/2012_02_04/nnndn0_tag20120204t232950_0.27
5.774401393 tag=TAG20120204T232950
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:03:04
Finished restore at 13-JUN-12
Starting recover at 13-JUN-12
using channel ORA_DISK_1
starting media recovery
archived log for thread 1 with sequence 1 is already on disk as
file +XFRA/xdb/archivelog/2012 _02_04/thread_1_seq_1.277.774402255
archived log for thread 1 with sequence 2 is already on disk as
file +XFRA/xdb/archivelog/2012
_02_04/thread_1_seq_2.278.774402273
archived log for thread 1 with sequence 3 is already on disk as
file +XFRA/xdb/archivelog/2012
_02_04/thread_1_seq_3.279.774402285
archived log for thread 1 with sequence 4 is already on disk as
file +XFRA/xdb/archivelog/2012
_02_05/thread_1_seq_4.281.774485121
archived log for thread 1 with sequence 5 is already on disk as
file +XFRA/xdb/archivelog/2012
_02_11/thread_1_seq_5.282.774986479
archived log for thread 1 with sequence 6 is already on disk as
file +XFRA/xdb/archivelog/2012 _02_11/thread_1_seq_6.283.774986847
archived log for thread 1 with sequence 7 is already on disk as
file +XFRA/xdb/archivelog/2012
_02_19/thread_1_seq_7.284.775694209
archived log for thread 1 with sequence 8 is already on disk as
file +XFRA/xdb/archivelog/2012
_02_27/thread_1_seq_8.288.776307623
archived log for thread 1 with sequence 9 is already on disk as
file +XFRA/xdb/archivelog/2012
_03_12/thread_1_seq_9.289.777764633
archived log for thread 1 with sequence 10 is already on disk as
file +XFRA/xdb/archivelog/201
2_03_12/thread_1_seq_10.290.777766019
archived log for thread 1 with sequence 11 is already on disk as
file +XFRA/xdb/archivelog/201 2_03_17/thread_1_seq_11.291.778189273
archived log for thread 1 with sequence 12 is already on disk as
file +XFRA/xdb/archivelog/201
2_03_17/thread_1_seq_12.292.778194849
archived log for thread 1 with sequence 13 is already on disk as
file +XFRA/xdb/archivelog/201
2_03_17/thread_1_seq_13.293.778195573
archived log for thread 1 with sequence 14 is already on disk as
file +XFRA/xdb/archivelog/201
2_03_17/thread_1_seq_14.294.778196007
archived log for thread 1 with sequence 15 is already on disk as
file +XFRA/xdb/archivelog/201
2_03_24/thread_1_seq_15.295.778788259
archived log for thread 1 with sequence 16 is already on disk as
file +XFRA/xdb/archivelog/201 2_03_25/thread_1_seq_16.296.778810005
archived log for thread 1 with sequence 17 is already on disk as
file +XFRA/xdb/archivelog/201
2_04_05/thread_1_seq_17.297.779829497
archived log for thread 1 with sequence 18 is already on disk as
file +XFRA/xdb/archivelog/201
2_04_08/thread_1_seq_18.298.780101645
archived log for thread 1 with sequence 19 is already on disk as
file +XFRA/xdb/archivelog/201
2_04_09/thread_1_seq_19.257.780105631
archived log for thread 1 with sequence 20 is already on disk as
file +XFRA/xdb/archivelog/201
2_04_30/thread_1_seq_20.256.782004437
archived log file
name=+XFRA/xdb/archivelog/2012_02_04/thread_1_seq_1.277.774402255 thread=1
s equence=1
archived log file
name=+XFRA/xdb/archivelog/2012_02_04/thread_1_seq_2.278.774402273 thread=1
s
equence=2
archived log file name=+XFRA/xdb/archivelog/2012_02_04/thread_1_seq_3.279.774402285
thread=1 s
equence=3
archived log file
name=+XFRA/xdb/archivelog/2012_02_05/thread_1_seq_4.281.774485121 thread=1
s equence=4
archived log file
name=+XFRA/xdb/archivelog/2012_02_11/thread_1_seq_5.282.774986479 thread=1
sequence=5
archived log file
name=+XFRA/xdb/archivelog/2012_02_11/thread_1_seq_6.283.774986847 thread=1
sequence=6
archived log file
name=+XFRA/xdb/archivelog/2012_02_19/thread_1_seq_7.284.775694209 thread=1
sequence=7
archived log file
name=+XFRA/xdb/archivelog/2012_02_27/thread_1_seq_8.288.776307623 thread=1
sequence=8
archived log file
name=+XFRA/xdb/archivelog/2012_03_12/thread_1_seq_9.289.777764633 thread=1
sequence=9
archived log file
name=+XFRA/xdb/archivelog/2012_03_12/thread_1_seq_10.290.777766019 thread=1
sequence=10
archived log file name=+XFRA/xdb/archivelog/2012_03_17/thread_1_seq_11.291.778189273
thread=1 sequence=11
archived log file
name=+XFRA/xdb/archivelog/2012_03_17/thread_1_seq_12.292.778194849 thread=1
sequence=12
archived log file
name=+XFRA/xdb/archivelog/2012_03_17/thread_1_seq_13.293.778195573 thread=1
sequence=13
archived log file
name=+XFRA/xdb/archivelog/2012_03_17/thread_1_seq_14.294.778196007 thread=1
sequence=14
archived log file
name=+XFRA/xdb/archivelog/2012_03_24/thread_1_seq_15.295.778788259 thread=1
sequence=15
archived log file name=+XFRA/xdb/archivelog/2012_03_25/thread_1_seq_16.296.778810005
thread=1 sequence=16
archived log file
name=+XFRA/xdb/archivelog/2012_04_05/thread_1_seq_17.297.779829497 thread=1
sequence=17
archived log file
name=+XFRA/xdb/archivelog/2012_04_08/thread_1_seq_18.298.780101645 thread=1
sequence=18
archived log file
name=+XFRA/xdb/archivelog/2012_04_09/thread_1_seq_19.257.780105631 thread=1
sequence=19
archived log file
name=+XFRA/xdb/archivelog/2012_04_30/thread_1_seq_20.256.782004437 thread=1
sequence=20
media recovery complete, elapsed time: 00:04:33
Finished recover at 13-JUN-12
As without problem finished
recover process We are opening database
open with resetlogs Because using resetlogs parameter, log number
reset and starting 1 number.
RMAN> alter database open resetlogs;
database opened
Muhammet,
YanıtlaSilthe error message from your blog post indicates that archiver is unable
to archive(create archive log file) online redo log file and all redo group are full
and actually you don't have to perform any recovery
just check for free space at the LOG_ARCHIVE_DEST location
and may be increase DB_RECOVERY_FILE_DEST_SIZE
additionally you may delete some old files from FRA or LAD in MOUNT state
Thank you for your attention.Yes i solved this problem. When I've already noticed this case and I've published "FRA exhaused" title a article.
YanıtlaSil