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 : 30-04-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-27011 : skgfrd: cannot read from file opened for write
  • ora-29918 : cannot create domain indexes on temporary tables
  • ora-34001 : (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.
  • ora-12419 : null binary label value
  • ora-24369 : required callbacks not registered for one or more bind handles
  • ora-04081 : trigger 'string' already exists
  • ora-39130 : Object type string not imported. Base object name conflicts with the master table
  • ora-19277 : XP0005 - XPath step specifies an item type matching no node: (string)
  • ora-02182 : savepoint name expected
  • ora-31434 : purge is currently running
  • ora-01669 : standby database control file not consistent
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-14277 : tables in EXCHANGE SUBPARTITION must have the same number of columns
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-38604 : FI including & excluding cursor item-id type must match input cursor item-id type
  • ora-12984 : cannot drop partitioning column
  • ora-30180 : argument index is too large
  • ora-38955 : Source platform string not cross platform compliant
  • ora-25444 : invalid ROWID: string for table alias: string
  • ora-02158 : invalid CREATE INDEX option
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-16173 : incompatible archival network connections active
  • ora-07621 : smscre: illegal redo block size
  • ora-13116 : [string]_FACE$ table does not exist
  • ora-06953 : Not enough virtual memory
  • ora-09931 : Unable to open ORACLE password file for reading
  • ora-37060 : (XSMCSESS08) number is not a valid custom member in dimension workspace object.
  • ora-13863 : Statistics aggregation for service(module/action) string is not enabled
  • ora-01633 : Real Application Clusters Option needed for this operation
  • ora-02087 : object locked by another process in same transaction
  • 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.