I've searched through the net and also this newsgroup about this particular
error, but haven't come to a conclusion as to where the problem resides. Our
app issues a SELECT query based on the user input and displays (and
generates) the search result as a online/downloadable report form.
Here's the stack trace of the error:
ORA-03113: end-of-file on communication channel
java.sql.SQLException: ORA-03113: end-of-file on communication channel
at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:251)
at weblogic.jdbc.oci.Statement.execute(Statement.java:531)
at weblogic.jdbc.pool.Statement.execute(Statement.java:216)
at
weblogic.jdbc.rmi.internal.StatementImpl.execute(StatementImpl.java:2
08)
at
weblogic.jdbc.rmi.SerialStatement.execute(SerialStatement.java:309)
at
com.hoike.punahou.reports.StudentRecordReports.getStudentIDsFromDB(St
udentRecordReports.java:885)
at
com.hoike.punahou.reports.StudentRecordReports.generateReport(Student
RecordReports.java:608)
at
com.hoike.punahou.reports.StudentRecordReports.onClickGenerateReport(
StudentRecordReports.java:390)
at java.lang.reflect.Method.invoke(Native Method)
at
com.documentum.web.form.FormProcessor.invokeMethod(FormProcessor.java
:878)
at
com.documentum.web.form.FormProcessor.fireActionEvent(FormProcessor.j
ava:606)
at
com.documentum.web.form.RecallOperation.execute(RecallOperation.java:
98)
at
com.documentum.web.form.FormProcessor.openForm(FormProcessor.java:151
)
at
com.documentum.web.form.WebformTag.doStartTag(WebformTag.java:124)
at
jsp_servlet._custom._reports.__studentrecord_reports._jspService(__st
udentrecord_reports.java:174)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1058)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:401)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:306)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:5412)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
eManager.java:744)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3086)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2544)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)
When I check the sqlnet.log, I don't see ORA-03113 error. But I see
TNS-12600 and TNS-5300 error with secondary code 126. I'm not sure if these
two are related to ORA-03113 error displayed in the console.
Here is a sniplet from sqlnet.log:
Fatal NI connect error 12560, connecting to:
(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCL)(ARGS=
'(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=ORCL
)(CID=(PROGRAM=C:\bea\jdk131_03\bin\java.exe)(HOST=HDMAPP3)(USER=Administrat
or))))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 8.1.7.0.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.1.7.0.0 -
Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version
8.1.7.0.0 - Production
Time: 13-AUG-2003 13:11:49
Tracing not turned on.
Tns error struct:
nr err code: 0
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 530
TNS-00530: Protocol adapter error
nt secondary err code: 126
nt OS err code: 0
Our DBA says MTS is not enabled. I also made sure that the
java.sql.Connection and java.sql.ResultSet objects are closed as soon as
they are no longer needed. We're using WLS 7.0 SP2 with Oracle 8.1.7, with
jDriver for Oracle (and Oracle 8i client).
Does anyone have any insight to where the cause of this problem be? and if
the errors (ORA-03113 and TNS errors) are related at all?
Thank you very much!
Makoto
Makoto Suzuki wrote:
> Hello everyone,
>
> I've searched through the net and also this newsgroup about this particular
> error, but haven't come to a conclusion as to where the problem resides. Our
> app issues a SELECT query based on the user input and displays (and
> generates) the search result as a online/downloadable report form.
>
> Here's the stack trace of the error:
>
> ORA-03113: end-of-file on communication channel
>
> java.sql.SQLException: ORA-03113: end-of-file on communication channel
Hi. This looks to be a problem with a mismatch between the JDBC driver version and the
DBMS. You should download the latest thin driver that they recommend for the DBMS
version you have, and put the zip file where it will be put in front of all the official
weblogic stuff in the server's classpath.
Joe
Thanks,
Mitesh
Thanks for your insight - how do I turn on the tracing? Do I do that on
Oracle client side, or on the jDriver?
Thanks!
Makoto
"Mitesh Patel" <Mitesh...@bea.com> wrote in message
news:3F3B9653...@bea.com...
Thanks for your input - I'm using the jDriver for Oracle 8.1.7 with Oracle
8.1.7. is there any other components whose version I should check? The path
to jDriver shared library (oci817_8) and to %ORACLE_HOME%\bin are put at the
beginning of the path, which is prepended by c:\bea7\weblogic700\server\bin
and c:\bea7\jdk131_03\bin by the startWLS.cmd.
Thank you,
Makoto
Mitesh
Makoto Suzuki wrote:
> Hi Joe,
>
> Thanks for your input - I'm using the jDriver for Oracle 8.1.7 with Oracle
> 8.1.7. is there any other components whose version I should check? The path
> to jDriver shared library (oci817_8) and to %ORACLE_HOME%\bin are put at the
> beginning of the path, which is prepended by c:\bea7\weblogic700\server\bin
> and c:\bea7\jdk131_03\bin by the startWLS.cmd.
Hmmmmm.... That sounds right. Does Oracle have older and newer versions
of 8.1.7 or is that as small an update as oracle does?
From the original stacktrace, it seems you're simply executing a statement. Can
you trry using the oracle thin driver, and see if the same thing happens?
thanks,
Joe