Apparatus for highly available transaction recovery for transaction processing systems

• US 7,406,618 B2
• Filed: 01/04/2006
• Issued: 07/29/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/325,028
• Publication Number:
  US 20060129872A1
• Time in Patent Office: 937 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 apparatus, comprising:

a shared storage to store a first transaction log corresponding to a first server and

a second transaction log corresponding to a second server,

an interface to the first server, said interface to the first server is stored in memory;

the first server having a first transaction recovery service to failover migrate from the first server to the second server when the first server fails; and

an interface to the second server, said interface to the second server is stored in memory;

the second server having a second transaction recovery service to coordinate transactions from the first transaction log upon the failover migration of the first transaction recovery service.

2. The transaction recovery apparatus of claim 1 wherein the second server instance is configured to receive more than one transaction recovery service.

3. The transaction recovery apparatus of claim 1 further including an input apparatus, the input apparatus enabling receiving a migrate command to initiate the failover migration.

4. The transaction recovery apparatus as claimed in claim 3 wherein the input apparatus includes an input configured to be used with a Graphical User Interface (GUI), the GUI configured to accept manual input of a migration command.

5. The transaction recovery apparatus as claimed in claim 3 wherein the input apparatus includes a keyboard, the keyboard configured to accept manual input of a migration command entered on a command line.

6. The transaction recovery apparatus as claimed in claim 5 wherein the input apparatus includes a keyboard, the keyboard configured to accept manual input of a migration command by using a JMX MBean.

7. The transaction recovery apparatus of claim 1 wherein the first server instance, the second server instance, and the shared storage reside on a single cluster.

8. The transaction recovery apparatus of claim 1 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.

9. The transaction recovery apparatus of claim 1 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.

10. The transaction recovery apparatus of claim 1 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.

11. The transaction recovery apparatus as claimed in claim 1 further comprising a migratable framework, the migratable framework configured to automatically failover migrate the first transaction recovery service from the first server to the second server.

12. The transaction recovery apparatus as claimed in claim 11 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.

13. The transaction recovery apparatus as claimed in claim 11 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.