Download TimesTen Troubleshooting Guide

Application is disconnected unexpectedly
Application is disconnected unexpectedly
If an application becomes disconnected from a TimesTen database, one of the
following events occurs:
■
■
If there was no outstanding transaction, the connection is cleanly removed by the
TimesTen daemon. Other existing connections continue processing as if no
problem had occurred.
If there was an outstanding transaction, the transaction is rolled back and the
connection is cleanly removed by the TimesTen daemon. Other existing
connections continue processing as if no problem had occurred.
This section describes what to check if your application unexpectedly disconnects
from the database.
Possible cause
See...
Internal application error.
"Check for ODBC, JDBC, OCI, Pro*C, and PL/SQL
application errors" on page 2-10
Failure of a concurrent application
thread.
"Check for ODBC, JDBC, OCI, Pro*C, and PL/SQL
application errors" on page 2-10
"Check the user error log" on page 2-11
If using a client/server connection,
the client may have disconnected
from the application.
"Troubleshooting Client/Server problems" on page 2-6
An error in the TimesTen library
Contact TimesTen technical support.
Check for ODBC, JDBC, OCI, Pro*C, and PL/SQL application errors
Check for the following types of errors:
■
ODBC errors returned by the SQLError function
■
JDBC errors returned by the SQLException class
TimesTen OCI and Pro*C applications, and those that use PL/SQL, report errors using
Oracle database error codes instead of TimesTen error codes. The error messages that
accompany the error codes may come from the TimesTen error catalog or the Oracle
database error catalog.
By default, TimesTen messages and diagnostic information are stored in:
■
■
■
A user error log that contains error message information. Generally, these
messages contain information on actions you may need to take. The default file is
daemon_home/tterrors.log. For more information on modifying the location of
the user error log, see "Modifying informational messages" in the Oracle TimesTen
In-Memory Database Reference.
A support log containing everything in the user error log plus information of use
by TimesTen technical support. The default file is daemon_home/ttmesg.log. For
more information on modifying the location of the user error log, see "Modifying
informational messages" in the Oracle TimesTen In-Memory Database Reference.
An invalidation file containing diagnostic information when TimesTen invalidates
a database. This file provides useful troubleshooting information for TimesTen
technical support. The invalidation file is created and named based on the value
specified by the DataStore connection attribute. This connection attribute is not a
file name. For example on Linux platforms, if the DataStore connection attribute is
/home/ttuser/AdminData, the actual invalidation file name has a suffix, .inval,
2-10 Oracle TimesTen In-Memory Database Troubleshooting Guide