Error: ORA 3113
Text: end-of-file on communication channel
-------------------------------------------------------------------------------
Cause: 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
network or server machine went down.
Action: If this message occurs during a connection attempt, check the setup
files for the appropriate SQL*net driver and confirm SQL*Net software
is correctly installed on the server. If the message occurs after a
connection is well established, and the error is not due to a physical
failure, check if a trace file was generated on the server at failure
time. Existence of a trace file may suggest an Oracle internal error
that requires the assistance of customer support.
*** Important: The notes below are for experienced users - See Note:22080.1
Explanation:
There are numerous causes of this error. It is a 'catch all' type
error which means 'I cannot communicate with the oracle shadow process'.
This usually occurs when the Oracle server process has died for
some reason.
Diagnosis:
Oracle support need more information to determine what caused the
error. The most useful items are:
1) Does this occur when trying to (a) make a connection to the
database or (b) on an established connection ?
2) There should be a trace file from the failed session in
USER_DUMP_DEST
3) Does a particular statement reproduce this problem or is it
random ? Use SQL_TRACE on the session to find the problem
statement.
Articles:
ORA-3113 on Unix - What Information to Collect Note:17613.1
Text: end-of-file on communication channel
-------------------------------------------------------------------------------
Cause: 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
network or server machine went down.
Action: If this message occurs during a connection attempt, check the setup
files for the appropriate SQL*net driver and confirm SQL*Net software
is correctly installed on the server. If the message occurs after a
connection is well established, and the error is not due to a physical
failure, check if a trace file was generated on the server at failure
time. Existence of a trace file may suggest an Oracle internal error
that requires the assistance of customer support.
*** Important: The notes below are for experienced users - See Note:22080.1
Explanation:
There are numerous causes of this error. It is a 'catch all' type
error which means 'I cannot communicate with the oracle shadow process'.
This usually occurs when the Oracle server process has died for
some reason.
Diagnosis:
Oracle support need more information to determine what caused the
error. The most useful items are:
1) Does this occur when trying to (a) make a connection to the
database or (b) on an established connection ?
2) There should be a trace file from the failed session in
USER_DUMP_DEST
3) Does a particular statement reproduce this problem or is it
random ? Use SQL_TRACE on the session to find the problem
statement.
Articles:
ORA-3113 on Unix - What Information to Collect Note:17613.1
'Database > ORA-ERR' 카테고리의 다른 글
| ORA-39142 덤프 버전이 틀려서 넣지 못할 때 (0) | 2011.01.06 |
|---|---|
| ORA-02049 : 시간초과 : 분산 트랜잭션이 잠금으로 대기중입니다. (0) | 2011.01.04 |
| Oracle Corrupt (0) | 2010.09.20 |
| OERR: ORA 2068 following severe error from [ID 19350.1] (0) | 2010.06.03 |
