SYSTEM AND METHOD FOR PERSISTING TRANSACTION RECORDS IN A TRANSACTIONAL MIDDLEWARE MACHINE ENVIRONMENT

• US 20130086419A1
• Filed: 03/07/2012
• Published: 04/04/2013
• Est. Priority Date: 09/29/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Little, Todd, Lv, Xianzheng, Li, Xiangdong
• Granted Patent: US 9,110,851 B2
• Time in Patent Office: Days
• US Class Current: 714/16
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2043 where the redundant components share a common memory address space
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 2201/80 Database-specific techniques

Abstract

A transactional system can utilize the distributed storage and high availability (HA) capability provided by a clustered database to support easy and feasible disaster recovery. The transactional middleware machine environment comprises one or more transactional application servers associated with a transaction. The one or more transactional application servers operate to persist transactional log information associated with the transaction in a database that connects with said one or more transactional application servers at a local site. The database at the local site operates to replicate the persisted transactional log information to a remote database at a remote site. The remote database allows a different transactional application server at the remote site to recover the persisted transactional log information and complete the transaction, when a disaster disables the local site.

Claims

1. A system for supporting disaster recovery in a transactional middleware machine environment, comprising:

one or more transactional application servers associated with a transaction, wherein said one or more transactional application servers operate to persist transactional log information associated with the transaction to a database that connects with said one or more transactional application servers at a local site, and

wherein the database operates to replicate the persisted transactional log information from a local database server at the local site to a remote database server at a remote site, and wherein the remote database allows a different transactional application server at the remote site to recover the persisted transactional log information and complete the transaction, when a disaster disables the local site.

2. The system of claim 1, wherein said one or more transactional application servers reuse an existing database connection to the local database server.

3. The system of claim 1, wherein the transactional log information can be written into a transactional log file.

4. The system of claim 3, wherein the transactional log file is supported in a distributed file system.

5. The system of claim 3, wherein the transactional log information in the transactional log file is synchronized on a recovery site.

6. The system of claim 1, wherein the transaction is a two-phase transaction.

7. The system of claim 6, wherein the transactional log information contains persist state of a transaction manger after successfully committing a first phase of the two-phase transaction.

8. The system of claim 1, wherein the transactional log information is based on a map of a transactional file system and is maintained in a transactional log record.

9. The system of claim 8, wherein the map of the transactional file system is created using a global transaction and the transactional log record is opened when a transaction process is booted.

10. The system of claim 1, wherein the transactional log information contains information for multiple transactional domains.

11. A method for supporting disaster recovery in a transactional middleware machine environment, comprising:

persisting, via one or more transactional application servers, transactional log information associated with a transaction into a database that connects with said one or more transactional application servers at a local site;

replicating, via the database, the persisted transactional log information from a local database server at the local site to a remote database server at a remote site; and

allowing a different transactional application server at the remote site to recover the persisted transactional log information from the remote database server and complete the transaction, when a disaster disables the local site.

12. The method of claim 11, further comprising allowing said one or more transactional application servers to reuse an existing database connection to the local database server.

13. The method of claim 11, further comprising writing the transactional log information into a transactional log file.

14. The method of claim 13, further comprising supporting the transactional log file in a distributed file system.

15. The method of claim 13, further comprising synchronizing the transactional log information in the transactional log file on a recovery site.

16. The method of claim 11, further comprising allowing the transaction to be a two-phase transaction.

17. The method of claim 16, further comprising allowing the transactional log information to contain persist state of a transaction manger after successfully committing a first phase of the two-phase transaction.

18. The method of claim 11, further comprising allowing the transactional log information to be based on a map of a transactional file system and maintaining the transactional log information in a transactional log record.

19. The method of claim 18, further comprising creating the map of the transactional file system using a global transaction and opening the transactional log record when a transaction process is booted.

20. The method of claim 11, further comprising allowing the transactional log information to contain information for multiple transactional domains.