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 : 24-09-2017

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

  • ora-31159 : XML DB is in an invalid state
  • ora-31062 : Cannot delete an unsaved resource
  • ora-24281 : invalid access past the maximum size of LOB parameter string
  • ora-14098 : index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
  • ora-40103 : invalid case-id column: string
  • ora-00255 : error archiving log string of thread string, sequence # string
  • ora-32319 : Cannot use direct loader log to FAST REFRESH materialized view "string"."string"
  • ora-16773 : error starting Redo Apply
  • ora-22850 : duplicate LOB storage option specificed
  • ora-12641 : Authentication service failed to initialize
  • ora-24388 : Unsupported functionality in fast path mode
  • ora-25135 : cannot use the SINGLE TABLE option
  • ora-00060 : deadlock detected while waiting for resource
  • ora-01941 : SEQUENCE keyword expected
  • ora-32120 : Buffer size is less than amount specified
  • ora-32615 : incorrect use of MODEL IS ANY predicate
  • ora-07209 : sfofi: file size limit was exceeded.
  • ora-31231 : DBMS_LDAP: invalid PROPERTY_SET
  • ora-28651 : Primary index on IOTs can not be marked unusable
  • ora-28044 : unsupported directory type
  • ora-28664 : a partitioned table may not be coalesced as a whole
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-39044 : Metadata transform string has already been specified.
  • ora-22931 : MOVE of nested table to a different tablespace not supported
  • ora-06919 : CMX: error during write request (unknown event)
  • ora-30687 : session terminated by debugger
  • ora-06514 : PL/SQL: The remote call cannot be handled by the server
  • ora-32627 : illegal pattern in MODEL FOR LIKE loop
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-24376 : cannot register/get user callback for non-environment handle
  • 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.