Dbms Error Code 12154
Contents |
Early Adopter Program ArcGIS Ideas Esri Support Services ArcGIS Blogs ArcGIS Code Sharing Product Life Cycles Manage Cases Request Case Start Chat Back to results Print Share Is ora 12154 could not resolve the connect identifier specified This Content Helpful? Search on GeoNet Submit to ArcGIS Ideas Error: Failed
Ora-12154 Tns Could Not Resolve The Connect Identifier Specified Windows 7
to connect to the specified server. Underlying DBMS error[ORA-12154: TNS:could not resolve the connect identifier specified. No ora-12154 sqlplus extended error] Error Message When creating a direct connect from ArcGIS Desktop installed on a computer installed with Windows 64-bit, the following error message is displayed:"Failed to connect to arcgis ora-12154 the specified server. Underlying DBMS error[ORA-12154: TNS:could not resolve the connect identifier specified. No extended error.]" Cause This is a known issue with parentheses in install path names on the Windows 64-bit operating system. Solution or Workaround Perform one of the following workarounds:Reinstall ArcGIS Desktop on a Windows 64-bit computer to a path that does not contain parenthesis. For
Error While Trying To Retrieve Text For Error Ora-12154
example:C:\Program Files\ArcGISFix the bug on a 64-bit computer:1. Download and install the Oracle 10g 32 bit client from Oracle.com. This installs version 10.2.0.1 of the client.2. Download and install Oracle Patch Number 4547817, which is '10.2.0.2 Patch for Windows 32-bit'. This upgrades the client to version 10.2.0.2.3. Download and install Oracle 32-Bit Patch Number 5383042. This patch fixes Oracle Bug 3807408:Externally authenticated usernames containing a '(',')' or '=' cannot be authenticated, additionally if a program name / path contains these characters, it may not be possible to connect (ORA-12154). Created: 5/5/2016 Last Modified: 5/5/2016 Article ID: 000008951 Software: ArcSDE 9.1, 9.2, 9.3, 9.3.1 Is This Content Helpful? Is This Content Helpful? Yes No We're glad to know this article was helpful. How can we make this better? Submit Contact our Support Team Request Case Start Chat Questions or issues with the site? Send Feedback Contact Support USA +1-888-377-4575 Name Email URL What issues are you having with the site? How can we improve? * Submit Feedback sent successfully. Error while sending mail. Loading
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 enabled. Please turn ora-12154 tns listener does not currently know of service requested in connect descriptor JavaScript back on and reload this page. Please enter a title. tns-03505 You can not post a blank message. Please type your message and try again. More discussions
Sqlnet.ora Example
in General Database Discussions All PlacesDatabaseGeneral Database Discussions This discussion is archived 1 2 3 … Previous Next 84 Replies Latest reply on Aug 4, 2010 http://support.esri.com/technical-article/000008951 1:51 PM by rajeysh ORA-12154: TNS:could not resolve the connect identifier specified 429733 Sep 29, 2004 8:57 PM Hi, I have a problem with my oracle 10g instalation over win 2003, each time a setup a new database I works fine the first time, but when I restart the win 2003, the https://community.oracle.com/thread/269600 next time oracle throws a error: ORA-12154: TNS:could not resolve the connect identifier specified. Can anybody help me with it!!!!! thanks for you help. 242753Views Tags: none (add) databaseContent tagged with database, errorContent tagged with error, ora-12154Content tagged with ora-12154, oracleContent tagged with oracle, sqlplusContent tagged with sqlplus, tnsContent tagged with tns, visual_studioContent tagged with visual_studio, vsContent tagged with vs This content has been marked as final. Show 84 replies 1. Re: ORA-12154: TNS:could not resolve the connect identifier specified 381046 Sep 30, 2004 4:49 AM (in response to 429733) hi open command prompt and set oracle_sid=
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! Oracle PostersOracle Books Oracle Scripts Ion Excel-DB http://www.dba-oracle.com/t_ora_12154_tns_resolve_service_name.htm Don Burleson Blog
http://www.bluegecko.com/ora-12154-tnscould-not-resolve-the-connect-identifier-specified/ 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 error, always related to your local copy of the tnsnames.ora file, your listener configuration and your database could not 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: $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 could not resolve 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 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: The following actions mayBlog Oracle MySQL News & Events Oracle Applications Amazon Web Services Jeremiah Wilton's Oradeblog OurSQL Community Podcast Remote DBA Team viewer Whitepapers About Us Philosophy The Blue Gecko Teams Employment Opportunities Partners News Press Contact Us March 4, 2009 by jwilton ORA-12154: TNS:could not resolve the connect identifier specified The error also appears in some versions as: "ORA-12154: TNS:could not resolve service name." When a program needs to connect to an Oracle service via Oracle Networking (SQL*Net), it must look up the connect data for that service somewhere. When the lookup fails, the Oracle client code raises ORA-12154. Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link. Note that this error is generated by the Oracle client code on the local host where the program is running, not by the remote Oracle service to which you are attempting to connect. There are a few ways that the Oracle client code can look up connect data: A flat file named tnsnames.ora Oracle Names service LDAP If you see the whole ORA-12154 error with the text, then your program is finding a working Oracle client install, but that the Oracle service as specified is not listed in tnsnames.ora, Oracle Names or LDAP. The most common causes of ORA-12154 are: The entry is missing from tnsnames.ora The entry in tnsnames.ora is malformed The program is using tnsnames.ora from the wrong ORACLE_HOME The program is not using a fully-qualified service name, but no default domain is enabled in sqlnet.ora Most sites use tnsnames.ora, but enough use Oracle Names and LDAP that the first step should be to