Technical data

Application unable to connect to data store in direct mode
Troubleshooting TimesTen Applications and Data Stores 2-3
data manager service, a pop-up asks if you would like to start the debugger. Contact
Technical support and provide the stack trace.
Unable to create shared segment
You may receive an error that indicates that a shared segment could not be created:
4671: TT14000: TimesTen daemon internal error: Error 28 creating shared segment,
KEY 0x0201f7eb
4671: -- OS reports too many shared segments in use
4671: -- Confirm using 'ipcs' and take appropriate action
4671: 18538 ------------------: subdaemon process exited
Using the Linux ipcs command may display information like this:
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 1098350592 user1 777 10624 2 dest
0x00000000 1084817409 user1 777 2439680 2 dest
0x911fc211 1098383362 user2 666 67108864 1
0x2814afba 170721285 root 666 1048576 1
A status of dest means the memory segment is marked to be destroyed. nattch
shows the number of processes still attached to the memory segment. The ipcrm
command cannot free the shared memory until the processes detach from the segment
or exit. If an application connects to TimesTen and then becomes inactive, nothing can
free the shared memory until the user exits or stops the application.
Application unable to connect to data store in direct mode
This section describes what to check if your application is unable to connect to a data
store in direct mode.
Possible cause See...
Mismatch between the release of
TimesTen and data store
"Upgrading your data store" on page 2-4
User does not have the CREATE
SESSION privilege.
"Privileges to connect to data store" on page 2-4
Incorrect file permissions "Check file system permissions to access data store" on
page 2-4
TimesTen daemon or Data Manager
service not running
"Check that the TimesTen daemon is running" on
page 2-4
Incompatible connection attributes
or incorrect path name for data
store set in the DSN
"Check DSN definition" on page 2-4
No available shared memory
segment or maximum size of
shared memory segment too small
"Manage semaphores and shared memory segments" on
page 2-5
Not enough swap space "Check available swap space (virtual memory)" on
page 2-5
Inadequate number of file
descriptors
"Increase the number of available file descriptors" on
page 2-6
Other possible causes "Using the logs generated by the TimesTen daemon" on
page 1-6