Technical data

Unable to resolve Oracle Service Name

4-4 Oracle TimesTen In-Memory Database Troubleshooting Procedures Guide

Log on to each grid node by connecting to the datastores on the rebooted server.

Start the replication agent by executing ttRepStart. The replication agent will

flush the existing log, even if the log is current.

2. Call ttGridAttach on each node, which will fail with a communication error

because it cannot communicate with other members. The failed attach cleans up

the node information.

3. The last node on which you execute the ttGridAttach should succeed. At this

point you have cleaned up all nodes, so execute ttGridAttach on all nodes

again to attach each node to the grid.

4. Resume normal database operations.

Unable to resolve Oracle Service Name

If you receive error ORA-12514 indicating "could not resolve service name":

■ Use the Oracle TNSPING utility to verify that the service can be reached.

■ Ensure that the OracleID set in your DSN definition matches the Oracle Service

Name for the Oracle instance that contains the tables to cache in TimesTen.

■ Ensure that there is a service name defined. If it is a Windows Oracle client, use

Oracle Net Configuration Assistant to configure a service name. In Oracle Net

Configuration Assistant, navigate to Oracle Net Configuration -> Local -> Service

Naming, select your Oracle server and confirm that there is a service name or a

SID that identifies the Oracle server. If you add or modify a service name, you

may need to reboot.

Check the cache administration user name and password on Oracle with SQL*Plus

to make sure this service name works. For example:

%sqlplus cache_admin_user/cache_admin_pwd@OracleHost

cache_admin_user is the cache administration user name, cache_admin_pwd

is the cache administration user password, and OracleHost is the OracleID

specified in your DSN definition.

■ Ensure that there is only one copy of tnsnames.ora on your TimesTen machine.

Also check the permission on tnsnames.ora.

■ If you are running TimesTen on a UNIX system, check that the ORACLE_HOME

environment variable points to the correct Oracle installation directory. For

example:

ORACLE_HOME=/products/oracle10g

■ Check the Oracle client and server versions. See "Incompatible Oracle Server and

Client versions" on page 4-5.

Unable to resolve connect identifier

You may receive ORA-12154 "TNS:could not resolve the connect identifier specified"

when you try to connect to a a data store.

Note: Your cache administration user may be different from your

regular Oracle user. See "Create Oracle users" in the Oracle In-Memory

Database Cache User's Guide.