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 : 25-09-2017
ORA-12154

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

  • ora-26517 : materialized view control entry for 'string.string' was not found
  • ora-31153 : Cannot create schema URL with reserved prefix "http://xmlns.oracle.com/xdb/schemas/"
  • ora-15040 : diskgroup is incomplete
  • ora-25352 : no current transaction
  • ora-12819 : missing options in PARALLEL clause
  • ora-38603 : FI including & excluding cursor can only return one column
  • ora-14114 : partitioned table cannot have column with object, REF, nested table, array datatype
  • ora-30689 : improper value for ORA_DEBUG_JDWP
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-39768 : only one direct path context top level column array is allowed
  • ora-27504 : IPC error creating OSD context
  • ora-19687 : SPFILE not found in backup set
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-36612 : (XSLMS01) invalid OLAP message number: value
  • ora-14046 : a partition may be split into exactly two new partitions
  • ora-28237 : seed length too short
  • ora-06141 : NETTCP: no privilege for user
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-22166 : collection is empty
  • ora-00322 : log string of thread string is not current copy
  • ora-31406 : change source string is referenced by a change set
  • ora-28270 : Malformed user nickname for password authenticated global user.
  • ora-16243 : paging out string bytes of memory to disk
  • ora-06534 : Cannot access Serially Reusable package string
  • ora-00601 : cleanup lock conflict
  • ora-02426 : privilege grant failed
  • ora-19700 : device type exceeds maximum length of string
  • ora-27508 : IPC error sending a message
  • ora-22337 : the type of accessed object has been evolved
  • 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.