Hi,
First of all, I have very little DB2 knowledge, so I apologise for anything strange that I might say!
I am working for a client who has a bespoke application that refers to a DB2 database held on an NT server. I believe the version of DB2 being used is 5.2 (yes, very old and out of support, but the client will not upgrade yet). The application is a simple VB front end, which is held on a Citrix server farm. When the front end is launched, the user is prompted for a user name and password, and then the application tries to connect to the database.
The first time the app tries to connect, it takes approximately 15 minutes to connect. If the app is closed and relaunched, connection is immediate. The DSN being used is configured in exactly the same way that is was in a test environment, which worked. The only difference is the location of the servers now, which is as follows.
The NT servers now reside in the same domain as the Citrix servers, and all servers have all the correct DNS settings for name resolution for that domain. This solution was previously tested in different domains. The test Citrix server was in a test domain, and the DB2 NT servers were in a live domain. In this set up, the connection was immediate. Now all of the servers are in the same domain, the connection takes a very long time. I mention domains in a security/authentication perspective, in case this affects how DB2 authenticates users. I have no idea how DB2 handles authentication, and nobody here can tell me either, so it might not even be important.
I realise that there are huge complexities in this, which I can't mention here due to the time it would take! But if anyone can suggest why a DB2 connection would take 15mins at the first attempt, but be 'instant' the second time, I would be very grateful.
I have looked into things like DB2 ACTIVATE DB, but I do not have a user account with the necessary rights, and DB2 PING needs to connect first (which surely will be another 15min wait???).
Regards,
Mark
