SYSTEM AND METHOD FOR SUPPORTING RESOURCE MANAGER (RM) INSTANCE AWARENESS IN A TRANSACTIONAL ENVIRONMENT

• US 20150309837A1
• Filed: 12/31/2014
• Published: 10/29/2015
• Est. Priority Date: 04/28/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Shen, Xugang, Zhang, Qingsheng, Little, Todd J., Jin, Yongshun
• Granted Patent: US 9,542,220 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/467 Transactional memory G06F9/528 takes precedence
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A system and method can support transaction processing in a transactional environment. A transactional server operates to receive resource manager (RM) instance information from a data source that is associated with one or more RM instances, wherein the received instance information allows the transactional server to be aware of which RM instance that the transactional server is currently connected to. Furthermore, the transactional server operates to save the received instance information into one or more tables that are associated with the transactional server. Then, the transactional server can process a global transaction based on the instance information saved in the one or more tables.

Claims

1. A method for supporting transaction processing in a transactional environment, comprising:

receiving, via a transactional server, resource manager (RM) instance information from a data source that is associated with one or more RM instances, wherein the received instance information allows the transactional server to be aware of which RM instance that the transactional server is currently connected to;

saving the received instance information into one or more tables that are associated with the transactional server; and

allowing the transactional server to process a global transaction based on the instance information saved in the one or more tables.

2. The method of claim 1, further comprising:

storing said one or more tables in a shared memory that is accessible by multiple transactional servers.

3. The method of claim 1, further comprising:

registering a call back operation with the RM, wherein the transactional server operated to retrieve the instance information from the RM when the call back operation is triggered.

4. The method of claim 3, further comprising:

allowing the call back operation to be registered statically or dynamically.

5. The method of claim 3, further comprising:

storing the received instance information in a context, and

enabling a flag, which indicates the receiving of the instance information.

6. The method of claim 5, further comprising:

checking the flag at one or more check points while performing the transaction, and

updating the instance information saved in the one or more tables when the instance information is updated.

7. The method of claim 1, further comprising:

allowing said one or more tables to include at least one of

a RM table, which stores one or more unique database names,

an instance table, which stores one or more instance names, and

a service table, which stores one or more database service names.

8. The method of claim 7, further comprising:

allowing said one or more tables to include a server table, which contains one or more server table entries.

9. The method of claim 8, further comprising:

allowing each said server table entry to contain an instance identifier (ID), which is associated with the RM instance that the transactional server is currently connected to.

10. The method of claim 9, further comprising:

allowing each said instance ID to be an integer with multiple sections.

11. A system for supporting transaction processing in a transactional environment, comprising:

one or more microprocessors;

a transactional server, running on the one or more microprocessors, wherein the transactional server operates to perform the steps comprising

receiving resource manager (RM) instance information from a data source that is associated with one or more RM instances, wherein the received instance information allows the transactional server to be aware of which RM instance that the transactional server is currently connected to;

saving the received instance information into one or more tables that are associated with the transactional server; and

processing a global transaction based on the instance information saved in the one or more tables.

12. The system according to claim 11, wherein:

the transactional server operates to store said one or more tables in a shared memory that is accessible by multiple transactional servers.

13. The system according to claim 11, wherein:

the transactional server operates to register a call back operation with the RM, wherein the transactional server operated to retrieve the instance information from the RM when the call back operation is triggered.

14. The system according to claim 13, wherein:

the call back operation is adaptive to be registered statically or dynamically.

15. The system according to claim 13, wherein:

the transactional server operates to

store the received instance information in a context, and

enable a flag, which indicates the receiving of the instance information.

16. The system according to claim 15, wherein:

the transactional server operates to

check the flag at one or more check points while performing the transaction, and

update the instance information saved in the one or more tables when the instance information is updated.

17. The system according to claim 11, wherein:

said one or more tables includes at least one of

a RM table, which stores one or more unique database names,

an instance table, which stores one or more instance names, and

a service table, which stores one or more database service names.

18. The system according to claim 17, wherein:

said one or more tables includes a server table, which contains one or more server table entries.

19. The system according to claim 18, wherein:

each said server table entry contains an instance ID, which is associated with the RM instance that the transactional server is currently connected to, and wherein said instance ID to be an integer with multiple sections.

20. A non-transitory machine readable storage medium having instructions stored thereon that when executed cause a system to perform the steps comprising:

receiving, via a transactional server, resource manager (RM) instance information from a data source that is associated with one or more RM instances, wherein the received instance information allows the transactional server to be aware of which RM instance that the transactional server is currently connected to;

saving the received instance information into one or more tables that are associated with the transactional server; and

allowing the transactional server to process a global transaction based on the instance information saved in the one or more tables.