connect to db2 9.5 server slow

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Dan van Ginhoven - 29 Apr 2008 14:48 GMT

Hi!

I have installed a new Db2 V9.5 fp1 Linux 64 bit with a partioned database.

When I connect to the database using DB2Visualizer on Windows, that uses db2jcc, it works OK.

Connecting from DB2 Control Center takes 4-5 minutes, but it connects. Opening a table can take 4-5 minutes too.
Connecting thru a Linux DB2 Client also takes 4-5 minutes, but after that table access seems OK.
I compared dbm cfg with a working db2 server but did'nt find any significant differences.

Where do I start looking? Tried to Google, but did'nt find any obvious answers.
Something with the authentication process?

Mvh
/dg

Reply to this Message

Serge Rielau - 29 Apr 2008 14:58 GMT

> Hi!
>
[quoted text clipped - 8 lines]
> Where do I start looking? Tried to Google, but did'nt find any obvious answers.
> Something with the authentication process?

That's the first place where I would look. Are you using some LDAP
server that DB2 is trying to reach out to? I'm far from being an expert
on thsi but I seem to recall that sometimes the OS tried to reach out to
various authentication services in a specific order. If one of the
remote ones is ahead of the one with the required information these
issues occur.

Cheers
Serge

Signature

Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

Reply to this Message

Dan van Ginhoven - 29 Apr 2008 16:53 GMT

Thanks Serge.
There is no LDAP server, but I suspect that jdbc uses one authentication metod that works,
and that DB2 CC and cCient uses one that times out after 300 seconds and than tries the other method.
But I don't know if this is DB2 or Linux issue, and where to look for a solution.

/dg

> > Hi!
> >
[quoted text clipped - 17 lines]
> Cheers
> Serge

Reply to this Message

Frank Swarbrick - 29 Apr 2008 22:06 GMT

Do you have a firewall blocking access to port 523? It looks like Control
Center first tries to connect to this port, and only later goes to the port
the instance is listening on. So if port 523 is blocked you have a delay
(though not 4 or 5 minutes, in my experience.)

Based on your comment that you have the same issue with a Linux DB2 Client
other than CC makes me think this is *not* the issue, but I just thought I'd
put it out there.

Frank

n 4/29/2008 at 7:48 AM, in message <VGFRj.6709$R_4.5308@newsb.telia.net>,

> Hi!
>
[quoted text clipped - 7 lines]
> Opening a table can take 4-5 minutes too.
> Connecting thru a Linux DB2 Client also takes 4-5 minutes, but after that

> table access seems OK.
> I compared dbm cfg with a working db2 server but did'nt find any
[quoted text clipped - 6 lines]
> Mvh
> /dg

Reply to this Message

Mark A - 30 Apr 2008 00:41 GMT

> Hi!
>
[quoted text clipped - 17 lines]
> Mvh
> /dg

Make sure that your databases are catalogued with "authentication server".

You can check it with "db2 list db directory".

Reply to this Message

Dan van Ginhoven - 30 Apr 2008 19:36 GMT

Hi!

I believe port 523 is open ( but when can you trust what the firewall people say).

I know that Authentication = SERVER (db2 get dbm cfg)

I also measured that the delay is 240 seconds (4 minutes) every time .
I searched for "anything" with a timeout = 240/4 but didn't find one.
Anyone with Linux expertise know of anything with 240 seconds timeout?
db2diag.log is quiet. (Greatly improved readability in 9.5!!!!)

/dg

Reply to this Message