Browse Prior Art Database

A method to define an alternate server for Automatic Client Reroute

IP.com Disclosure Number: IPCOM000028707D
Original Publication Date: 2004-May-27
Included in the Prior Art Database: 2004-May-27
Document File: 1 page(s) / 97K

Publishing Venue

IBM

Abstract

A method to define an alternate server for Automatic Client Reroute

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 67% of the total text.

Page 1 of 1

A method to define an alternate server for Automatic Client Reroute

This disclosure is to introduce a method to define an alternate server for Automatic Client Reroute.

Whenever a server crashes, each client that is connected to that server gets a communication error which terminates the connection leading to an application error. In cases where availability is important the user will either have a redundant setup or will fail the server over to a standby node. In either case, the client code should attempt to re-establish the connection to either the original server which may be running on a failover node (IP address fails over as well), or to an alternate server. This disclosure will describe a method to define an alternate server for Automatic Client Reroute.

This disclosure describes a method to specify an alternate server for Automatic Client Reroute. The DB2 "UPDATE ALTERNATE SERVER FOR DATABASE" command will be used to specify an alternate server for a database alias in DB2 UDB server. By using this command, database administrators could easily define the alternate server location on a particular database for DB2 UDB server. The command syntax and an example will be provided below. In order to specify the alternate server uniquely regardless of any clients, the alternate server location has to be specified at server side. By doing so, the alternate server will be centralized, all of the connections to the same database alias will use the same alternate ser...