ORA-12514 error- TNS: Listener does not currently know of service requested in connect descriptor

Document ID : KB000008272
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

I am getting below error while trying to connect to a database instance. This happens for Datamaker, Fast Data Masker (FDM), and Subset. 


LISTENER REFUSED THE CONNECTION WITH THE FOLLOWING ERROR: 
ORA-12514, TNS: LISTENER DOES NOT CURRENTLY KNOW OF SERVICE REQUESTED IN CONNECT DESCRIPTOR 

Environment:
CA Test Data Manager (TDM)- Datamaker, Fast Data Masker (FDM), Subset
Cause:

In General:
The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener. 

 

For Subset:
When you launch Subset from within Datamaker, you are seeing the error because it is expecting the "tnsnames.ora" file in the Datamaker installation folder.

You will see this error if you do not have the TNSNAMES.ORA files in these locations with the instance and service names listed correctly:
C:\Program Files (x86)\Grid-Tools\GTDatamaker
C:\odac64\network\admin

 

Make sure the profiles that are stored in %APPDATA%\Grid-Tools\profiles.xml are accurate.
You can also use the Utilities -> Connect Repository menu option to make sure you select the right profile for the repository connection, which would update the profiles.xml file. 

Resolution:

Datamaker:

  • Sometimes the listener service is not statis, so try waiting a moment then trying to connect a second time. 
  • Check which services are currently known by the listener by executing: lsnrctl services <listener name> 
  • Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener. 
  • If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener. 
  • Check for an event in the listener.log file. 
  • Please review the following documents with your DBA in order to investigate the cause and find a solution: 
    https://docs.oracle.com/cd/B19306_01/server.102/b14219/net12500.htm 
    http://dba-oracle.com/t_ora_12514_tns_listener_does_not_currently_know_service_requested.htm

 

Subset:

  • Try launching Subset standalone, instead of through the Datamaker UI.
  • Make sure the repository profile connection details (GTREP) are correct in the tnsnames.ora file in C:\ProgramFiles (x86)\Grid-Tools\GTDatamaker. 

 

Fast Data Masker:

  • The ‘service’ name is the name the listener knows the database by and that should not change. 
  • Trying connecting with the service name instead of a global name.
Additional Information:

If you experience any further issues, please open a support case by going to https://www.ca.com/us/services-support/ca-support/contact-support.html.