Oracle error--ora-03113: File end solution for communication channel __oracle

Origin

Today as usual, landing pl/sql, the failure to login, there is an error "ORA-01034" and "ORA-27101" as shown:

Then you go to Oracle at the command prompt to see what's going on, and then the problem goes further, the error "ORA-03113: The end of the communication channel file process id:6320 reply id:191 serial number: 3".

The root of the problem

Oracle error, so go to the error log to find the source of the problem: in the E:\app\kang\diag\rdbms\oracle\oracle\trace\ folder to find the Oracle_ora_6320.trc file, open the display error log:

Trace filee:\app\kang\diag\rdbms\oracle\oracle\trace\oracle_ora_6320.trc Oracle Database 11gEnterprise Edition  Release 11.2.0.1.0-64bit Production with Thepartitioning, OLAP, Data Mining and real application testing options Windows NT VersionV6.1 Service Pack 1 cpu:4-type 8664, 2 physicalcores Process affinity:0x0x000000000000 
0000 Memory (Avail/total):P h:2805m/6087m, ph+pgf:6761m/12173m, Instance name:oracle thread Redo this Mountedby Oracle processnumber:19 Windows thread id:6320, image:oracle. EXE (Shad) * * * * 2014-08-1608:18:55.461 * * * SESSIONID: (191.3) 2014-08-16 08:18:55.461 * * CLIENT ID: () 2014-08-16 08:18:5 5.461 * * * * SERVICE Name: () 2014-08-16 08:18:55.461 modulename: (sqlplus.exe) 2014-08-16 08:18:55.461 * * ACTION Name: () 2
014-08-16 08:18:55.461 ORA-19815: Warning: db_recovery_file_dest_size byte (total 4102029312 bytes) has been used 100%, and 0 bytes are available. Have followingchoices to Free up spaces from recovery area:1. Consider Changingrman RETENTION POLICY.
If you are using Data Guard, then consider changing RMAN archivelogdeletion POLICY.
2. Back up the files totertiary device such as tape using RMAN BACKUP RECOVERY Area Command.
3. ADD disk andincrease db_recovery_file_dest_size parameter to reflect the new space. 4. Delete Unnecessaryfiles the Using RMAN Delete command.
If an operating system command is used to delete Files,then the use RMAN crosscheck and delete expired commands. ORA-19809: The limit for the number of recovered files is exceeded ORA-19804: Unable to reclaim 33961984 bytes of disk space (from 4102029312 limit) * * * 2014-08-1608:18:55.502 4132 krsh.c arch:error 19809Creating archive log file T O ' E:\APP\KANG\FLASH_RECOVERY_AREA\ORACLE\ARCHIVELOG\2014_08_16\O1_MF_1_159_%U_. ARC ' * * * 2014-08-1608:18:55.502 2747 krsi.c krsi_dst_fail:dest:1err:19809 force:0 blast:1 dde:problem Key ' ORA312 ' was F Lood controlled (0x1) (no incident) ORA-00312: Online logs3 thread 1: ' E:\APP\KANG\ORADATA\ORACLE\REDO03. Log ' ORA-16038:3sequence# 159 cannot be archived ORA-19809: exceeded the limit of the number of recovered files ORA-00312: Online log 3 thread 1: ' E:\APP\KANG\ORADATA\ORACLE\REDO03.LO G ' * * * * 2014-08-1608:18:55.565 USER (ospid:6320): Terminating the instance due to error 16038

From here we find the root of the problem: "

ORA-19815: Warning: db_recovery_file_dest_size byte (total 4102029312 bytes) has been used 100%, and 0 bytes are still available. "Is db_recovery_file_dest_size also called the Archive log space is not enough, since the root cause of the problem is found, it is easy to solve."

ways to solve

The space is small, that put in front of us the method is, one is to set the space big point, the other is to remove the superfluous files, then we will use both methods.

Through the command window:

--------set the size of the archive log space

Sqlplus/as sysdba
shutdown abort     ----shutdown process
startup mount       ----Mount Database
SELECT * FROM V$recovery_file_ Dest ---query archive log
db_recovery_file_dest_size=10737418240;--Set the archive log space to 10G
Exit---to where the space size has been set to complete

--------Delete an archive log

Rmantarget/   -----into the RMAN tool window
rman>crosscheckarchivelog all;  --run this command to mark the archivelog of the invalid expired.
rman>deletenoprompt Archivelog until Time "sysdate-3";  ---delete an archive log 3 days ago
 

It's completely OK to be here. Next, reopen the database: normal use.

One thing to note in deleting an archive is that the display archive is E:\app\kang\flash_recovery_area\oracle\ARCHIVELOG under the Command window, but we cannot manually delete the files directly from the operating system. This is because the information about each archivelog is recorded in the Controlfile, and when we delete the files in the OS, the Archivelog information is still recorded in our controlfile. Therefore, these logs will also exist in Oracle's OEM manager. Because when we manually clear the files in the archive directory, the records were not removed from the controlfile, which means Oracle did not know that the files were no longer there. So it's still a command window to execute the command to delete these files.

PostScript

Archive logs are actually designed to help us recover from the database, but sometimes these archived logs can actually give us a little bit of trouble, so these archive logs need our attention.