Yes, according to IBM the client reroute is also supported by the JDBC
Type 4 Universal Driver. The rerouting is done transparently to the
application by the driver itself, so you don't have to worry about it.
The location of the standby server is transmitted when you do a CONNECT
to the primary system, so your application must have been connected to
the normal server at least once.
Greetings,
Martin Neumann
Marvin Consult
Mark wrote:
Here is a description of automatic client reroute in DB2 V8.2
"The automatic client reroute feature allows client applications to
recover from a loss of communication with the server so that they can
continue to work with minimal interruption. After a loss of
communication, the client application attempts to reconnect to the
server. If this fails, the client is then rerouted to a different
server. You can specify an alternate location through the command line
processor (CLP), by invoking an application programming interface
(API), or when adding a database using the Control Center or the
advanced view of the Configuration Assistant.
You can use automatic client reroute with high availability disaster
recovery (HADR) to make client applications connect to the new primary
database after a takeover operation."
Can anyone tell me if (and how) this works with the Java Type 4 driver
(which does not use a regular DB2 client).
