Efficient integration between an external workload manager and an RDBMS

• US 8,583,604 B2
• Filed: 02/19/2009
• Issued: 11/12/2013
• Est. Priority Date: 02/19/2009
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bird, Paul Miller, Dillenberger, Donna N Eng, Hulber, Mark Francis, Manners, David Cree, Wong, Francis, Yocom, Peter B.
• Primary Examiner(s): Vy, Hung T
• Assistant Examiner(s): PHAN, TUANKHANH D
• Application Number:
  US12/388,721
• Publication Number:
  US 20100211555A1
• Time in Patent Office: 1,727 Days
• Field of Search: 707/615, 707/655, 707/620, 707/609, 707/689, 705/4
• US Class Current: 707/687
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409

Abstract

According to one embodiment of the present invention, a system, method and computer program product is provided for integrating an external workload manager with a database system. The method according to one embodiment includes a method comprises: receiving a request in a database component, the request including a cross component token; starting a new unit of work in workload management software in the database component, in response to the request; determining, from a cross component workload management unit, a transaction class and a synchronization code using the database component; finding an internal workload in the workload management software that matches the transaction class and the synchronization code of the cross component workload management unit; and using the matching internal workload for the new unit of work.

Claims

1. A method comprising:

receiving a request in a database component, said request including a cross component token;

starting a new unit of work in workload management software in said database component, in response to said request;

determining, from a cross component workload management unit, a transaction class and a synchronization code using said database component;

finding an internal workload in said workload management software that matches said transaction class and said synchronization code of said cross component workload management unit;

acquiring information for workload management software classifications;

generating internal workload classifications that correspond to the workload management software classifications;

mapping the request to internal workload classifications to process the request;

using said matching internal workload for said new unit of work;

removing, via an autonomous daemon, stale workloads in which related transaction classes are at least one of no longer existing and having been modified and synchronization codes are at least one of having become old and not found; and

on a periodic basis, performing checking of a cleanup list at a catalog node, said performing comprising attempting to delete all workloads using a synchronization code, until said cleanup list is empty.

2. The method according to claim 1 further comprising, if said finding does not find an internal workload that matches said transaction class and said synchronization code, performing a cleanup process.

3. The method according to claim 2 wherein said cleanup process comprises, checking a local database partition cleanup list to determine if cleanup is signaled for said synchronization code, and if not, sending said request to a catalog node and adding said request to a local cleanup list.

4. The method according to claim 3 further comprising adding said request to a central cleanup list.

5. The method according to claim 1 further comprising, if said finding does not find an internal workload that matches said transaction class and said synchronization code, performing a discovery process.

6. The method according to claim 5 wherein said discovery process comprises:

checking a local database partition discovery list to determine if there is an existing entry, and if not, sending said request to a catalog node and adding said request to a local discovery list.

7. The method according to claim 6 further comprising adding said request to a central discovery list.

8. The method according to claim 1 further comprising, on a periodic basis, performing checking of a discovery list at a catalog node, said performing comprising:

determining transaction class and service call association information from said cross component workload management unit; and

deleting said synchronization code if said synchronization code is old or is not found.

9. The method according to claim 1 wherein said database component is a relational database management system.

10. The method according to claim 1 wherein said cross component workload management unit is an Enterprise Workload Management (EWLM) system.

11. A method comprising:

receiving a request in a relational database management system, said relational database management system having internal workload management software, wherein said request includes an external workload management system token;

starting a new unit of work in said internal workload management software in said relational database management system;

said relational database management system contacting an external workload management system to determine an external workload management system transaction class and synchronization code;

said relational database management system finding an internal workload in said internal workload management software that matches said transaction class and said synchronization code of said external workload management system;

said relational database acquiring information for workload management software classifications;

said relational database generating internal workload classifications that correspond to the workload management software classifications;

said relational database mapping the request to internal workload classifications to process the request;

said relational database management system using said matching internal workload for said new unit of work;

said relational database management system removing, via an autonomous daemon, stale workloads in which related transaction classes are at least one of no longer existing and having been modified and synchronization codes are at least one of having become old and not found; and

on a periodic basis, said relational database management system performing checking of a cleanup list at a catalog node, said performing comprising attempting to delete all workloads using a synchronization code, until said cleanup list is empty.

12. The method according to claim 11 further comprising:

discovering when said request represents a new external workload management classification.

13. The method according to claim 11 further comprising automatically acquiring information on new external workload management system classifications;

and

creating internal workload classifications corresponding to said new external workload management system classification.

14. The method according to claim 11 further comprising mapping said request to an internal workload management classification and to an external workload management system mapping.

15. The A method according to claim 11 wherein said relational database management system shares management of said request with said external workload management system.

16. A system comprising:

a processor;

a relational database management system coupled to the processor;

internal workload management software within said relational database management system and executable in the processor;

an external workload management system;

an autonomous daemon;

said relational database management system contacting an external workload management system to determine an external workload management system transaction class and synchronization code;

said internal workload management software receiving an incoming request which has been classified by said external workload management system, analyzing said request to determine said classification of said request, acquiring information for workload management software classifications, generating internal workload classifications that correspond to the workload management software classifications, and mapping the request to internal workload classifications to process the request;

said autonomous daemon removing stale workloads in which related transaction classes are at least one of no longer existing and having been modified and synchronization codes are at least one of having become old and not found; and

on a periodic basis, said relational database management system performing checking of a cleanup list at a catalog node, said performing comprising attempting to delete all workloads using a synchronization code, until said cleanup list is empty.

17. The system according to claim 16 further comprising means for mapping said determined classification of said request to a classification in said internal workload management software.

18. The system according to claim 16 wherein said relational database system comprises DB2 for Linux, Unix and Windows.

19. The system according to claim 16 wherein said external workload management system comprises an Enterprise Workload Management (EWLM) system.

20. A computer program product for integrating an external workload manager and a database system, said computer program product including a non- transitory computer readable medium for causing a computer to implement a method, the method comprising:

receiving a request in a database component, said request including a cross component token;

starting a new unit of work in workload management software in said database component;

determining, from a cross component workload management unit, a transaction class and a synchronization code using said database component;

finding an internal workload in said workload management software that matches said transaction class and said synchronization code of said cross component workload management unit;

acquiring information for workload management software classifications;

generating internal workload classifications that correspond to the workload management software classifications;

mapping the request to internal workload classifications to process the request;

using said matching internal workload for said new unit of work;

removing, via an autonomous daemon, stale workloads in which related transaction classes are at least one of no longer existing and having been modified and synchronization codes are at least one of having become old and not found; and

on a periodic basis, performing checking of a cleanup list at a catalog node, said performing comprising attempting to delete all workloads using a synchronization code, until said cleanup list is empty.

21. The computer program product according to claim 20, wherein, if said finding does not find an internal workload that matches said transaction class and said synchronization code, said computer usable code is further configured to perform a cleanup process.

22. The computer program product according to claim 20 wherein, if said finding does not find an internal workload that matches said transaction class and said synchronization code, said computer usable code is further configured to perform a discovery process.

23. The computer program product according to claim 20 wherein said computer usable code is further configured to, on a periodic basis, perform checking a discovery list at a catalog node, said performing comprising:

determining transaction class and service call association information from said cross component workload management unit; and

deleting said synchronization code if said synchronization code is old or is not found.