Unable to Resolve Oracle Service Name

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

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

  • Ensure that the OracleNetServiceName set in your database source name definition matches the Oracle Service Name for the Oracle Database 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 Database server and confirm that there is a service name or a SID that identifies the Oracle Database server. If you add or modify a service name, you may need to restart.

    Check the cache administration user name and password on the Oracle database 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 OracleNetServiceName specified in your database source name definition.

    Note:

    Your cache administration user may be different from your regular Oracle database user. See Create the Oracle Database Users and Default Tablespace in the Oracle TimesTen In-Memory Database Cache Guide.

  • Ensure that there is only one copy of tnsnames.ora on your TimesTen system. Also check the permission on tnsnames.ora.

  • If you run TimesTen on a Linux or UNIX system, check that the ORACLE_HOME environment variable is correctly defined. For example: 

    ORACLE_HOME=/products/oracle11g

  • Check the Oracle Database client and server versions. See Incompatible Oracle Database Server and Client Versions.