ERROR:"ORA-12514, TNS:listener does not currently know of service requested in connect descriptor" when starting Hive Metastore
SupportKB
Problem Description:
When starting a Hive Metatsore service from Ambari, the service fails to start with the following error: ERROR: Check db_connection_check was unsuccessful. Exit code: 1. Message: ERROR: Unable to connect to the DB. Please check DB connection properties. java.sql.SQLException: Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
Traceback (most recent call last): File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py", line 506, in CheckHost().execute() File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 280, in execute method(env) File "/var/lib/ambari-agent/cache/custom_actions/scripts/check_host.py", line 206, in actionexecute raise Fail(error_message) resource_management.core.exceptions.Fail: Check db_connection_check was unsuccessful. Exit code: 1. Message: ERROR: Unable to connect to the DB. Please check DB connection properties. java.sql.SQLException: 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 maybe a temporary condition that can occur after the listener has started and before the database instance has registered with the listener.
The following is the connection string used in this case for connecting to Oracle database:
"jdbc:oracle:thin:@//node01.hortonworks.com:1521/hdporcl"The error ORA-12514: TNS:listener does not currently know of service requested in connect descriptor means that a 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 (usually a database service). In this case it is hdporclthat either has not been dynamically registered with the listener or has not been statically configured for the listener.
Solution:
To solve the issue, do the following:
- Verify that the SERVICE_NAME parameter exists in the connect descriptor. You can check this by checking the entries for the Oracle database in the tnsnames.ora file.
- Check which services are currently known by the listener by executing the following in Oracle server:
lsnrctl services <listener name>
- Request your database administrator to check listerner.log to check for further error messages.
- After confirming that the listener is running and the SERVICE_NAME parameter is valid, attempt a restart of Hive Metastore
- If there is a change in SERVICE_NAME, make the changes in JDBC URL of Hivemetastore using Ambari Hive-Configs and restart Hive Metastore
About:
This article created by Hortonworks Support (Article: 000005691) on 2017-05-12 02:34
OS: n/a
Type: Configuration
Version: n/a
