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-07-2017

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

  • ora-39057 : invalid worker request string for string jobs.
  • ora-13124 : unable to determine column id for column string
  • ora-26046 : REF column string expects scoped table name string; user passed in string.
  • ora-25194 : invalid COMPRESS prefix length value
  • ora-36637 : (XSDUNION05) The concat dimension cannot be defined as UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-00119 : invalid specification for system parameter string
  • ora-01882 : timezone region string not found
  • ora-02349 : invalid user-defined type - type is incomplete
  • ora-01671 : control file is a backup, cannot make a standby control file
  • ora-25257 : consumer must be specified with a multi-consumer queue
  • ora-39145 : directory object parameter must be specified and non-null
  • ora-14151 : invalid table partitioning method
  • ora-06257 : NETNTT: cannot send command line to shadow process
  • ora-31694 : master table string failed to load/unload
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-30930 : NOCYCLE keyword is required with CONNECT_BY_ISCYCLE pseudocolumn
  • ora-24774 : cannot switch to specified transaction
  • ora-16143 : RFS connections not allowed during or after terminal recovery
  • ora-06750 : TLI Driver: sync failed
  • ora-39046 : Metadata remap string has already been specified.
  • ora-14523 : Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
  • ora-39176 : Encryption password is incorrect.
  • ora-27467 : invalid datatype for string value
  • ora-40219 : apply result table string is incompatible with current operation
  • ora-01076 : multiple logons per process not yet supported
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-30677 : session is already connected to a debugger
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-29868 : cannot issue DDL on a domain index marked as LOADING
  • ora-23537 : function or procedure string is not allowed to be invoked from this site.
  • 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.