IBM Support

SQL1337N The service "<service-name>" was not found.

Troubleshooting


Problem

You may hit with SQL1337N when connecting to a database, if you have catalogued the remote database using a service name instead of port number.

Symptom

Following error will be seen in this case:

db2diag.log file has entries similar to:

2010-07-06-14.48.35.869000-300 I22006H392 LEVEL: Error
PID : 1940 TID : 2804 PROC : javaw.exe
INSTANCE: DB2 NODE : 000
EDUID : 2804
FUNCTION: DB2 UDB, common communication, sqlcctcpconnr, probe:33
MESSAGE : DIA3221E The service name "db2inst1c" was not found, TCP/IP function "getaddrinfo" error return code = "10109".

db2trace shows something like below:

7796 data DB2 UDB DRDA Communication Manager sqljcCommConnect fnc
(3.3.54.62.0.10)
dip 1940 tid 2804 cpid 25232 node 0 probe 10
bytes 445

Data1 (PD_DB2_TYPE_SQLCA,136) SQLCA:
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1337 sqlerrml: 10
sqlerrmc: db2inst1c
sqlerrp : SQLJCMN
sqlerrd : (1) 0x81360012 (2) 0x00000012 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"DB2 Tools - Troubleshooting","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"9.7;9.5;9.1;10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
01 May 2025

UID

swg21596283

Page Feedback