Oracle error -- ORA-03113: file end solution for communication channel
Origin
Today as usual, login PL/SQL, indeed login failed, there is an error "ORA-01034" and "ORA-27101"
Then I log on to Oracle through the command prompt, to view what is going on, and then the problem further appears, the error "ORA-03113: communication channel file end process ID: 6320 session ID: 191 serial number: 3 ".
Root Cause
If an error occurs in Oracle, go to the error log to find the root cause: Find the oracle_ora_6320.trc file in the e: \ app \ kang \ diag \ rdbms \ oracle \ trace \ folder, open the error log:
Trace filee: \ app \ kang \ diag \ rdbms \ oracle \ trace \ oracle_ora_6320.trc
Oracle Database 11 gEnterprise 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: 0x0x0000000000000000
Memory (Avail/Total): Ph: 2805 M/6087 M, Ph + PgF: 6761 M/12173 M
Instance name: oracle
Redo thread mountedby this instance: 1
Oracle processnumber: 19
Windows thread id: 6320, image: ORACLE. EXE (SHAD)
* ** 2014-08-1608: 18: 55.461
* ** SESSIONID: (191.3) 08:18:55. 461
* ** Client id: () 08:18:55. 461
* ** Service name :() 08:18:55. 461
* ** MODULENAME :( sqlplus.exe) 08:18:55. 461
* ** Action name :() 08:18:55. 461
ORA-19815: Warning: db_recovery_file_dest_size bytes (4102029312 bytes in total) are 100.00% in use and 0 bytes are available.
**************************************** ********************************
You have followingchoices to free up space from recovery area:
1. Consider changingRMAN retention policy. If you are using Data Guard,
Then consider changing rman archivelogdeletion policy.
2. Back up files totertiary device such as tape using RMAN
Backup recovery area command.
3. Add disk space andincrease db_recovery_file_dest_size parameter
Reflect the new space.
4. Delete unnecessaryfiles using rman delete command. If an operating
System command was used to delete files, then use rman crosscheck and
Delete expired commands.
**************************************** ********************************
ORA-19809: exceeds the limit on the number of recovery files
ORA-19804: unable to reclaim 33961984 bytes of disk space (from 4102029312 limit)
* ** 2014-08-1608: 18: 55.502 4132 krsh. c
ARCH: Error 19809 Creating archive log file to '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 flood controlled (0x1) (no incident)
ORA-00312: Online log 3 thread 1: 'e: \ APP \ KANG \ ORADATA \ ORACLE \ redo03.log'
ORA-16038: log 3 sequence #159 cannot be archived
ORA-19809: exceeds the limit on the number of recovery files
ORA-00312: Online log 3 thread 1: 'e: \ APP \ KANG \ ORADATA \ ORACLE \ redo03.log'
* ** 2014-08-1608: 18: 55.565
USER (ospid: 6320): terminating the instance due to error 16038
Here we find the root cause of the problem:"
ORA-19815: Warning: db_recovery_file_dest_size bytes (4102029312 bytes in total) are 100.00% in use and 0 bytes are available ." Db_recovery_file_dest_size is also caused by insufficient archive log space. It is easy to solve the problem by finding the root cause.
For more details, please continue to read the highlights on the next page: