System and method for providing session affinity in a clustered database environment

• US 8,635,185 B2
• Filed: 02/16/2012
• Issued: 01/21/2014
• Est. Priority Date: 06/27/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Somogyi, Alexander, Revanuru, Naresh, Felts, Stephen, Zhou, Tong
• Primary Examiner(s): Badawi, Sherief
• Assistant Examiner(s): HARMON, COURTNEY N
• Application Number:
  US13/398,538
• Publication Number:
  US 20130054516A1
• Time in Patent Office: 705 Days
• Field of Search: 707/609
• US Class Current: 707/613
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• 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/28 Databases characterised by their database models, e.g. relational or object models
• CPC Class Codes: G06F 16/285 Clustering or classification

Abstract

A clustered database environment (e.g. Oracle Real Application Cluster (RAC)) includes multiple database instances that appear as one server. An application server (e.g. WebLogic Server (WLS)) can use a data source (e.g. an Oracle GridLink data source) and connection pools to connect with the clustered database. In accordance with an embodiment, a data source configuration allows for specification of a preferred affinity policy, such as a data affinity, temporal affinity, and/or session or session-based affinity policy. In accordance with an embodiment, the system includes a number of features that improve application connectivity in the clustered database environment, including a select-only case for application continuity, wherein an application-independent infrastructure, e.g. implemented within a Java Database Connectivity (JDBC) driver, enables recovery of work from an application perspective and masks system communications, hardware failures and hangs.

Claims

1. A system for supporting affinity in a data source and clustered database environment, comprising:

a computer, including a computer readable medium and one or more microprocessors;

a clustered database system, and a notification service associated with a plurality of database instances in the clustered database system, wherein the notification service broadcasts notifications that describe state changes in the clustered database;

an application server environment on the computer, including one or more application server instances therein, wherein each said application server instance is associated with one or more data sources and one or more connection pools, wherein each said data source is associated with one or more affinity policies, each said affinity policy defining one of a session affinity and a distributed transaction (XA) affinity for that data source, wherein the data sources and connection pools are used to manage connections to the plurality of database instances in the clustered database based on the state changes in the clustered database;

wherein the session affinity is set as a default affinity policy for each said data source, and wherein the session affinity switches to the XA affinity when the each said data source is accessed outside a context of a session;

wherein when the session affinity is triggered for the each said data source, database operations requested by an application during a session are routed to a same said database instance;

wherein the routing to the same said database instance is performed by

storing routing information to an affinity context, and

associating the affinity context with the session using a work context object of the application,

wherein the work context object propagates around the system and is accessible to each of the application requests for the database operations.

2. The system of claim 1, wherein the affinity policy is defined globally across multiple data sources, or individually for each of said multiple data sources.

3. The system of claim 2, wherein at runtime, when the application requests a connection from one of the data sources which has a session affinity policy set, the system makes a callback to get any available context associated with the session, wherein the system then uses the affinity context associated with the session to choose an appropriate connection.

4. The system of claim 3, wherein a servlet container determines from the work context object that the affinity policy is set and retrieves additional information for choosing the appropriate connection.

13. The system of claim 1, wherein the notification service sends affinity information to be replicated across the clustered database.

14. The system of claim 1, wherein keys are extracted from data being used by the application to route client connections to an appropriate server.

15. The system of claim 2, wherein the affinity policy defined globally takes precedence over the affinity policy defined individually.

5. A method for supporting session affinity in a data source and clustered database environment, comprising the steps of:

providing access to a clustered database system, and a notification service associated with a plurality of database instances in the clustered database system, wherein the notification service broadcasts notifications that describe state changes in the clustered database;

providing an application server environment, including one or more application server instances therein, wherein each said application server instance is associated with one or more data sources and one or more connection pools, wherein each said data source is associated with one or more affinity policies, each said affinity policy defining one of a session affinity and a distributed transaction (XA) affinity for that data source, wherein the data sources and connection pools are used to manage connections to the plurality of database instances in the clustered database based on the state changes in the clustered database;

wherein the session affinity is set as a default affinity policy for each said data source, and wherein the session affinity switches to the XA affinity when the each said data source is accessed outside a context of a session;

wherein when the session affinity is triggered for the each said data source, database operations requested by an application during a session are directed to a said same database instances;

wherein the routing to the same said database instance is performed by

storing routing information to an affinity context, and

associating the affinity context with the session using a work context object of the application,

wherein the work context object propagates around the system and is accessible to each of the application requests for the database operations.

6. The method of claim 5, wherein the affinity policy is defined globally across multipe data sources, or individually for each of said multiple data sources.

7. The method of claim 6, wherein at runtime, when the application requests a connection from one of the data sources which has a session affinity policy set, the system makes a callback to get any available context associated with the session, wherein the system then uses the affinity context associated with the session to choose an appropriate connection.

8. The method of claim 7, wherein a servlet container determines from the work context object that the affinity policy is set and retrieves additional information for choosing the appropriate connection.

16. The method of claim 5, wherein the notification service sends affinity information to be replicated across the clustered database.

17. The method of claim 5, further comprising extracting keys from data being used by the application to route client connections to an appropriate server.

18. The method of claim 6, wherein the affinity policy defined globally takes precedence over the affinity policy defined individually.

9. A non-transitory computer readable medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform the steps comprising:

providing access to a clustered database system, and a notification service associated with a plurality of database instances in the clustered database system, wherein the notification service broadcasts notifications that describe state changes in the clustered database;

providing an application server environment, including one or more application server instances therein, wherein each said application server instance is associated with one or more data sources and one or more connection pools, wherein each said data source is associated with one or more affinity policies, each said affinity policy defining one of a session affinity and a distributed transaction (XA) affinity for that data source, wherein the data sources and connection pools are used to manage connections to the plurality of database instances in the clustered database based on the state changes in the clustered database;

wherein the session affinity is set as a default affinity policy for each said data source, and wherein the session affinity switches to the XA affinity when the each said data source is accessed outside a context of a session;

wherein when the session affinity is triggered for the each said data source, database operations requested by an application during a session are directed to a said same database instance;

wherein the routing to the same said database instance is performed by

storing routing information to an affinity context, and

associating the affinity context with the session using a work context object of the application,

wherein the work context object propagates around the system and is accessible to each of the application requests for the database operations.

10. The non-transitory computer readable medium of claim 9, wherein the affinity policy is defined globally across multiple database source, or individually for each of said multiple data sources.

11. The non-transitory computer readable medium of claim 10, wherein at runtime, when the application requests a connection from one of the data sources which has a session affinity policy set, the system makes a callback to get any available context associated with the session, wherein the system then uses the affinity context associated with the session to choose an appropriate connection.

12. The non-transitory computer readable medium of claim 11, wherein a servlet container determines from the work context object that the affinity policy is set and retrieves additional information for choosing the appropriate connection.

19. The non-transitory computer readable medium of claim 9, wherein the notification service sends affinity information to be replicated across the clustered database.

20. The non-transitory computer readable medium of claim 9, wherein the notification service sends affinity information to be replicated across the clustered database.