Method and apparatus for increasing database availability

• US 6,480,854 B1
• Filed: 03/27/2000
• Issued: 11/12/2002
• Est. Priority Date: 03/27/2000
• Status: Expired due to Term

• Current Assignee: Advanced Micro Devices, Inc.
• Original Assignee: Advanced Micro Devices, Inc.
• Inventors: Gross, Danny B., Conboy, Michael R.
• Primary Examiner(s): Coby, Frantz
• Application Number:
  US09/536,501
• Time in Patent Office: 960 Days
• Field of Search: 707/3, 707/103, 707/10
• US Class Current: 1/1
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching

Abstract

A computer system includes a first database, a second database, and a data handler. The data handler is adapted to receive a database request, issue a first request to the first database, and issue a second request to the second database. The first and second requests are based on the database request. The data handler is further adapted to receive a first response from the first database, receive a second response from the second database, and ignore one of the first and second responses. A method for increasing database availability includes receiving a database request; issuing a first request to a first database; issuing a second request to a second database, the first and second requests being based on the database request; receiving a first response from the first database; receiving a second response from the second database; and ignoring one of the first and second responses.

Claims

1. A computer system, comprising:

a first database;

a second database, the second database being synchronized with the first database; and

a data handler adapted to receive a database request, issue a first request to the first database, issue a second request to the second database, the first and second requests being identical and based on the database request, receive a first response from the first database, receive a second response from the second database, and ignore one of the first and second responses.

2. The computer system of claim 1, wherein the data handler is adapted to identify one of the first and second databases as failed in response to not receiving one of the first and second responses.

3. The computer system of claim 2, wherein the data handler is adapted to ignore any subsequent responses from the failed one of the first and second databases.

4. The computer system of claim 2, wherein the data handler is adapted to determine a return of the failed one of the first and second databases and update the returned one of the first and second databases.

5. The computer system of claim 4, further comprising a restoration queue, wherein the data handler is adapted to store subsequent requests in the restoration queue.

6. The system of claim 5, wherein the data handler is adapted to read the requests stored in the restoration queue and issue corresponding requests to the returned one of the first and second databases.

7. The computer system of claim 5, wherein the data handler is adapted to read the requests stored in the restoration queue and issue corresponding requests to the returned one of the first and second databases.

8. The computer system of claim 2, wherein the data handler is adapted to ignore any subsequent responses from the failed one of the first and second databases until receiving a message indicating the operability of the failed one of the first and second databases.

9. The computer system of claim 1, further comprising:

a first computer adapted to host the data handler;

a second computer adapted to host the first database; and

a third computer adapted to host the second database.

10. The method of claim 2, further comprising ignoring any subsequent responses from the failed one of the first and second databases until receiving a message indicating the operability of the failed one of the first and second databases.

11. A computer system, comprising:

a message bus;

a first computer adapted to issue a database request on the message bus;

a first database server coupled to the bus and adapted to host a first database;

a second database server coupled to the bus and adapted to host a second database, the second database being synchronized with the first database; and

a data handler coupled to the bus and adapted to receive the database request, issue a first request to the first database, issue a second request to the second database, the first and second requests being identical and based on the database request, receive a first response from the first database, receive a second response from the second database, forward one of the first and second responses to the first computer, and ignore the other of the first and second responses.

12. The computer system of claim 11, wherein the data handler is adapted to identify one of the first and second databases as failed in response to not receiving one of the first and second responses.

13. The system of claim 12, wherein the data handler is adapted to ignore any subsequent responses from the failed one of the first and second databases.

14. The system of claim 12, wherein the data handler is adapted to determine a return of the failed one of the first and second databases and update the returned one of the first and second databases.

15. The system of claim 14, further comprising a restoration queue, wherein the data handler is adapted to store subsequent requests in the restoration queue.

16. The system of claim 12, wherein the data handler is adapted to ignore any subsequent responses from the failed one of the first and second databases until receiving a message indicating the operability of the failed one of the first and second databases.

17. The system of claim 11, further comprising a third computer adapted to host the data handler.

18. A method for increasing database availability, comprising:

receiving a database request;

issuing a first request to a first database;

issuing a second request to a second database, the second database being synchronized with the first database and the first and second requests being identical and based on the database request;

receiving a first response from the first database;

receiving a second response from the second database; and

ignoring one of the first and second responses.

19. The method of claim 18, further comprising identifying one of the first and second databases as failed in response to not receiving one of the first and second responses.

20. The method of claim 19, further comprising ignoring any subsequent responses from the failed one of the first and second databases.

21. The method of claim 19, further comprising:

determining a return of the failed one of the first and second databases; and

updating the returned one of the first and second databases.

22. The method of claim 21, further comprising storing subsequent database requests in a restoration queue.

23. The method of claim 22, further comprising:

reading the database requests stored in the restoration queue; and

issuing corresponding requests to the returned one of the first and second databases.

24. A program storage device, comprising:

program instructions, that when executed by a processing device perform a method for increasing database availability, the method comprising;

receiving a database request;

issuing a first request to a first database;

issuing a second request to a second database, the second database being synchronized with the first database and the first and second requests being identical and based on the database request;

receiving a first response from the first database;

receiving a second response from the second database; and

ignoring one of the first and second responses.

25. A computer system, comprising:

a first database;

a second database;

means for receiving a database request;

means for issuing a first request to the first database;

means for issuing a second request to the second database, the second database being synchronized with the first database and the first and second requests being identical and based on the database request;

means for receiving a first response from the first database;

means for receiving a second response from the second database; and

means for ignoring one of the first and second responses.