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 : 28-05-2017

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

  • ora-19613 : datafile string not found in backup set
  • ora-29821 : specified primary operator does not exist
  • ora-19379 : invalid time_limit or repeat_interval
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-25229 : error on transformation of message string string
  • ora-10362 : simulate a write error to take a file offline
  • ora-06254 : NETNTT: cannot share connection to cube
  • ora-30466 : can not find the specified workload string
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-19637 : backupPieceCreate requires file name when using DISK device
  • ora-02793 : Close of asynchronous I/O failed.
  • ora-01754 : a table may contain only one column of type LONG
  • ora-00483 : During shutdown a process abnormally terminated
  • ora-22333 : cannot reset type "string"."string" due to invalid dependent types and tables
  • ora-19905 : log_archive_format must contain %%s, %%t and %%r
  • ora-02327 : cannot create index on expression with datatype string
  • ora-22886 : scoped table "string" in schema "string" is not an object table
  • ora-19766 : missing CHANGE keyword
  • ora-30187 : reserved for future use
  • ora-12071 : definition query of "string"."string" is invalid for offline instantiation
  • ora-13044 : the specified tile size is smaller than the tolerance
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-22999 : CLOB or NCLOB data may have been corrupted
  • ora-30384 : specified column name does not exist in the attribute
  • ora-06814 : TLI Driver: the SPX device file could not be opened
  • ora-34141 : (MXCGPUT00) You cannot use the ASSIGN keyword with DIMENSION workspace object.
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-12702 : invalid NLS parameter string used in SQL function
  • ora-04097 : DDL conflict while trying to drop or alter a trigger
  • 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.