connect failed with sql error 12154
SAP on Microsoft WindowsWhere is this place located?All Places SAP on Microsoft Windows 3 Replies Latest reply: Feb 11, 2010 12:54 PM by Mark Norman Tweet *** ERROR => CONNECT failed with sql error '12154' Umang Patodia Feb 11, 2010 7:43 AM Currently Being Moderated Hi,My system landscape consits of one production server and one application server with dialog instance only for load balancing.Up to yesterday this was working perfectly.Todat I restart the application server and when I start SAP service the dispatcher is getting stopped after some time. Yesterday I tried to configure the data guard in the production server with another stanby database server and accordingly I have changed some settings in TNSNAMES.ora and LISTENER.ora. It was not successful and revert back the changes in the TNSNAMES.ora and LISTENER. The dev_disp file output is given below-trc file: "dev_disp", trc level: 1, release: "700"-sysno 00sid GTPsystemid 562 (PC with Windows NT)relno 7000patchlevel 0patchno 52intno 20050900make: multithreaded, ASCII, 64 bit, optimizedpid 3756Thu Feb 11 11:50:20 2010kernel runs with dp version 210(ext=109) (@(#) DPLIB-INT-VERSION-210)length of sys_adm_ext is 360 bytesSWITCH TRC-HIDE on ******LOG Q00=> DpSapEnvInit, DPStart (00 3756) [dpxxdisp.c 1231]shared lib "dw_xml.dll" version 52 successfully loadedshared lib "dw_xtc.dll" version 52 successfully loadedshared lib "dw_stl.dll" version 52 successfully loadedshared lib "dw_gui.dll" version 52 successfully loadedrdisp/softcancel_sequence : -> 0,5,-1use internal message server connection to port 3900Thu Feb 11 11:50:24 2010WARNING => DpNetCheck: NiAddrToHost(18.104.22.168) took 4 seconds***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5233]MtxInit: 30000 0 0DpSysAdmExtInit: ABAP is activeDpSysAdmExtInit: VMC (JAVA VM in WP) is not activeD
server but either failed to contact the server or did not find a matching service name on that server. TNS or 'Transparent Network Substrate' http://ss64.com/ora/syntax-ora-12154.html 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 http://www.dba-oracle.com/t_ora_12154_tns_resolve_service_name.htm 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 connect failed 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 connect failed with 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.
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 Don Burleson BlogORA-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 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 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 may be appropriate: If you are using local naming (tnsnames.ora file): Make sure that TNSNAMES is listed as one of the values of the names.directory_path par