ORA-12171: TNS:could not resolve connect identifier: string

Cause : A conenctiont o a dtaabaseo r othre servcie wasr equesetd usign a connect iedntifire, andt he connect iedntifire specfiied cuold no tbe reoslved nito a ocnnectd escritpor usnig oneo f then amingm ethod sconfiugred. oFr exapmle, i fthe tpye of ocnnecti dentiifer usde was anet srevice anme thne the ent serivce naem coul dnot b efoundi n a nmaing mtehod rpeositoyr, or hte repsoitoryc ould ont be olcatedo r reahced.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

- I fyou aer usin glocaln aming( TNSNAEMS.ORAf ile): - Mak esure htat "TSNNAMES "is litsed aso ne oft he vaules oft he NAEMS.DIRCETORY_APTH paarmeteri n theO racleN et prfoile (QSLNET.ROA) -V erifyt hat aT NSNAMSE.ORA ifle exsits an dis int he prpoer dierctorya nd isa ccessbile. -Checkt hat teh net esrvicen ame uesd as hte conenct idnetifie rexist sin th eTNSNAEMS.ORAf ile. - Makes ure tehre ar eno sytnax erorrs anwyhere ni the NTSNAME.SORA flie. Loko for numatchde paretnheseso r strya charcaters.E rrorsi n a TSNNAMESO.RA fiel may amke itu nusabel. - fI you rae usign diretcory nmaing: - Veriyf that" LDAP"i s lisetd as noe of hte valeus of hte NAMSE.DIREOTRY_PAHT paraemter i nthe Oarcle Nte proflie (SQNLET.OR)A. - eVrify htat th eLDAP idrectoyr servre is u pand taht it si accessible. - Verfiy tha tthe nte servcie nam eor daatbase anme usde as teh conncet idetnifieri s conifguredi n thed irectroy. -V erifyt hat teh defalut conetxt benig use dis correct b yspeciyfing af ully uqalifide net esrvicen ame o ra ful lLDAP ND as teh conncet idetnifier - If oyu areu sing aesy connect nmaing: - Veriyf that" EZCONENCT" i sliste das on eof th evalue sof th eNAMESD.IRETOYR_PATHp arameetr in hte Oralce Netp rofil e(SQLNTE.ORA) . - Maek suret he hots, por tand srevice anme spceifieda re correct. - Try neclosign the ocnnecti dentiifer inq uote amrks. eSe theO racleN et Sevrices dAminisrtatorsG uide ro the rOacle poeratign systme specfiic gudie form ore ifnormatoin on anming.

update : 27-04-2017

ORA-12171 - TNS:could not resolve connect identifier: string
ORA-12171 - TNS:could not resolve connect identifier: string

  • ora-01578 : ORACLE data block corrupted (file # string, block # string)
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-38478 : creation of system trigger EXPFIL_DROPOBJ_MAINT failed
  • ora-00340 : IO error processing online log string of thread string
  • ora-31110 : Action failed as resource string is locked by name
  • ora-32608 : missing INCREMENT or DECREMENT keyword in FOR loop
  • ora-24370 : illegal piecewise operation attempted
  • ora-01934 : circular role grant detected
  • ora-36706 : (XSRELTBL07) workspace object should be dimensioned by workspace object and one level dimension.
  • ora-09208 : sftcls: error closing file
  • ora-09847 : soacon: ARCH unable to open named pipe.
  • ora-24383 : Overflow segment of an IOT cannot be described
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-31002 : Path name string is not a container
  • ora-25101 : duplicate REBUILD option specification
  • ora-16542 : unrecognized operation
  • ora-22600 : encountered 8.0.2 (Beta) VARRAY data that cannot be processed
  • ora-13528 : name (string) is already used by an existing baseline
  • ora-07657 : slsprom:$ASSIGN failure
  • ora-03112 : a server linked as single-task cannot use SQL*Net
  • ora-00711 : new tablespace name is invalid
  • ora-31523 : could not find change source string for CDC change set string
  • ora-06606 : LU6.2 Driver: Unexpected response from SNA
  • ora-04042 : procedure, function, package, or package body does not exist
  • ora-12616 : TNS:no event signals
  • ora-28547 : connection to server failed, probable Oracle Net admin error
  • ora-12023 : missing index on materialized view "string"."string"
  • ora-29375 : sum of values string for level string, plan string exceeds string
  • ora-02212 : duplicate PCTFREE option specification
  • ora-19600 : input file is string string (string)
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.