DB2 slow response on first connection Win 2003

[Steve D]

We are using a UDB 8.1 client on a Windows 2003 server, standard
edition. We are seeing slow connection response times (27 seconds) on
the first attempt and second attempt is great (< 1 second). The
Windows server uses a DSN that points to a Linux server with DB2 on
it.

We see the same problem when we bring up a DB2 command window on the
Windows server and run a "DB2 LIST NODE xxxxx". Takes about 27
seconds and next connect is under 1 second.

We had heard the 27 seconds is loading cache on the first connect?
However it shouldn't take that long.

Has anyone else experienced this type of problem?

[Mark Yudkin]

This is normal documented behaviour, exacerbated by large buffer pools and
poor I/O buffering (Linux). It is also unrelated to W2K3 (although you may
be pre-scanning for LDAP catalogued databases).

Use ACTIVATE DATABASE on the Linux Server. Also consult the documentation
for that command for a description of your scenario.

Check that LDAP is either used, or deactivate its usage.

"Steve D" <st***************@ecolab.com> wrote in message
news:cd*************************@posting.google.co m...

We are using a UDB 8.1 client on a Windows 2003 server, standard
edition. We are seeing slow connection response times (27 seconds) on
the first attempt and second attempt is great (< 1 second). The
Windows server uses a DSN that points to a Linux server with DB2 on
it.

We see the same problem when we bring up a DB2 command window on the
Windows server and run a "DB2 LIST NODE xxxxx". Takes about 27
seconds and next connect is under 1 second.

We had heard the 27 seconds is loading cache on the first connect?
However it shouldn't take that long.

Has anyone else experienced this type of problem?