Technical data

Application unable to find previously created objects
Troubleshooting TimesTen Applications and Data Stores 2-15
Specify object owner
Tables, indexes and sequences can be created either with a single name, such as
PARTS, or with a qualified name incorporating an owner and table name, such as
STAN.PARTS. When accessing a table or index, if no owner is specified, TimesTen first
assumes that the owner is the login ID of the user (the value of the UID attribute). If
TimesTen cannot find the table or index under the user's login ID, it then assumes that
the owner is user SYS.
If applications need to connect to a data store as different users and share objects,
explicitly specify the owners of the objects when they are created and referenced.
Check privilege to access tables
All privileges for the user can be viewed in the SYS.USER_SYS_PRIVS table, which
contains all of the system-level privileges for a given user, and the SYS.USER_TAB_
PRIVS table, which contains all of the object-level privileges for a given user. Check
these tables to verify if you have 'SELECT' privilege for the tables. If you do not have
'SELECT' privilege for the tables, the privilege may be granted with the GRANT
statement. The method for granting privileges is described in the "Managing Access
Control" chapter in the Oracle TimesTen In-Memory Database Operations Guide.
Check temporary DSN attribute
Temporary data stores (DSN attribute: Temporary=1) persist until all connections to
the data store have been removed. When attempting to access a table in a temporary
data store and the table does not exist, it is possible that the data store in which the
table resided in has been dropped.
Check Overwrite DSN attribute
If the Overwrite and AutoCreate DSN attributes are enabled and the data store
already exists, TimesTen drops that data store and creates a new one. Any tables that
were created in the old data store are dropped.
Check path name to data store
To ensure that you are always accessing the same data store when connecting to a
particular DSN, use an absolute data store path name instead of a relative one. For
example, if the demo data store is in the datastore directory, specify:
DataStore=/datastore/demo
rather than:
DataStore=demo
In the latter case, the data store path name is relative to the directory where the
application was started. If you are unable to find a table and you are using a relative
data store path name, it is possible that the data store in which the table resides in does
exist but the data store (checkpoint and log) files are in a different directory than the
one that you are accessing.
See "Specifying Data Source Names to identify TimesTen data stores" in the Oracle
TimesTen In-Memory Database Operations Guide.