By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,159 Members | 1,941 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,159 IT Pros & Developers. It's quick & easy.

Client side alternate server

P: n/a
So I've updated the alternate server on our db server. What do I have
to do in order for a remote db catalog to pick up that remote server?
DB2 won't allow me to update alternate server on the client side. I've
read something about LDAP being involved, but I'm not sure where to
start. Any help?

Thanks,
Chris

Sep 29 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
cb******@gmail.com wrote:
So I've updated the alternate server on our db server. What do I have
to do in order for a remote db catalog to pick up that remote server?
DB2 won't allow me to update alternate server on the client side. I've
read something about LDAP being involved, but I'm not sure where to
start. Any help?

Thanks,
Chris
If you have a type 2 driver, it will pick it up when it connects to the
primary server. If you connect to the remote server, and then type: db2
list db directory, you should see the alternate server information.

When using the type 4 driver, the connection code in the application
must persist the information.

Sep 29 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.