Technical data

Application becomes disconnected unexpectedly
Troubleshooting TimesTen Applications and Data Stores 2-9
Increasing the server stack size decreases the number of concurrent connections that
can be made before running out of swap space.
See "Working with the TimesTen Client and Server" in the Oracle TimesTen In-Memory
Database Operations Guide.
Out of space when DSN specifies new data store
You may receive "out of space" messages if you change a DSN to specify a new data
store while there are existing connections to the original data store in a system with
multiple client connections. This can happen on 32-bit platforms if either data store is
close to 2 GB.
Close all connections to the original data store. This causes a new server process to be
created for connections to the data store that is now specified in the DSN. Use the
ttStatus utility to list the connections for the old data store. Alternatively, you can
restart the server by using the ttDaemonAdmin utility with the -restartServer
option, which resets all client connections on all DSNs in the instance.
Application connects or disconnects are slow
This section describes what to check if you encounter slow connects and disconnects to
a data store.
Check if data store is being recovered
A slow connect may indicate that a TimesTen data store is being recovered. This
happens only for a first connect.
Check ODBC tracing
On Windows platforms, if ODBC tracing is enabled, it can slow connect and
disconnect speeds. Double-click ODBC in the Control Panel to open the ODBC Data
Source Administrator. Select the Tracing tab and confirm tracing is disabled. See
"Using ODBC tracing" on page 1-20.
Application becomes disconnected unexpectedly
If an application becomes disconnected from a TimesTen data store, 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 but the application was not in the middle
of executing code in the TimesTen library, 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.
Possible cause See...
Data store is being recovered. "Check if data store is being recovered" on page 2-9
ODBC tracing is enabled. "Check ODBC tracing" on page 2-9
Other possible causes "API tracing" on page 1-10