My Oracle Support Banner

ORA-03113 ORA-03114 from Control Center (Doc ID 332087.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Lite - Version 5.0.2.10.0 to 5.0.2.10.0
Information in this document applies to any platform.
Information in this document applies to any platform.
Using Oracle9i Application Server with Oracle9i Lite Mobile Server and a DMZ or Firewall may cause this issue.
Checked for relevance on 13-Nov-2007

Purpose

The purpose is to help users determine what is causing an ORA-03113 and ORA-03114 User logs into URL running Mobile Server and goes into Control Center.  After a period of time(1 hour) the user comes back to use Control Center.  The user will receive a runtimeException: ORA-03114 : not connected to ORACLE message.  

The servertrace_sys1.log, will display: 
Servlet oracle.lite.web.admin.console.ConsoleLoader
log1: Creating a new session
log9: ORA-03113 : end-of-file on communication channel
log9: java.lang.RuntimeException: ORA-03114 : not connected to ORACLE
log9: at oracle.lite.web.JupUserAuthenticate.isSystem(JupUserAuthenticate.java:132)
log9: at oracle.lite.web.admin.console.ConsoleLoader.service(ConsoleLoader.java:41)
log9: at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
log9: at oracle.lite.web.JupServlet.service(JupServlet.java:235)
log9: at oracle.lite.web.AppServletHandler.handle(AppServletHandler.java:279)
log9: at oracle.lite.web.JupApplication.service(JupApplication.java:536)
log9: at oracle.lite.web.JupHandler.handle(JupHandler.java:102)
log9: at oracle.lite.web.HTTPServer.process(HTTPServer.java:309)
log9: at oracle.lite.web.HTTPServer.handleRequest(HTTPServer.java:162)
log9: at oracle.lite.web.JupServer.handle(JupServer.java:308)
log1: request path /admin/console/loader
log1: String is /admin
log1: Did not find exception error page
log1: ID: <ID>
log9: handler:/admin/console/loader /admin/console
log1: Servlet oracle.lite.web.admin.console.ConsoleLoader
log9: ORA-03114 : not connected to ORACLE
log9: java.lang.RuntimeException: ORA-03114 : not connected to ORACLE
log9: at oracle.lite.web.JupUserAuthenticate.isSystem(JupUserAuthenticate.java:132)
log9: at oracle.lite.web.admin.console.ConsoleLoader.service(ConsoleLoader.java:41)
log9: at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
log9: at oracle.lite.web.JupServlet.service(JupServlet.java:235)
log9: at oracle.lite.web.AppServletHandler.handle(AppServletHandler.java:279)
log9: at oracle.lite.web.JupApplication.service(JupApplication.java:536)
log9: at oracle.lite.web.JupHandler.handle(JupHandler.java:102)
log9: at oracle.lite.web.HTTPServer.process(HTTPServer.java:309)
log9: at oracle.lite.web.HTTPServer.handleRequest(HTTPServer.java:162)
log9: at oracle.lite.web.JupServer.handle(JupServer.java:308)
log1: request path /admin/console/loader
log1: String is /admin
log1: Did not find exception error page

Scope

The database alert log and trace files will not report this error.  Users should turn on tracing in the Control Center after restarting the application server to establish a new connection.  The trace files will generated and then after a period of time (61 Minutes) you should try to re-enter the Control Center to receive the error.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.