Oracle error -- ORA-03113: file end solution for communication channel, oracleora-03113

Source: Internet
Author: User

Oracle error -- ORA-03113: file end solution for communication channel, oracleora-03113

 

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.trcOracle Database 11 gEnterprise Edition Release 11.2.0.1.0-64bit ProductionWith thePartitioning, OLAP, data Mining and Real Application Testing optionsWindows NT VersionV6.1 Service Pack 1CPU: 4-type 8664, 2 PhysicalCoresProcess Affinity: 0x0x0000000000000000Memory (Avail/Total): Ph: 2805 M/6087 M, ph + PgF: 6761 Mbit/s/12173 MInstance n Ame: oracleRedo 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_d Est_size bytes (4102029312 bytes in total) already use 100.00%, 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 stored POLICY.2. Back up files totertiary device such as tape using rman backup recovery area command.3. Add disk space andincrease specified parameter to 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: ORA-19804: unable to reclaim 33961984 bytes disk space (from 4102029312 limit) *** 2014-08-1608: 18: 55.502 4132 krsh. cARCH: 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. ckrsi_dst_fail: dest: 1err: 19809 force: 0 blast: 1DDE: 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 unable to archive ORA-19809: ORA-00312 beyond the limit on the number of recovery files: 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.

 

Solution

 

If the space is small, the solution is to increase the size of the space and delete unnecessary files. Then we can use both methods.

 

In the command window:

-------- Set the size of the archive log Space

Sqlplus/as sysdbashutdown abort ---- close the process startup mount ---- load the database select * from v $ recovery_file_dest; --- query the archive log db_recovery_file_dest_size = 10737418240; -- set the archive log space to 10 GExit --- the space size has been set here


 

-------- Delete archived logs

Rmantarget/----- enter the rman tool window RMAN> crosscheckarchivelog all; -- run this command to mark the invalid expired archivelog. RMAN> deletenoprompt archivelog until time "sysdate-3"; -- deletes the archived logs three days ago.


This is the complete OK. Next, open the database again: normal use.

 

Note that the command window shows that all the archive files are under E: \ app \ kang \ flash_recovery_area \ oracle \ ARCHIVELOG, however, we cannot manually delete these files in the operating system. This is because the controlfile records information about each archivelog. When we delete these files in the OS, the archivelog information is still recorded in our controlfile, so these logs still exist in the Oracle OEM manager. Because after we manually clear the files in the archive directory, these records are not cleared from the controlfile, that is, oracle does not know that these files do not exist. Therefore, you still need to execute the command to delete these files through the command window.

 

Postscript

 

Archive logs are used to facilitate database recovery, but sometimes these archive logs may cause us a little trouble. Therefore, we need to pay attention to these archive logs.


Oracle Database, startup error "ora-03113, communication channel file end", help such as can solve, add wealth Value

1. What is the environment and operating system? Oracle version
2. Please post the log corresponding to the time in alert
3. This may be a bug or a parameter issue.
4. Only said ora-03113 error, it is difficult to diagnose Ah ~

Oracle database connection problems: ORA-03113: communication channel file end process ID: 5272 session ID: 191 serial number: 3

Insufficient information to provide suggestions
What version is the database?

Startup mount
Show parameter background_dump_dest
If the version is 10 Gb or above
Select name, value from v $ diag_info where name = 'diag Trace ';
Find alert_SID.log from the directory obtained in the previous step.
Open the log file and paste the last 20 lines.


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.