System for highly available transaction recovery for transaction processing systems

• US 7,380,155 B2
• Filed: 02/12/2007
• Issued: 05/27/2008
• Est. Priority Date: 02/22/2002
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Somogyi, Alexander J., Fung, Priscilla C.
• Primary Examiner(s): Wilson; Yolanda L
• Application Number:
  US11/673,727
• Publication Number:
  US 20070136393A1
• Time in Patent Office: 470 Days
• Field of Search: None
• US Class Current: 714/4.11
• CPC Class Codes: G06F 11/1662 the resynchronized component or unit being a persistent storage device re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence
• CPC Class Codes: H04L 1/22 using redundant apparatus to increase reliability
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A highly available transaction recovery service migration system in accordance with one embodiment of the present invention implements a server'"'"'s Transaction Recovery Service (TRS) as a migratable service. In one embodiment of the present invention, the TRS is a server instance or software module implemented in JAVA. The TRS migrates to an available server that resides in the same cluster as the failed server. The migrated TRS obtains the TLOG of the failed server, reads the transaction log, and performs transaction recovery on behalf of the failed server. The migration may occur manually or automatically on a migratable services framework. The TRS of the failed server migrates back in a fail back operation once the failed primary server is restarted. Failback operation may occur whether recovery is completed or not. This expedites recovery and improves availability of the failed server thereby preserving the efficiency of the network and other servers.

Claims

1. A transaction recovery system comprising:

a first server;

said first server having a memory;

said memory of said first server comprising;

a first server instance having transaction recovery functionality, the first server instance owning a first transaction log;

a second server;

said second server having a memory;

said memory of said second server comprising;

a second server instance having transaction recovery functionality, the second server instance owning a second transaction log; and

a shared memory, the first transaction log and the second transaction log residing on the shared memory, wherein normally the first server instance coordinates at least one transaction from the first transaction log and wherein, upon the failure of the first server instance, the second server instance coordinates the at least one transaction from the first transaction log.

2. The transaction recovery system of claim 1, wherein the second server instance coordinates one or more transactions from the second transaction log, and wherein, upon failure of the second server instance, the first server instance coordinates the one or more transactions from the second transaction log.

3. The transaction recovery system of claims 1, wherein the first server instance has a first transaction recovery service that is migrated to the second server instance.

4. The transaction recovery system of claim 3, further including an input apparatus, the input apparatus operable to allow a user to input a migrate command to initiate the failover migration.

5. The transaction recovery system of claim 3, wherein the first transaction recovery service is configured to be moved from the first server instance to the second server instance and activated on the second server instance.

6. The transaction recovery system of claim 3, wherein the first transaction recovery service is configured to failback migrate from the second server instance to the first server instance upon detecting the startup of the server instance startup.

7. The transaction recovery system of claim 6, wherein the first transaction recovery service is configured to be deactivated, moved from the second server instance to the first server instance, and activated on the first server instance.

8. The transaction recovery system of claim 1, further comprising a migratable framework and a transaction recovery service, the first server instance and the second server instance configured to operate in conjunction with the migratable framework.

9. The transaction recovery system as claimed in claim 8, wherein the migratable framework is configured to automatically failover migrate a first transaction recovery service from the first server instance to the second server instance.

10. The transaction recovery system as claimed in claim 9, wherein the migratable framework is configured to automatically failback migrate the first transaction recovery service from the second server to the first server when the second server has completed coordinating transactions from the first transaction log.

11. The transaction recovery system as claimed in claim 9, wherein the migratable framework is configured to automatically failback migrate the first transaction recovery service from the second server to the first server when the first server has restarted.

12. The transaction recovery system of claim 1, wherein the first server instance, the second server instance, and the shared memory reside on a single cluster.