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

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

  • ora-32152 : Cannot perform operation on a null number
  • ora-16637 : an instance failed to access the Data Guard broker configuration
  • ora-39600 : Queue keys needs to be a suffix of cluster key.
  • ora-04078 : OLD and NEW values cannot be identical
  • ora-09944 : Password entry is corrupt.
  • ora-14016 : underlying table of a LOCAL partitioned index must be partitioned
  • ora-00224 : control file resize attempted with illegal record type (string)
  • ora-25223 : user_data type used is not supported
  • ora-37603 : (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing to a system temporary analytic workspace. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-04941 : required operating system patch needs to be applied
  • ora-16114 : applying DDL transaction with commit SCN string
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-39203 : Partition selection is not supported over a network link.
  • ora-09804 : Class conversion from binary to ORACLE failed.
  • ora-14156 : invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
  • ora-12813 : value for PARALLEL or DEGREE must be greater than 0
  • ora-16025 : parameter string contains repeated or conflicting attributes
  • ora-00236 : snapshot operation disallowed: mounted control file is a backup
  • ora-15037 : disk 'string' is smaller than mimimum of string MBs
  • ora-27033 : failed to obtain file size limit
  • ora-09342 : Detached process terminated by Oracle during shutdown abort
  • ora-25256 : consumer cannot be specified with a single-consumer queue or an exception queue
  • ora-19251 : XQ0031 - unsupported query version
  • ora-31635 : unable to establish job resource synchronization
  • ora-12831 : Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
  • ora-19625 : error identifying file string
  • ora-12619 : TNS:unable to grant requested service
  • ora-23416 : table "string"."string" does not contain a primary key constraint
  • ora-01543 : tablespace 'string' already exists
  • ora-32019 : The parameter SPFILE cannot be updated in the server parameter file.
  • 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.