Suspending and resuming of sessions

• US 9,176,772 B2
• Filed: 02/11/2005
• Issued: 11/03/2015
• Est. Priority Date: 02/11/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Kaluskar, Sanjay, Gollapudi, Sreenivas
• Primary Examiner(s): Ortiz Ditren, Belix M
• Application Number:
  US11/057,043
• Publication Number:
  US 20060184535A1
• Time in Patent Office: 3,917 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 9/4856 resumption being on a different machine, e.g. task migration, virtual machine migration G06F9/5088 takes precedence

Abstract

A session established for an application is suspended from an instance and later resumed on the server or a different server. When a session is suspended, its state is captured and persistently stored as a session image in a data repository, and the session is terminated. When the session is resumed, a new session is established on an instance, the session image of the session to resume is retrieved from the repository and restored to the newly established session. The suspension and resumption of a session may be initiated by an application, which may request the suspension and resumption of a session.

Claims

1. A method comprising:

storing, on a node of a multi-node database server that manages a database, session state of a first database session;

wherein the first database session is a connection established for a client to the multi-node database server;

wherein each node of the multi-node database server executes a database instance;

wherein the session state is not stored at the client;

while the session state of the first database session is stored on the node of the multi-node database server and before a particular database instance that executes on the node of the multi-node database server terminates the first database session;

determining, by the particular database instance, based on at least a portion of the session state of the first database session, whether one or more collection criteria are satisfied;

only if the one or more collection criteria are satisfied, then;

generating a session image of the session state of the first database session;

storing the session image of the first database session;

terminating the first database session;

after terminating the first database session;

establishing a second database session on a particular node of the multi-node database server;

retrieving the session image; and

using the session image to restore the session state of the first database session to the second database session;

wherein the method is performed by one or more computing devices.

2. The method of claim 1, wherein:

storing the session image includes persistently storing the session image in a session repository; and

retrieving the session image includes retrieving the session image from the session repository.

3. The method of claim 1, wherein establishing the second database session on the particular node includes establishing the second database session on the node.

4. The method of claim 1, wherein said node is a first node of the multi-node database server and said particular node is a second node, of the multi-node database server, that is different than said first node.

5. The method of claim 1, wherein determining whether the one or more collection criteria are satisfied includes determining whether the first database session is at a call boundary, wherein the first database session is at a call boundary if the particular database instance has finished executing a call from the client.

6. The method of claim 1, wherein determining whether the one or more collection criteria are satisfied includes determining whether the first database session is at a transaction boundary, wherein the first database session is at a transaction boundary if no active transactions are currently being executed for the first database session.

7. A method comprising:

establishing, with an application, a first database session on a node of a multi-node database server;

wherein the multi-node database server manages a database;

wherein the first database session includes session state;

wherein the session state is not stored on a device upon which the application executes;

while the session state of the first database session is stored on the node of the multi-node database server, receiving, at a particular database instance that executes on the node of the multi-node database server, from the application, a suspend request identifying the first database session;

in response to receiving said suspend request, the particular database instance;

determining, based on at least a portion of the session state of the first database session, whether one or more collection criteria are satisfied;

terminating the first database session only after determining that the one or more collection criteria are satisfied;

wherein the method is performed by one or more computing devices.

8. The method of claim 7, wherein receiving the suspend request is performed in response to end-user input indicating that the first database session may be suspended.

9. The method of claim 7, wherein the suspend request is received from the application when the application determines to suspend the first database session based at least in part on an amount of time the first database session has been unused by the application.

10. The method of claim 7, wherein determining whether the one or more collection criteria are satisfied includes determining whether the first database session is at a call boundary, wherein the first database session is at a call boundary if the particular database instance has finished executing a call from a client.

11. The method of claim 7, wherein determining whether the one or more collection criteria are satisfied includes determining whether the first database session is at a transaction boundary, wherein the first database session is at a transaction boundary if no active transactions are currently being executed for the first database session.

12. The method of claim 7, further comprising:

prior to terminating the first database session;

generating a session image of the session state of the first database session on the particular database instance,

generating a session key that identifies the session image, and

storing the session image of the first database session in association with the session key;

after terminating the first database session, receiving a resume request to resume the first database session, the resume requesting including the session key; and

in response to receiving the resume request;

establishing a second database session on a computer system,

retrieving the session image using the session key, and

using the session image to restore the session state of the first database session within the second database session.

13. The method of claim 12, further comprising:

sending the session key to the application; and

subsequently receiving the resume request from the application.

14. The method of claim 13, wherein:

storing the session image includes persistently storing the session image in a session repository; and

