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

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

  • ora-13228 : spatial index create failed due to invalid type
  • ora-13451 : GeoRaster metadata scaling function error
  • ora-12234 : TNS:Redirect to destination
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-07479 : scgcmn: cannot open or convert lock.
  • ora-24339 : cannot set server group name after connecting to server
  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-03248 : Too much of segment creation activity during migration
  • ora-25214 : cannot specify delay or expiration for enqueue to exception queue
  • ora-29905 : method string does not exist in type string.string
  • ora-07242 : slembfn: translation error, unable to translate error file name.
  • ora-12491 : DBHIGH value does not dominate DBLOW
  • ora-21527 : internal OMS driver error
  • ora-02794 : Client unable to get key for shared memory
  • ora-02036 : too many variables to describe with automatic cursor open
  • ora-02456 : The HASH IS column specification must be NUMBER(*,0)
  • ora-07265 : sppst: semop error, unable to increment semaphore.
  • ora-14173 : illegal subpartition-extended table name syntax
  • ora-01589 : must use RESETLOGS or NORESETLOGS option for database open
  • ora-39012 : Client detached before the job started.
  • ora-13915 : Critical byte based free space threshold value is greater than warning threshold value.
  • ora-32146 : Cannot perform operation on a null date
  • ora-40225 : model is currently in use by another process
  • ora-02144 : no option specified for ALTER CLUSTER
  • ora-08232 : smsdes: cannot detach from SGA
  • ora-24007 : invalid value string, MAX_RETRIES should be non-negative integer
  • ora-39024 : wrong schema specified for job
  • ora-36400 : (XSSPROP02) workspace object is not a valid variable name.
  • ora-16820 : Fast-Start Failover observer is no longer observing this database
  • ora-12477 : greatest lower bound resulted in an invalid OS label
  • 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.