Electrical computers and digital processing systems: multicomput – Computer-to-computer data routing – Least weight routing
Reexamination Certificate
2002-05-10
2004-04-27
El-Hady, Nabil (Department: 2154)
Electrical computers and digital processing systems: multicomput
Computer-to-computer data routing
Least weight routing
C709S241000, C709S241000, C709S201000, C709S202000, C709S203000, C709S226000, C709S227000, C707S793000, C707S793000, C714S002000, C714S016000
Reexamination Certificate
active
06728747
ABSTRACT:
BACKGROUND AND SUMMARY
A typical client-server database system includes a client, a database server, and a database. The client portion includes two main components, a database application and a client driver interface. The database application issues database language commands, such as SQL (Structured Query Language) commands, and provides an interface to a user through a keyboard, screen, and pointing devices such as a mouse. The client driver interface, on the other hand, provides the connection and communication interface between the client and the database server.
A connection is a communication pathway between a client and a database server and a specific connection between a client and a database server is termed a database session. The database server responds to the database language commands sent from the client by executing database operations for accessing and manipulating a physical database. A logical unit of work that is comprised of one or more database language commands is often referred to as a transaction.
Contained within the database server is the session state data that reflects the current transaction state of the database session. To initiate a database session, a “log on” procedure may be performed to establish a new database session by connecting a client with a database server.
Normally, the database session lasts from the time the user connects until the time the user disconnects or exits the database application. However, if a database session failure occurs, the connection between the client and the database server is lost. Once the database session fails, the user will observe a visible interrupt in his service as access to the database is terminated. To continue accessing the database, the user must reconnect a client to an active database server. This may require human intervention to manually log back onto the system to establish a new database session.
Besides requiring human intervention to manually log back onto the system, the failure of a database session creates other significant problems to the user. Because the logon process creates a new database session, all previous transactions that were not complete at the time of the failure are lost. Thus the user must resubmit all lost transactions once the connection to the database is reestablished.
Based on the foregoing, it is desirable to provide a mechanism for handling the failure of a database session without requiring someone to perform manual reconnection steps. Additionally, it is also desirable for users not to lose session state data on the occurrence of a database session failure.
A method, system, and apparatus is provided for passing a client from a first server to which the client was connected for accessing a resource, to a second server for accessing the resource. While executing, the first server ceases to respond to the client. After the client detects that the first server has ceased to respond to the client, the client is automatically connected with the second server that has access to the resource. After automatically connecting the client, the client accesses the resource through the second server. In one embodiment, the client stores information about the state of the session with the first server so that processing can continue where it left off after the client connects with the second server. The client may be pre-connected to the second server prior to the failure of the first server to reduce the latency caused by switching in response to a failure. The second server may be configured to pre-parse the commands that the client issues to the first server to further reduce the latency associated with switching to the second server.
REFERENCES:
patent: 3444528 (1969-05-01), Lovell et al.
patent: 4868832 (1989-09-01), Marrington et al.
patent: 5157663 (1992-10-01), Major et al.
patent: 5179660 (1993-01-01), Devany et al.
patent: 5247664 (1993-09-01), Thompson et al.
patent: 5535326 (1996-07-01), Baskey
patent: 5544313 (1996-08-01), Shachnai et al.
patent: 5566225 (1996-10-01), Haas
patent: 5566297 (1996-10-01), Devarakonda et al.
patent: 5596720 (1997-01-01), Hamada et al.
patent: 5633999 (1997-05-01), Clowes et al.
patent: 5652908 (1997-07-01), Douglas et al.
patent: 5666479 (1997-09-01), Kashimoto et al.
patent: 5696895 (1997-12-01), Hemphill et al.
patent: 5721918 (1998-02-01), Nilsson et al.
patent: 5734896 (1998-03-01), Rizvi et al.
patent: 5784630 (1998-07-01), Saito et al.
patent: 5796934 (1998-08-01), Bhanot
patent: 5796941 (1998-08-01), Lita
patent: 5796999 (1998-08-01), Azagury
patent: 5819019 (1998-10-01), Nelson
patent: 5832483 (1998-11-01), Barker
patent: 5850507 (1998-12-01), Ngai et al.
patent: 5862362 (1999-01-01), Somasegar et al.
patent: 5867713 (1999-02-01), Shrader et al.
patent: 5870545 (1999-02-01), Davis et al.
patent: 5890963 (1999-04-01), Yen
patent: 5951694 (1999-09-01), Choquier et al.
patent: 6038677 (2000-03-01), Lawlor et al.
patent: 6047323 (2000-04-01), Krause
patent: 6199110 (2001-03-01), Rizvi et al.
Jenkins, Bob, “Hash Functions”, Dr. Dobb's Journal, Sep. 1997, pp. 107-109, 115-116.
“Coda: A Highly Available File System for a Distributed Workstation Environment”, Mahadev Satyanarayanan, IEEE Transactions on Computers, vol. 39, No. 4, pp. 447-459, Apr. 1990.
“Scalable, Secure, and Highly Available Disributed File Access”, Mahadev Satyanarayanan, IEEE Transactions on Computers, vol. 23 5, pp. 9-21, May 1990.
“Distributed Systems, Concepts and Designs”, Coulouris et al., 1994, Adison-Wesley.
“Local Area Network Server Replacement Procedure”, IBM Technical Disclosure Bulletin, Jan. 1995.
“Workload Balancing in a Distributed Environment”, IBM Technical Disclosure Bulletin, Nov. 1995.
“High Availability in Clustered Multimedia Servers”, Renu Tewari et al., (IEEE), Mar. 1996, pp. 645-654.
Bastawala Mehul
Jenkins Robert
Krishnaswamy Srinath
Bingham & McCutchen LLP
El-Hady Nabil
Oracle International Corporation
LandOfFree
Method and system for implementing failover for database... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method and system for implementing failover for database..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method and system for implementing failover for database... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3245875