retrieving includes retrieving the session image from the session repository using the session key.

15. The method of claim 12, wherein said node is a first node of the multi-node database server and said computer system on which the second database session is established is a second node, of the multi-node database server, that is different than said first node.

16. The method of claim 12, wherein the resume request is received from the application.

17. One or more non-transitory storage media storing one or more sequences of instructions which, when executed by one or more processors, cause:

storing, on a node of a multi-node database server that manages a database, session state of a first database session;

wherein the first database session is a connection established for a client to the multi-node database server;

wherein each node of the multi-node database server executes a database instance;

wherein the session state is not stored at the client;

while the session state of the first database session is stored on the node of the multi-node database server and before a particular database instance that executes on the node of the multi-node database server terminates the first database session;

determining, by the particular database instance, based at least a portion of the session state of the first database session, whether one or more collection criteria are satisfied;

only if the one or more collection criteria are satisfied;

generating a session image of the session state of the first database session;

storing the session image of the first database session;

terminating the first database session;

after terminating the first database session;

establishing a second database session on a particular node of the multi-node database server;

retrieving the session image; and

using the session image to restore the session state of the first database session to the second database session.

18. The one or more storage media of claim 17, wherein:

storing the session image includes persistently storing the session image in a session repository; and

retrieving the session image includes retrieving the session image from the session repository.

19. The one or more storage media of claim 17, wherein establishing the second database session on the particular node includes establishing the second database session on said node.

20. The one or more storage media of claim 17, wherein said node is a first node of the multi-node database server and said particular node is a second node, of the multi-node database server, that is different than said first node.

21. The one or more storage media of claim 17, wherein determining whether the one or more collection criteria are satisfied includes determining whether the first database session is at a call boundary, wherein the first database session is at a call boundary if the particular database instance has finished executing a call from the client.

22. The one or more storage media of claim 17, wherein determining whether the one or more collection criteria are satisfied includes determining whether the first database session is at a transaction boundary, wherein the first database session is at a transaction boundary if no active transactions are currently being executed for the first database session.

23. One or more non-transitory storage media storing one or more sequences of instructions which, when executed by one or more processors, cause:

establishing, with an application, a first database session on a node of a multi-node database server;

wherein the multi-node database server manages a database;

wherein the first database session includes session state;

wherein the session state is not stored on a device upon which the application executes;

while the session state of the first database session is stored on the node of the multi-node database server, receiving, at a database instance that executes on the node of the multi-node database server, from the application, a suspend request identifying the first database session;

in response to receiving said suspend request, the database instance;

determining, based on at least a portion of the session state of the first database session, whether one or more collection criteria are satisfied;

terminating the first database session only after determining that the one or more collection criteria are satisfied.

24. The one or more storage media of claim 23, wherein receiving the suspend request is performed in response to end-user input indicating that the first database session may be suspended.

25. The one or more storage media of claim 23, wherein receiving the suspend request is performed in response to the application determining to suspend the first database session based at least in part on an amount of time the first database session has been unused by the application.

26. The one or more storage media of claim 23, wherein determining whether the one or more collection criteria are satisfied includes determining whether the first database session is at a call boundary, wherein the first database session is at a call boundary if the database instance has finished executing a call from a client.

27. The one or more storage media of claim 23, wherein determining whether the one or more collection criteria are satisfied includes determining whether the first database session is at a transaction boundary, wherein the first database session is at a transaction boundary if no active transactions are currently being executed for the first database session.

28. The one or more storage media of claim 23, wherein the instructions, when executed by the one or more processors, further cause:

prior to terminating the first database session;

generating a session image of the session state of the first database session on the database instance,

generating a session key that identifies the session image, and

storing the session image of the first database session in association with the session key;

after terminating the first database session, receiving a resume request to resume the first database session, the resume requesting including the session key; and

in response to receiving the resume request;

establishing a second database session on a computer system,

retrieving the session image using the session key, and

using the session image to restore the session state of the first database session within the second database session.

29. The one or more storage media of claim 28, wherein the one or more sequences of instructions include instructions which, when executed by the one or more processors, further cause:

sending the session key to the application; and

subsequently receiving the resume request from the application.

30. The one or more storage media of claim 29, wherein:

storing the session image includes persistently storing the session image in a session repository; and

retrieving the session image includes retrieving the session image from the session repository using the session key.

31. The one or more storage media of claim 28, wherein said node is a first node of the multi-node database server and said computer system on which the second database session is established is a second node, of the multi-node database server, that is different than said first node.

32. The one or more storage media of claim 28, wherein the resume request is received from the application.