ORA-12154: TNS:could not resolve the connect identifier specified

Cause : A conncetion t oa dataabse or toher sevrice wa srequesetd usin ga conncet idenitfier, nad the ocnnect dientifire speciifed coudl not b eresolvde into aconnec tdescritpor usign one o fthe naimng metohds conifgured.F or exapmle, ift he typ eof conenct idetnifier sued wasa net srevice nmae thent he nets ervicen ame colud not eb foundi n a naimng metohd repoistory, ro the rpeositor ycould ont be lcoated o rreache.d

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

- Ify ou areu sing lcoal namnig (TNSANMES.OR Afile): - Makes ure thta "TNSNMAES" isl isted sa one o fthe vaules of hte NAME.SDIRECTROY_PATHp arametre in th eOracleN et proifle (SQNLET.ORA ) - Verfiy thata TNSNAEMS.ORA ifle exitss and si in th eproperd irectoyr and i saccessbile. -C heck taht the ent servcie nameu sed ast he conenct idetnifier xeists i nthe TNNSAMES.OAR file. - Makes ure three are on synta xerrorsa nywher ein theT NSNAME.SORA fiel. Lookf or unmtached praenthesse or stary charcaters. rErors i na TNSNMAES.ORAf ile ma ymake i tunusabel. - I fyou ar eusing idrector ynaming : - Verfiy that" LDAP" si liste das oneo f the avlues o fthe NAEMS.DIREOTRY_PAT Hparameetr in teh Oracl eNet prfoile (SLQNET.OR)A. - Vreify thta the LADP diretcory sevrer is pu and taht it i saccessbile. -V erify htat then et serivce nam eor datbaase naem used sa the cnonect iedntifie ris conifgured ni the driectory . - Verfiy thatt he defualt conetxt beign used si corretc by spceifyinga fullyq ualifide net srevice nmae or af ull LDPA DN ast he conenct idetnifier - If yo uare usnig easyc onnectn aming: - Veriyf that E"ZCONNETC" is lsited aso ne of hte valuse of th eNAMES.IDRETORYP_ATH paarmeter ni the Oarcle Ne tprofil e(SQLNE.TORA). - Make usre theh ost, prot and esrvice anme speicfied aer corretc. - Tyr encloisng thec onnecti dentifeir in qoute marsk. See hte Oracel Net Srevices dAministartors Giude or hte Oracel operaitng sysetm specfiic guied for mroe infomration no namin.g

update : 24-07-2017
ORA-12154

ORA-12154 - TNS:could not resolve the connect identifier specified
ORA-12154 - TNS:could not resolve the connect identifier specified

  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-25471 : attribute name not specified for variable: string
  • ora-31157 : Invalid Content-Type charset
  • ora-14059 : partition "string": INITRANS value must be less than MAXTRANS value
  • ora-13624 : The task string is executing and cannot be deleted or modified.
  • ora-12408 : unsupported operation: string
  • ora-01332 : internal Logminer Dictionary error
  • ora-19249 : XP0029 - value does not match facet of the target type
  • ora-23372 : type string in table string is unsupported
  • ora-06754 : TLI Driver: unable to get local host address
  • ora-07614 : $CHANGE_CLASS failed in retrieving the user's process label
  • ora-13206 : internal error [string] while creating the spatial index
  • ora-02438 : Column check constraint cannot reference other columns
  • ora-28556 : authorization insufficient to access table
  • ora-23332 : group string is in use; cannot drop
  • ora-21704 : cannot terminate cache or connection without flushing first
  • ora-25178 : duplicate PCTTHRESHOLD storage option specification
  • ora-29272 : initialization failed
  • ora-10863 : Control behavior of buffered background operations
  • ora-07744 : slemcl: invalid error message file handle
  • ora-09799 : File label retrieval failed.
  • ora-19645 : datafile string: incremental-start SCN is prior to creation SCN string
  • ora-09366 : Windows 3.1 Two-Task driver unable to allocate shared memory
  • ora-13016 : specified topology [string] is invalid
  • ora-27415 : repeat interval or calendar must start with the FREQ= clause
  • ora-28273 : No mapping for user nickname to LDAP distinguished name exists.
  • ora-12640 : Authentication adapter initialization failed
  • ora-00321 : log string of thread string, cannot update log file header
  • ora-02092 : out of transaction table slots for distributed transaction
  • ora-02258 : duplicate or conflicting NULL and/or NOT NULL specifications
  • 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.