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

Source: Internet
Author: User

1. An error is reported when Oracle is started.

SQL> startup

Error:

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

View the alert. log File and find

ORA-03113: end-of-file on communication channel
Cannot reclaim 45680128 bytes disk space from 2147483648 limit
ARCH: Error 19809 Creating archive log file to '/u01/flash_recovery_area/ORCL/archivelog/2014_01_17/o1_mf_1_6 _ % u _. arc'


This is because the archive tablespace is full and cannot be allocated.

Solution: Open the database to the mount mode and delete the files to be discarded:

RMAN> startup nomount;

Oracle instance started

Total System Global Area 835104768 bytes

Fixed Size 2217952 bytes
Variable Size 587204640 bytes
Database Buffers 243269632 bytes
Redo Buffers 2412544 bytes

RMAN> resotre spfile from autobackup;

RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "advise, allocate, alter, backup, @, catalog, change, configure, connect, convert, copy, create, crosscheck, delete, drop, duplicate, exit, flashback, grant, host, import, list, mount, open, print, quit, recover, register, release, repair, replace, report, reset, restore, resync, revoke, run, send, set, show, shutdown, spool, SQL, startup, switch, transport, unregister, upgrade, validate ,{,"
RMAN-01008: the bad identifier was: resotre
RMAN-01007: at line 1 column 1 file: standard input

RMAN> alter database mount;

Database mounted

RMAN> delete obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 1 days
Allocated channel: ORA_DISK_1
Channel ORA_DISK_1: SID = 19 device type = DISK
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
----------------------------------------------------------------
Backup Set 2 27-DEC-13
Backup Piece 2 27-DEC-13/u01/flash_recovery_area/ORCL/backupset/2013_12_27/o1_mf_nnndf_TAG20131227T172528_9cwb48k0 _. bkp
Archive Log 2 27-DEC-13/u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_7_9cwq8sbj _. arc
Backup Set 1 27-DEC-13
Backup Piece 1 27-DEC-13/u01/flash_recovery_area/ORCL/backupset/2013_12_27/o1_mf_ncsnf_TAG20131227T172528_9cwb7lrp _. bkp
Archive Log 1 27-DEC-13/u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_6_9cwq0xm1 _. arc
Archive Log 3 27-DEC-13/u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_5_9cwm7cv6 _. arc

Do you really want to delete the above objects (enter YES or NO )? Yes
Deleted backup piece
Backup piece handle =/u01/flash_recovery_area/ORCL/backupset/2013_12_27/o1_mf_nnndf_TAG20131227T172528_9cwb48k0 _. bkp RECID = 2 STAMP = 835306248
Deleted archived log
Archived log file name =/u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_rj7_9cwq8sbj _. arc RECID = 2 STAMP = 835306247
Deleted backup piece
Backup piece handle =/u01/flash_recovery_area/ORCL/backupset/2013_12_27/o1_mf_ncsnf_TAG20131227T172528_9cwb7lrp _. bkp RECID = 1 STAMP = 835306248
Deleted archived log
Archived log file name =/u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_1_6_9cwq0xm1 _. arc RECID = 1 STAMP = 835306247
Deleted archived log
Archived log file name =/u01/flash_recovery_area/ORCL/archivelog/2013_12_27/o1_mf_rj5_9cwm7cv6 _. arc RECID = 3 STAMP = 835306247
Deleted 5 objects


RMAN> alter datatbase open;

ORA-00600 [2662] troubleshooting

Troubleshooting for ORA-01078 and LRM-00109

Notes on ORA-00471 Processing Methods

ORA-00314, redolog corruption, or missing Handling Methods

Solution to ORA-00257 archive logs being too large to store

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.