Ora-03113 End-of-file On Communication Channel Fix
Just guessing but I suspect that there is a timeout rule on the SAS - Oracle communications channel / port, possibly caused by a firewall around your SAS or Oracle server. I suggest you check with your SAS administrators or your IT network specialists to get them to check this out. An unexpected end-of-file was processed on the communication channel. The problem could not be handled by the SQL.Net, two task, software. This message could occur if the shadow two-task process associated with a SQL.Net connect has terminated abnormally, or if there is a physical failure of the interprocess communication vehicle, that is, the.
One of the lesser used features in an application using Oracle Database installed on a UNIX server stopped working recently throwing the ORA-03113 error.
Dear All,Actually i have upgraded from SAP 4.7 to ECC 6 ondemo server with hostname 'bssltests' but now i want to do a full system copy on a new server.OS - Sun Solaris 10Oracle - 10.2But now after full system replica.its giving me below error in Oracle startup.SQL connect /as sysdbaConnected to an idle instance.SQL startupORACLE instance started.Total System Global Area bytesFixed Size 2029624 bytesVariable Size bytesDatabase Buffers bytesRedo Buffers 14745600 bytesDatabase mounted.ORA-03113: end-of-file on communication channel.PLEASE HELP ME on how to resolve this error. Everythinsg is ok on current demo server but error is coming on new systemIf you need anymore details then pls tell me.Regards & Thanks,Ankita.
End Of File On Communication Channel
There is a DB corruption.619172 - ORA-03113 on entering the NOMOUNT phase370278 - ORA-3113 when starting SQLPLUS or SVRMGRLThe ora 3113 means,that the client process got disconnected from itsequivalent shadow process. It could be caused by:-Network problems which lead the connection to break, which you'vealready checked.-The shadow process got killed for any reason.-The statement that is executed is running into a resource problem whenbeing executed or when the optimal execution plan is found this might bcaused by a incorrect parameter setting.-The table, on which you are having the problem is having corruptions.-There is a bug in the oracle-release you are currently running on.335199 check this note as well.Please post all ur trace files to look at the issue more deeply.ThanksSubbu.