Technical data

Application unable to connect to data store in direct mode
2-4 Oracle TimesTen In-Memory Database Troubleshooting Procedures Guide
Upgrading your data store
A data store is only guaranteed to be accessible by the same minor release of TimesTen
that was used to create the data store. When you upgrade the TimesTen software and
you would like to use the new release to access a data store that was previously
created, create a data store with the new release. Then use the ttMigrate utility to
copy the tables, indexes, and table data from the old data store to the new one.
See "Data Store Upgrades" in the Oracle TimesTen In-Memory Database Installation Guide
for details.
Privileges to connect to data store
The user must have the CREATE SESSION privilege to connect to the data store. If you
do not have access, the administrator must use the GRANT statement to grant you the
CREATE SESSION privilege. See "Granting privileges to connect to the database" in
the Oracle TimesTen In-Memory Database Operations Guide.
Check file system permissions to access data store
A "permission denied" error is generated if you attempt to connect to a data store and
you do not have the proper permissions to access the checkpoint or transaction log
files or the directory where those files reside. Check the file system permissions on the
files located in the directory specified in the DataStore attribute in your DSN.
Check that the TimesTen daemon is running
If the TimesTen daemon or Data Manager service is not running, an attempt to connect
to a data store generates TimesTen error 799 (Unable to connect to daemon; check
daemon status).
Use the ttStatus utility as described in "Check the TimesTen user error log" on
page 2-2 to check the status of the TimesTen daemon.
Check DSN definition
In your DSN description:
■ Check DSN attributes
■ Check path name to data store and transaction log directories
Check DSN attributes
Certain connection options or DSN attribute settings combinations are not compatible.
In cases where incompatible settings are used, an error is returned to the application
when it attempts to connect to a data store.
Check path name to data store and transaction log directories
Confirm that you have specified the correct path names in the DataStore and LogDir
attributes in your DSN. Also confirm that the path names are absolute path names,
rather than relative. Otherwise, the path name will be relative to the directory where
the application was started.
On Windows, be careful to distinguish between User and System DSNs in the ODBC
Data Source Administrator. Do not create user DSNs because they are visible only to
the user who defines them. System DSNs are visible to all users. In particular, if you
run a TimesTen application as a Windows service, it runs as the user "SYSTEM" by