Connections Fail Reporting ORA-12169: TNS:Net service name given as connect identifier is too long
(Doc ID 361843.1)
Last updated on JANUARY 22, 2020
Applies to:Oracle Net Services - Version 220.127.116.11.0 to 10.2.0.1.0 [Release 8.1.7 to 10.2]
Business Intelligence Server Enterprise Edition - Version 18.104.22.168.1 to 22.214.171.124.1 [Release 11g]
Information in this document applies to any platform.
Connections to database, over Oracle Net fail reporting error code :
ORA-12169: TNS:Net service name given as connect identifier is too long.
or eg. tnsping may fail with:
TNS-3505: Failed to resolve name
ORA-12169 can be reported in a error stack, similar to following, if stored procedure, database link is failing :
ORA-03113: end-of-file on communication channel
ORA-01591: lock held by in-doubt distributed transaction 3.16.62978
ORA-12169: TNS:Net service name given as connect identifier is too long
An Oracle Net client trace of the failure may show the following symptoms, but is not limited to these examples.
Local naming resolution, (TNSNAMES.ORA) failure to read file 100% correctly:
[16-OCT-2010 01:06:23:655] nnftmlf_make_local_addrfile: construction of local names file failed
[16-OCT-2010 01:06:23:655] nnftmlf_make_local_addrfile: ex
dump of the entry showing address with white spaces:
That is white spaces after second port and delay.
(PORT = 1526)) )
(DELAY =5)) ) )
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document