Technical data

Application is slow
2-10 Oracle TimesTen In-Memory Database Troubleshooting Procedures Guide
This section describes what to check if your application unexpectedly disconnects
from the data store.
Check for ODBC or JDBC errors
Check for the following types of errors:
■ ODBC errors returned by the SQLError function
■ JDBC errors returned by the SQLException class
The application may have encountered a problem that caused it to exit prematurely,
which in turn may have caused other connections to be forced to disconnect. Call
SQLError after each ODBC call to identify error or warning conditions when they
first happen. Examples of SQLError usage can be found in the demo programs and in
"Retrieving errors and warnings" in the Oracle TimesTen In-Memory Database Error
Messages and SNMP Traps.
In more extreme cases, it may be helpful to use ttTraceMon to generate a level 4 ERR
trace for the application and review all of the errors messages that are pushed in the
TimesTen direct driver. See "ERR tracing" on page 1-13 for details.
Check the user error log
If a TimesTen application disconnects without returning an ODBC error or any other
warning, look through the user error log. See "Using the logs generated by the
TimesTen daemon" on page 1-6.
Application is slow
For details on how to maximize the performance of your application and TimesTen
data store, see:
■ "TimesTen Database Performance Tuning" in the Oracle TimesTen In-Memory
Database Operations Guide
■ "Application Tuning" in the Oracle TimesTen In-Memory Database C Developer's
Guide
■ "Application Tuning" in the Oracle TimesTen In-Memory Database Java Developer's
Guide
This section describes some of the issues that impair performance.
Possible cause See...
Internal application error. "Check for ODBC or JDBC errors" on page 2-10
Failure of a concurrent application
thread.
"Check for ODBC or JDBC errors" on page 2-10
"Check the user error log" on page 2-10
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 Technical support.
Possible cause See...
Using client/server mode "Consider connection mode" on page 2-11
Outdated database statistics "Update statistics for your tables" on page 2-11