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

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

  • ora-01608 : cannot bring rollback segment 'string' online, its status is (string)
  • ora-25266 : didnt try to dequeue by message id. with the signature
  • ora-12543 : TNS:destination host unreachable
  • ora-30556 : functional index is defined on the column to be modified
  • ora-28107 : policy was disabled
  • ora-01515 : error dropping log group string: no such log
  • ora-29533 : attempt to overwrite class or resource string while defining or compiling string.string
  • ora-02780 : Name given for the core dump directory is invalid
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • ora-12593 : TNS:no registered connection
  • ora-29397 : cannot grant/revoke switch privilege for string
  • ora-13019 : coordinates out of bounds
  • ora-32054 : lost communication with FMPUTL process
  • ora-22887 : type of REF column is not the same as that of its scoped table
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-16019 : cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
  • ora-19373 : invalid staging table or tablespace
  • ora-12061 : invalid ALTER MATERIALIZED VIEW option
  • ora-25294 : Cannot propagate user buffered messages to a database with version lower than 10.2
  • ora-39012 : Client detached before the job started.
  • ora-13761 : invalid filter
  • ora-02212 : duplicate PCTFREE option specification
  • ora-07756 : slemcf: fread failure
  • ora-13851 : Tracing for client identifier string is already enabled
  • ora-16165 : LGWR failed to hear from network server
  • ora-13624 : The task string is executing and cannot be deleted or modified.
  • ora-12647 : Authentication required
  • ora-28181 : proxy 'string' failed to enable one or more of the specified initial roles for client 'string'
  • ora-12801 : error signaled in parallel query server string
  • ora-33450 : (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.
  • 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.