Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

ERROR: "ORA-12514, TNS:listener does not currently know of service requested in connect descriptor" while connecting to Oracle Database from Data Archive service
Problem Description

While connecting to Oracle database from Data Archive service through Archive/Retirement jobs or from Enterprise Data Manager (EDM) client, connection fails with 'ORA-12514' error message, as below:

 

URL:jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=zest)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ORCL)))

Userid: ILM_ADMIN; nested exception is: 

        java.sql.SQLException: AMConnectionManager.getSingleConnection Failed!

 Cause:oracle.net.ns.NetException: Listener refused the connection with the following error:

ORA-12514, TNS:listener does not currently know of service requested in connect descriptor msg: Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor

Cause

This issue occurs in one of the following cases:

  • Listener service on the source Oracle Database is not running.
  • Service Name of the Oracle database is different from SID.

All the JDBC connections to Oracle Database from Data Archive service, would be using SERVICE_NAME. Hence if the SID and SERVICE_NAME are not same for the Oracle Database, to which connection is established and if SID is used, then connection would fail.

Solution

To resolve this issue, execute the following steps:

  1. ​Confirm if the Listener service is running in the Source Database. Once it is confirmed to be running, try connecting from 'Oracle SQL Developer' client and confirm if the connection gets established successfully.
  2. Connect to source Oracle database and run the following queries, to confirm on the SID and SERVICE_NAME: 
    select value from v$parameter where name like '%service_name%'; --ORACLE SERVICE NAME
    select instance from v$thread; -- ORACLE SID
    select host_name,instance_name,version from v$instance; -- ORACLE SID

If the result of the first query is different from others, then it can be confirmed that SERVICE_NAME of Oracle Database is different from its SID. In that case, for resolving the connection issue encountered in Data Archive, use the result of the first query in the 'Service Name' attribute of the Oracle connection in Data Archive service.

More Information
Applies To
Product: Data Archive
Problem Type:
User Type:
Project Phase:
Product Version: Data Archive 6.3; Data Archive 6.4
Database: Oracle
Operating System: Windows; Linux; AIX; HP-UX; Solaris; UNIX
Other Software:

Reference
Attachments
Last Modified Date:10/5/2016 10:44 PMID:501657
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)