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
"Serge Rielau" <srielau@[EMAIL PROTECTED]
> wrote in message
news:67ons3F2pnrfqU1@[EMAIL PROTECTED]
> Dan van Ginhoven wrote:
> > 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?
> 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
>
> --
> Serge Rielau
> DB2 Solutions Development
> IBM Toronto Lab
|
