IBM Support

Slow connection when connecting from a DB2 Windows client.

Question & Answer


Question

When connecting from a DB2 Windows client with an ID which does not exist in the Windows client or the Windows client’s domain, the connection may take a long time.

Cause

By default, a DB2 Windows client would authenticate an ID. If the ID does not exist, the domain will be queried and also its trusted domains. It could take a long time query all trusted domains.

Answer

Cataloging database as authentication set to server stops DB2 Windows client to authenticate. The following is the command to catalog a database as authentication set to server.
db2 catalog db <database name> at node <node name> authentication server

[{"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Connectivity - Other","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.8;9.7;9.5;9.1;10.1;10.5;11.1","Edition":"Enterprise Server;Express;Personal;Personal Developer's;Workgroup Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21450945