What db2 version you are using and on what platform??
There was a bug which was solved in UDB Version 8.1 FixPak 9.
http://www-1.ibm.com/support/docview.wss?uid=swg1JR20763
Error description
Slow connect times might be experienced when connecting from a
DB2 UDB Version 8.1 FixPak 7a Windows client in a Windows Domain
environment to either a DB2 UDB Version 8 server or a z/OS
server. This problem is caused by a call to the Windows API
LookupAccountName on the client, which is done to determine the
user ID on the connect statement. In certain circumstances, this
call can take a long time to complete, because an entire domain
might be searched. In FixPaks 7a and 8, this is done even if
authentication is set to SERVER. In previous FixPaks, this API
would only be called if authentication was set to CLIENT or not
specified. Starting in FixPak 9, the Windows API will again only
be called when authentication is set to CLIENT or not specified.
Local fix
Problem summary
Users Affected: Windows clients running DB2 UDB Version 8.1 FP7
and FP8
Problem Description: Slow connections from V8 fp7a client to
z/OS or LUW servers due to call to Windows API on client even
if authentication is set to server.
Problem Summary: Slow connections from V8 fp7a client to z/OS or
LUW servers due to call to Windows API on client even if
authentication is set to server.
Problem conclusion
The complete fix (JR20763) for this problem first appears in DB2
UDB Version 8.1 FixPak 9.
The fix needs to be applied to the DB2 Client machine.
--Rahul Singh
-----Original Message-----
From: DANIEL CALLAHAN [mailto:db2udbdba-ezmlmshield-x61042183.[Email address protected]
Sent: Wednesday, August 30, 2006 9:44 PM
To: LazyDBA Discussion
Subject: Re: connecting to a db.
Activate the database first and also make sure that the client
authentication is "SERVER"
"pavan"
<db2udbdba-ezmlms
hield-x68247630.x To
[Email Address Removed] "LazyDBA Discussion"
a.com> <[Email address protected]
cc
08/30/2006 11:38
AM Subject
connecting to a db.
HI all,
There is a brand new database on our test server with lots of data on it.
When I issue connect command to this db, it takes more time to connect
than other dbs on the same server.
What factors might need tuning to make sure that the time is optimal to
connect ? There are no others users connecting to this db as of now; so, no
of connections is not an issue that might affect the timing. any help ?
thanks.
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
DB2 & UDB email list listserv db2-l LazyDBA home page