Oracle Logon Error Ora-12154 And Ora-12154
Contents |
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it error ora-12154 tns could not resolve the connect identifier specified enabled. Please turn JavaScript back on and reload this page. ora-12154 tns could not resolve service name Please enter a title. You can not post a blank message. Please type your message
Ora-12154 Tns Could Not Resolve The Connect Identifier Specified Windows 7
and try again. More discussions in General FLEXCUBE Questions All PlacesOracle ApplicationsOracle FLEXCUBE Core BankingGeneral FLEXCUBE Questions This discussion is archived 7 Replies Latest reply
Asp.net Ora-12154: Tns:could Not Resolve The Connect Identifier Specified
on Feb 2, 2014 5:18 PM by Baris Yildirim Unable to resolve ORA-12154: TNS:could not resolve the connect identifier specified Karki Feb 2, 2014 8:24 AM Hi Friends, I am unable to resolve ORA-12154: TNS:could not resolve the connect identifier specified, error:C:\Windows\system32>sqlplus scott/tiger@ORADATASQL*Plus: Release 11.2.0.1.0 Production on Sun Feb ora-12154 sqlplus 2 13:46:10 2014Copyright (c) 1982, 2010, Oracle. All rights reserved.ERROR:ORA-12154: TNS:could not resolve the connect identifier specifiedSQL> select database_name from v$database;DATABASE_NAME----------------------------------------------------ORADATASQL> select instance_name from v$instance;INSTANCE_NAME----------------oradatatnsnames.ora============ORADATA = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL=TCP)(HOST=himanshu-PC)(PORT=1521)) ) (CONNECT_DATA =(SERVICE_NAME = oradata) (SERVER = DEDICATED) ) )listener.ora=========LISTENER = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = himanshu-PC)(PORT = 1521)) ) (DESCRIPTION = (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521)) ) )SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = ORADATA) (ORACLE_HOME = G:\app\himanshu\product\11.2.0\dbhome_1) (SID_NAME = oradata) ) )sqlnet.ora========SQLNET.AUTHENTICATION_SERVICES = (NTS)C:\Windows\system32>lsnrctl statusLSNRCTL for 32-bit Windows: Version 11.2.0.1.0 - Production on 02-FEB-2014 13:53:37Copyright (c) 1991, 2010, Oracle. All rights reserved.Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=himanshu-PC)(PORT=1521)))STATUS of the LISTENER------------------------Alias LISTENERVersion TNSLSNR for 32-bit Windows: Version 11.2.0.1.0 - ProductionStart Date 02-FEB-2014 13:29:35Uptime 0 days 0 hr. 24 min. 6 secTrace Level offSecurity ON: Local OS AuthenticationSNMP OFFListener Parameter File G:\app\himanshu\product\11.2.0\dbhome_1\network\admin\listener.oraListener Log File g:\app\himanshu\diag\tnslsnr\himanshu-PC\listener\alert\log.xmlListening Endpoints Summary... (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=himanshu-PC)(PORT=1521))) (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPE
resolve the connect identifier specified"? Article: 00951 Last Reviewed: 7th September 2006 Revision: 1 This error indicates that Oracle is unable to locate the service name specified in your Easysoft ODBC-Oracle Driver ODBC data source. You
Error While Trying To Retrieve Text For Error Ora-12154
need to check the Database attribute value in the data source.If you are using the ora-12154 tns could not resolve service name oracle 11g standard Oracle client, the Database attribute value must specify a valid service name defined in tnsnames.ora. For example, for the following tnsnames.ora tns could not resolve the connect identifier specified oracle 10g entry, the Database attribute value needs to be my_database: my_database = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = my_host)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = my_database) ) ) If you are using https://community.oracle.com/thread/3510766 the Instant Client without a tnsnames.ora file, the Database attribute value needs to be a SQL connect URL rather than a service name: //host:port/service_name where host is the host name or IP address of the Oracle database server, port is the Oracle listener port and service_name is the service name. For example: //my_host:1521/my_database If you want to use the Instant Client with a tnsnames.ora file, the Database attribute value must specify a http://www.easysoft.com/support/kb/kb00951.html tnsnames.ora service name and you need to set and export the TNS_ADMIN environment variable. Set TNS_ADMIN to specify the location of the tnsnames.ora file. For example: TNS_ADMIN = /home/oracle/network/admin export TNS_ADMIN Applies To Products Easysoft ODBC-Oracle Driver Knowledge Base Feedback * Did this content help you? Yes No Maybe * Please select one option based on your first choice: I'm very satisfied I think it will help, but I haven't tried it yet It is helpful, but I need more information It is helpful, but hard to understand Seemed relevant in search results, but didn't help me The information is incorrect The page contains one or more broken links Suggest new content or let us know how we can improve this content: (* Required Fields) About Easysoft Contact Us About Us Clients Upgrade Offer Blog Careers Products ODBC Drivers JDBC Drivers Bridges and Gateways In Development Services Consultancy Training Custom Development Licensing Product Licenses Prices Support Support Home Solution Wizard Getting Started Guides User Guides Knowledge Base Search Easysoft.com Documentation Knowledge Base Popular Resources Developer Area Client Applications Legal Privacy Statement © 1993 - 2016 Easysoft Limited. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other trademarks and registered trademarks appearing on easysoft.com are the property of their respective owners.
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! http://www.dba-oracle.com/t_ora_12154_tns_resolve_service_name.htm Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson http://ss64.com/ora/syntax-ora-12154.html Blog
ORA-12154: TNS could not resolve service name tips Question: I need help with this error: ORA-12154: TNS: could not resolve service name.Answer: The ORA-12154 is a very common could not error, always related to your local copy of the tnsnames.ora file, your listener configuration and your database name aliases. Make sure that your listener is listening for the same service name that you are using. Your service name might have an alias, so check for global (world) entries and local entries. Check: could not resolve $ORACLE_HOME/network/admin/tnsnames.ora Check your global_name setting with this SQL: select * from global_name; The query value should match your init.ora parms for db_name and db_domain, You can change the global_name with an ALTER DATABASE command, as follows: alter database rename global_name to xxx; Also see these notes on configuring your tnsnames.ora file and troubleshooting network errors. Rampant author Steve Callan notes this on the ORA-12154 error: "One of the most common errors related to improper configuration is the "ORA-12154: TNS: could not resolve service name" error. It is not uncommon for new users of Oracle to spend hours upon hours trying to figure out what their mistake is when ORA-12154 appears." The oerr utility notes this on the ORA-12154 error:: $oerr ora 12154 ORA-12154: TNS:could not resolve the connect identifier specifiedCause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connserver but either failed to contact the server or did not find a matching service name on that server. TNS or 'Transparent Network Substrate' is a transport protocol that allows Oracle sessions to communicate across a network. DB Server <=> Listener <=> Network connection <=> Client (SQL*Net) <=> Application. In the path above, tnsping can be used to test the parts in bold and should be the first troubleshooting step. If tnsping fails, that generally indicates a problem finding the server connection - if TNSNAMES specifies an IP address, is it correct?, if it's a DNS name, is that resolving correctly? (try switching for an IP address to find out.) If tnsping succeeds, that can indicate a problem with the client configuration but could equally be that the connection is working as far as the listener but the database is down. Try comparing with another PC - if multiple machines are failing that usually points towards a server issue. Ora-12154 can be a tricky problem to nail down because there are many possible causes, try making a connection directly on the server or completely regenerate the TNSNAMES.ORA file on the client. ORA-12154 description: Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached. Action: Local naming (TNSNAMES.ORA file): - Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA) - Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible. - Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file. - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file can make it unusable. Directory Naming: - Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA). - Verify that the LDAP directory server is up and that it is accessible. - Verify that the net service name or database name used as the connect identifier is configured in the directory. - Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect id