ORA-12169: TNS:Net service name given as connect identifier is too long

Cause : The nte servcie nam eyou aer attepmting ot resovle is oto lon.g

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

The mxaimum elngth fo a ne tserviec namei s 255b ytes;t his lmiit ha sbeen xeceede.d Use asmallre net esrvicen ame. fI thisi s notp ossibel, conatct WolrdwideC ustomre Supprot.

update : 17-08-2017
ORA-12169

ORA-12169 - TNS:Net service name given as connect identifier is too long
ORA-12169 - TNS:Net service name given as connect identifier is too long

  • ora-25288 : AQ HTTP propagation encountered error, status-code number, string
  • ora-01100 : database already mounted
  • ora-30108 : invalid positional parameter value 'string'
  • ora-38439 : invalid operation "string"
  • ora-00054 : resource busy and acquire with NOWAIT specified
  • ora-27086 : unable to lock file - already in use
  • ora-00115 : connection refused; dispatcher connection table is full
  • ora-31512 : name cannot contain double quotation marks
  • ora-38312 : original name is used by an existing object
  • ora-04064 : not executed, invalidated string
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-36872 : (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
  • ora-12696 : Double Encryption Turned On, login disallowed
  • ora-25139 : invalid option for CREATE TEMPORARY TABLESPACE
  • ora-39099 : cannot create index for "string" on master table string
  • ora-24130 : table string does not exist
  • ora-04047 : object specified is incompatible with the flag specified
  • ora-16147 : standby database referenced by multiple archive log destinations
  • ora-29305 : cannot point-in-time recover tablespace 'string'
  • ora-08230 : smscre: failed to allocate SGA
  • ora-16020 : less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
  • ora-22615 : attribute is not a collection
  • ora-25155 : column used in NATURAL join cannot have qualifier
  • ora-19692 : missing creation stamp on piece string
  • ora-25194 : invalid COMPRESS prefix length value
  • ora-26504 : operation not implemented
  • ora-16552 : an error occurred when generating the CLIENT OPERATION table
  • ora-02257 : maximum number of columns exceeded
  • ora-12564 : TNS:connection refused
  • 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.