System and Methods For Temporary Data Management in Shared Disk Cluster

• US 20080086480A1
• Filed: 06/01/2007
• Published: 04/10/2008
• Est. Priority Date: 10/06/2006
• Status: Active Grant

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: Wang, Yanhong, Rathee, Raj K., Srivastava, Ajay K.
• Granted Patent: US 8,156,082 B2
• Time in Patent Office: Days
• US Class Current: 707/10
• 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

Abstract

System and methods for temporary data management in shared disk cluster configurations is described. In one embodiment, a method for managing temporary data storage comprises: creating a global temporary database accessible to all nodes of the cluster on shared storage; creating a local temporary database accessible to only a single node (owner node) of the cluster; providing failure recovery for the global temporary database without providing failure recovery for the local temporary database, so that changes to the global temporary database are transactionally recovered upon failure of a node; binding an application or database login to the local temporary database on the owner node for providing the application with local temporary storage when connected to the owner node; and storing temporary data used by the application or database login in the local temporary database without requiring use of write ahead logging for transactional recovery of the temporary data.

Claims

1. In a shared disk cluster (SDC) database system comprising a plurality of nodes, a method for managing storage of temporary data, the method comprising:

creating a global temporary database on shared storage, said global temporary database comprising a temporary database accessible to all nodes of the cluster;

creating a local temporary database accessible to only a single node (owner node) of the cluster;

providing failure recovery for said global temporary database without providing failure recovery for said local temporary database, so that changes to said global temporary database are transactionally recovered upon failure of a node;

binding an application to the local temporary database on the owner node for providing the application with local temporary storage when the application is connected to the owner node; and

storing temporary data used by the application in the local temporary database without requiring use of write ahead logging for transactional recovery of said temporary data.

2. The method of claim 1, further comprising:

binding a database login to the local temporary database on the owner node for local temporary storage; and

storing temporary data used by the database login in the local temporary database when connected to the owner node;

without requiring use of write ahead logging for transactional recovery of said temporary data.

3. The method of claim 1, wherein said step of creating a local temporary database includes creating the local temporary database on a private device.

4. The method of claim 3, wherein said step of creating the local temporary database on a private device includes using an attribute to indicate that only the owner node has access to the private device.

5. The method of claim 3, wherein said private device comprises a solid state storage disk using random-access memory.

6. The method of claim 1, wherein said step of creating a local temporary database includes creating the local temporary database on a shared device.

7. The method of claim 1, wherein said storing temporary data step includes storing temporary data in the local temporary database on the owner node without requiring synchronization with other nodes of the cluster.

8. The method of claim 1, wherein said storing temporary data step includes storing temporary data in the local temporary database on the owner node without requiring transfer of pages among nodes of the cluster.

9. The method of claim 1, wherein storing temporary data step includes storing temporary data in the local temporary database without use of a cluster wide lock for protecting access to said temporary data from other nodes in the cluster.

10. The method of claim 1, further comprising:

upon failure of a node, transactionally recovering changes made in the global temporary database.

11. The method of claim 1, further comprising:

upon failure of the owner node, discarding changes made in the local temporary database.

12. The method of claim 1, further comprising:

creating one local system temporary database for each node of the cluster.

13. The method of claim 12, wherein a local system temporary database at a given node of the cluster serves as a default local temporary database for such node.

14. The method of claim 1, further comprising:

in response to user input, creating a plurality of local temporary databases at the owner node.

15. The method of claim 14, wherein said binding an application step includes binding an application to a local temporary database selected by the user from the plurality of local temporary databases at the owner node.

16. The method of claim 14, further comprising:

creating a temporary database group; and

adding a local temporary database as a member of the temporary database group.

17. The method of claim 16, wherein said binding an application step includes binding an application to the temporary database group.

18. The method of claim 16, further comprising:

binding a database login to the temporary database group for local temporary storage; and

storing temporary data used by the database login in a member local temporary database of the temporary database group when connected to the owner node, without requiring use of write ahead logging for transactional recovery of said temporary data.

19. A computer-readable medium having processor-executable instructions for performing the method of claim 1.

20. The method of claim 1, further comprising:

downloading a set of processor-executable instructions for performing the method of claim 1.

21. In a shared disk cluster (SDC) database system comprising a plurality of nodes, a system for managing storage of temporary data, the system comprising:

a global temporary database on shared storage, said global temporary database comprising a temporary database accessible to all nodes of the cluster;

a local temporary database accessible to only a single node (owner node) of the cluster and providing storage for temporary data on the owner node;

a module for providing failure recovery for said global temporary database without providing failure recovery for said local temporary database, so that changes to said global temporary database may be transactionally recovered upon failure of a node; and

an application which is bound to the local temporary database and when connected to the owner node uses the local temporary database for storing temporary data without use of write ahead logging for transactional recovery of said temporary data.

22. The system of claim 21, further comprising:

a database login which is bound to the local temporary database and when connected to the owner node uses the local temporary database for storing temporary data without use of write ahead logging for transactional recovery of said temporary data.

23. The system of claim 21, wherein said local temporary database is created on a private device.

24. The system of claim 23, wherein said local temporary database is created on a private device using an attribute to indicate that only the owner node has access to the private device.

25. The system of claim 23, wherein said private device comprises a solid state storage disk using random-access memory.

26. The system of claim 21, wherein said local temporary database is created on a shared device.

27. The system of claim 21, wherein temporary data is stored in the local temporary database on the owner node without requiring synchronization with other nodes of the cluster.

28. The system of claim 21, wherein temporary data is stored in the local temporary database on the owner node without requiring transfer of pages among nodes of the cluster.

29. The system of claim 21, wherein temporary data is stored in the local temporary database without protecting said temporary data with a cluster wide lock.

30. The system of claim 21, wherein said module for providing failure recovery transactionally recovers changes made in the global temporary database upon failure of a node.

31. The system of claim 30, wherein said module for providing failure recovery discards changes made in the local temporary database upon failure of the owner node.

32. The system of claim 21, further comprising:

a local system temporary database at each node of the cluster.

33. The system of claim 32, wherein a local system temporary database at a given node of the cluster serves as a default local temporary database for such node.

34. The system of claim 21, further comprising:

a plurality of additional local temporary databases at the owner node.

35. The system of claim 34, wherein the application is bound to a given local temporary database selected by a user from the plurality of local temporary databases available at the owner node.

36. The system of claim 34, wherein a database login is bound to a given local temporary database selected by a user from the plurality of local temporary databases available at the owner node.

37. The system of claim 36, wherein the database login uses the local temporary database for storing temporary data when connected to the owner node without use of write ahead logging for transactional recovery of said temporary data.

38. The system of claim 34, further comprising:

a temporary database group including a local temporary database as a member.

39. The system of claim 38, wherein the application is bound to the temporary database group for local temporary storage.

40. The system of claim 38, further comprising:

a database login bound to the temporary database group for local temporary storage;

wherein the database login stores temporary data in a member local temporary database of the temporary database group when connected to the owner node without requiring use of write ahead logging for transactional recovery of said temporary data.