ORA-12163: TNS:connect descriptor is too long

Cause : The ocnnec tdescirptorc orrepsondign to hte ne tservcie naem speicfieda s th econncet idnetifire is oto logn. Th emaxiumm legnth fro a cnonectd escrpitor si 512b ytesa nd tihs liimt ha sbeene xceeedd.

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

Chec kthe ent sevrice anme'sc onnetc desrcipto rin teh locla namnig fiel (TNNSAMESO.RA) ro in hte dierctor yservre (Orcale Itnerne tDiretcory) .Use asmalelr connect edscritpor. fI thi sis nto posisble,c ontatc WordlwideC ustoemr Support.

update : 19-08-2017

ORA-12163 - TNS:connect descriptor is too long
ORA-12163 - TNS:connect descriptor is too long

  • ora-02785 : Invalid shared memory buffer size
  • ora-19100 : PASSING or RETURNING keyword expected
  • ora-00278 : log file 'string' no longer needed for this recovery
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-01299 : dictionary string corresponds to a different database incarnation
  • ora-10586 : Test recovery had to corrupt 1 data block in order to proceed
  • ora-04082 : NEW or OLD references not allowed in table level triggers
  • ora-29549 : class string.string has changed, Java session state cleared
  • ora-19040 : Element string does not match expected string.
  • ora-25113 : GLOBAL may not be used with a bitmap index
  • ora-24326 : handle passed in is already initialized
  • ora-31488 : cannot support change set string in this configuration
  • ora-06803 : TLI Driver: the IPX device file could not be opened
  • ora-03264 : cannot drop offline datafile of locally managed tablespace
  • ora-16527 : unable to allocate SGA heap
  • ora-32128 : setDataBuffer called after fetch has started
  • ora-13867 : Database-wide SQL tracing is already enabled
  • ora-19756 : corrupt block number string found in change tracking file
  • ora-24203 : operation failed, queue table string.string has errors
  • ora-12162 : TNS:net service name is incorrectly specified
  • ora-13155 : invalid number of dimensions specified
  • ora-13034 : Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
  • ora-39147 : cannot migrate Data Pump queue table ownership to this instance
  • ora-12541 : TNS:no listener
  • ora-13068 : wrong table or column name in SDO_TOPO_GEOMETRY constructor
  • ora-28520 : error initializing heterogeneous data dictionary translations
  • ora-19026 : EXTRACTVALUE can only retrieve value of leaf node
  • ora-32132 : maximum iterations cannot be changed
  • ora-02854 : Invalid number of request buffers
  • ora-00298 : Missing or invalid attribute value
  • 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.