System and method for handling backout processing during capture of changed data in an enterprise computer system

• US 6,092,086 A
• Filed: 03/31/1998
• Issued: 07/18/2000
• Est. Priority Date: 03/31/1998
• Status: Expired due to Term

• Current Assignee: Informatica LLC (Informatica, Inc. (California))
• Original Assignee: BMC Software Incorporated (KKR & Co., Inc.)
• Inventors: Mansur, Bruce H., Martin, James L.
• Primary Examiner(s): Amsbury, Wayne
• Application Number:
  US09/052,353
• Time in Patent Office: 840 Days
• Field of Search: 707/1, 707/202, 709/10, 395/600
• US Class Current: 1/1
• 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/275 Synchronous replication
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

An enterprise data movement (EDM) system and method for more intelligently recording changes made to an IMS database. According to the present invention, when an application issues SETS/SETU and ROLS calls during the application'"'"'s unit of work, the EDM system operates to create sub-units of work for identifying changes which correspond to the SETS/SETU and ROLS calls. This allows the EDM system to individually record or monitor the status of these changes, and either discard and/or commit the individual changes within that total application'"'"'s unit of work, depending on the SETS/SETU and ROLS calls received.

Claims

1. A method for handling backout processing during capture of change data in an enterprise computer system, the method comprising:

capturing a plurality of changes made to a source database, wherein the changes are made by an application, wherein the application maintains a unit of work (UOW) for the plurality of changes;

receiving one or more set calls from the application during said receiving said plurality of changes, wherein each of said set calls operates to establish a point in time for backing out subsequent changes;

creating a corresponding sub unit of work value for each of said one or more received set calls, wherein said capturing includes storing changes received after a respective one of said set calls including the corresponding one of said sub unit of work values;

receiving at least one backout call from the application during said receiving said plurality of changes, wherein the at least one backout call corresponds to one of said set calls, wherein the at least one backout call is operable to back out changes made since the corresponding set call was received;

aborting said changes made since the corresponding set call was received in response to receiving the at least one backout call.

2. The method of claim 1, wherein said sub unit of work values are useable to monitor a commit or abort of one or more of said plurality of changes made to the source database.

3. The method of claim 1, wherein said creating the corresponding sub unit of work value for each of said one or more set calls includes storing the sub unit of work values in a table;

wherein said aborting said changes includes marking the sub unit of work value corresponding to said changes as aborted.

4. The method of claim 3, wherein said capturing includes:

examining said table to determine a most current sub unit of work value in response to receiving a change;

storing said change with the most current sub unit of work value.

5. The method of claim 4, wherein said storing said change with the most current sub unit of work value includes creating a change record including said sub unit of work value.

6. The method of claim 3, further comprising:

the application completing, wherein the application completes normally;

examining the table to determine a status of each of the sub unit of work values;

committing changes corresponding to active sub UOW values in response to said examining.

7. The method of claim 6,

wherein said aborting includes creating an end sub-packet for changes corresponding to the respective sub UOW value, wherein the end sub-packet includes an abort flag;

wherein said committing changes comprises creating an end sub-packet for changes corresponding to each of the active sub UOW values, wherein the end sub-packet includes a commit flag.

8. The method of claim 3, further comprising:

determining if any sub unit of work values are active in response to receiving said at least one backout call;

creating a new sub unit of work value in response to receiving said at least one backout call from the application and in response to determining that no sub unit of work values are active;

wherein subsequent changes after said backout call use a most current sub unit of work value in response to determining that one or more sub unit of work values are active.

9. The method of claim 1, further comprising:

providing a recovery token for each of said received set calls;

wherein said at least one backout call includes one of said recovery tokens provided during said providing, wherein said one of said recovery tokens corresponds to one of said received set calls.

10. The method of claim 1, wherein changes received after a respective one of said set calls and prior to a subsequent one of said set calls are stored with the corresponding one of said sub unit of work values.

11. The method of claim 1, further comprising:

receiving a plurality of nested set calls and one or more backout calls, wherein said plurality of nested set calls and said one or more backout calls are interspersed among said plurality of changes;

wherein said sub unit of work values are useable to monitor a commit or abort of each of said plurality of changes.

12. The method of claim 1, wherein the database is an IMS database system;

wherein each of the one or more set calls comprises one of an IMS SETS call or an IMS SETU call;

wherein the at least one backout call comprises an IMS ROLS call.

13. A method for handling backout processing during capture of change data in an enterprise computer system, the method comprising:

receiving a first set call from the application, wherein said first set call operates to establish a point in time for backing out subsequent changes;

receiving one or more first changes made to a source database, wherein the first changes are received after receiving the first set call;

storing said one or more first changes with a first sub unit of work value in response to receiving said one or more first changes, wherein said first sub unit of work value is useable to monitor a commit or abort of said one or more first changes.

14. The method of claim 13, further comprising:

receiving a first backout call from the application after receiving and storing said one or more first changes, wherein said first backout call operates to backout said one or more first changes made since said set call was received;

aborting said one or more first changes in response to receiving said first backout call, wherein said aborting includes analyzing received changes and aborting said one or more first changes having said first sub unit of work value.

15. The method of claim 13, further comprising:

creating said first sub unit of work value in response to receiving said first set call.

16. The method of claim 13, further comprising:

receiving a plurality of changes from the application prior to receiving said first set call;

wherein said first sub unit of work value is not used to monitor a commit or abort of said plurality of changes made prior to receiving said first set call.

17. The method of claim 13,

wherein said receiving said first set call, said receiving said one or more first changes, and said storing said one or more first changes with said first sub unit of work value are performed a plurality of times for a plurality of set calls,

wherein each of said first sub unit of work values are useable to monitor a commit or abort of the corresponding one or more first changes.

18. A method for handling backout processing during capture of change data in an enterprise computer system, the method comprising:

receiving one or more first changes made to a source database, wherein the changes are made by an application, wherein the application maintains a unit of work (UOW) for the changes

capturing said one or more first changes made to the source database;

receiving a set call from the application, wherein said set call operates to establish a point in time for backing out subsequent changes;

receiving one or more second changes made to a source database, wherein the second changes are received after receiving the set call;

storing said one or more second changes with a subset unit of work value in response to receiving said one or more second changes after receiving the set call;

receiving a backout call from the application, wherein said backout call operates to backout changes made since said set call was received;

aborting said one or more second changes in response to receiving said backout call, wherein said aborting includes analyzing received changes and aborting said second changes having said subset unit of work value.

19. A memory media which stores program instructions for handling backout processing during capture of change data in an enterprise computer system, wherein the program instructions implement:

capturing a plurality of changes made to a source database, wherein the changes are made by an application, wherein the application maintains a unit of work (UOW) for the plurality of changes;

receiving one or more set calls from the application during said receiving said plurality of changes, wherein each of said set calls operates to establish a point in time for backing out subsequent changes;

creating a corresponding sub unit of work value for each of said one or more received set calls, wherein said capturing includes storing changes received after a respective one of said set calls including the corresponding one of said sub unit of work values;

receiving at least one backout call from the application during said receiving said plurality of changes, wherein the at least one backout call corresponds to one of said set calls, wherein the at least one backout call is operable to back out changes made since the corresponding set call was received;

aborting said changes made since the corresponding set call was received in response to receiving the at least one backout call.

20. The memory media of claim 19, wherein said sub unit of work values are useable to monitor a commit or abort of one or more of said plurality of changes made to the source database.

21. The memory media of claim 19, wherein said creating the corresponding sub unit of work value for each of said one or more set calls includes storing the sub unit of work values in a table;

wherein said aborting said changes includes marking the sub unit of work value corresponding to said changes as aborted.

22. The memory media of claim 21, wherein said capturing includes:

examining said table to determine a most current sub unit of work value in response to receiving a change;

storing said change with the most current sub unit of work value.

23. The memory media of claim 22, wherein said storing said change with the most current sub unit of work value includes creating a change record including said sub unit of work value.

24. The memory media of claim 23, wherein the application completes normally, wherein the program instructions further implement:

examining the table to determine a status of each of the sub unit of work values;

committing changes corresponding to active sub UOW values in response to said examining.

25. The memory media of claim 24,

wherein said aborting includes creating an end sub-packet for changes corresponding to the respective sub UOW value, wherein the end sub-packet includes an abort flag;

wherein said committing changes comprises creating an end sub-packet for changes corresponding to each of the active sub UOW values, wherein the end sub-packet includes a commit flag.

26. The memory media of claim 21, wherein the program instructions further implement:

determining if any sub unit of work values are active in response to receiving said at least one backout call;

creating a new sub unit of work value in response to receiving said at least one backout call from the application and in response to determining that no sub unit of work values are active;

wherein subsequent changes after said backout call use a most current sub unit of work value in response to determining that one or more sub unit of work values are active.

27. The memory media of claim 19, wherein the program instructions further implement:

providing a recovery token for each of said received set calls;

wherein said at least one backout call includes one of said recovery tokens provided during said providing, wherein said one of said recovery tokens corresponds to one of said received set calls.

28. The memory media of claim 19, wherein changes received after a respective one of said set calls and prior to a subsequent one of said set calls are stored with the corresponding one of said sub unit of work values.

29. The memory media of claim 19, wherein the program instructions further implement:

receiving a plurality of nested set calls and one or more backout calls, wherein said plurality of nested set calls and said one or more backout calls are interspersed among said plurality of changes;

wherein said sub unit of work values are useable to monitor a commit or abort of each of said plurality of changes.

30. The memory media of claim 19, wherein the database is an IMS database system;

wherein each of the one or more set calls comprises one of an IMS SETS call or an IMS SETU call;

wherein the at least one backout call comprises an IMS ROLS call.

31. A memory media which stores program instructions for handling backout processing during capture of change data in an enterprise computer system, wherein the program instructions implement:

receiving a first set call from the application, wherein said first set call operates to establish a point in time for backing out subsequent changes;

receiving one or more first changes made to a source database, wherein the first changes are received after receiving the first set call;

storing said one or more first changes with a first sub unit of work value in response to receiving said one or more first changes, wherein said first sub unit of work value is useable to monitor a commit or abort of said one or more first changes.

32. The memory media of claim 31, wherein the program instructions further implement:

receiving a first backout call from the application after receiving and storing said one or more first changes, wherein said first backout call operates to backout said one or more first changes made since said set call was received;

aborting said one or more first changes in response to receiving said first backout call, wherein said aborting includes analyzing received changes and aborting said one or more first changes having said first sub unit of work value.

33. The memory media of claim 31, wherein the program instructions further implement:

creating said first sub unit of work value in response to receiving said first set call.

34. The memory media of claim 31, wherein the program instructions further implement:

receiving a plurality of changes from the application prior to receiving said first set call;

wherein said first sub unit of work value is not used to monitor a commit or abort of said plurality of changes made prior to receiving said first set call.

35. The memory media of claim 31,

wherein said receiving said first set call, said receiving said one or more first changes, and said storing said one or more first changes with said first sub unit of work value are performed a plurality of times for a plurality of set calls,

wherein each of said first sub unit of work values are useable to monitor a commit or abort of the corresponding one or more first changes.

36. A memory media which stores program instructions for handling backout processing during capture of change data in an enterprise computer system, wherein the program instructions implement:

receiving one or more first changes made to a source database, wherein the changes are made by an application, wherein the application maintains a unit of work (UOW) for the changes

capturing said one or more first changes made to the source database;

receiving a set call from the application, wherein said set call operates to establish a point in time for backing out subsequent changes;

receiving one or more second changes made to a source database, wherein the second changes are received after receiving the set call;

storing said one or more second changes with a subset unit of work value in response to receiving said one or more second changes after receiving the set call;

receiving a backout call from the application, wherein said backout call operates to backout changes made since said set call was received;

aborting said one or more second changes in response to receiving said backout call, wherein said aborting includes analyzing received changes and aborting said second changes having said subset unit of work value.

37. A method for propagating data in an enterprise computer system, the method comprising:

capturing a plurality of changes made to a source database, wherein the changes are made by an application, wherein the application maintains a unit of work (UOW) for the plurality of changes;

propagating each of said plurality of changes to a target database, wherein each change includes a unit of work identifier;

receiving one or more set calls from the application during said capturing said plurality of changes, wherein each of said set calls operates to establish a point in time for backing out subsequent changes; and

creating a corresponding sub unit of work value for each of said one or more received set calls;

wherein said propagating includes propagating changes received after a respective one of said set calls including the corresponding one of said sub unit of work values.

38. The method of claim 37, wherein said sub unit of work values are useable to monitor a commit or abort of one or more of said plurality of changes made to the source database.

39. The method of claim 37, further comprising:

the application completing;

wherein said propagating includes propagating either a commit or abort for any units of work or sub units of work that are active.

40. The method of claim 37

wherein said capturing further includes storing changes received after a respective one of said set calls including the corresponding one of said sub unit of work values.

41. The method of claim 37, further comprising:

receiving at least one backout call from the application during said receiving said plurality of changes, wherein the at least one backout call corresponds to a first set call, wherein the at least one backout call is operable to back out changes made since the first set call was received;

wherein the first set call corresponds to a first sub unit of work; and

propagating an abort message for said changes corresponding to said first sub unit of work, wherein said propagating an abort message operates to abort said changes made since the first set call was received.

42. The method of claim 41, wherein said creating the corresponding sub unit of work value for each of said one or more set calls includes storing the sub unit of work values in a table;

and

wherein said propagating an abort message includes marking the sub unit of work value corresponding to said changes as aborted.

43. The method of claim 42, wherein said capturing includes:

examining said table to determine a most current sub unit of work value in response to receiving a change; and

storing said change with the most current sub unit of work value.

44. The method of claim 43, wherein said storing said change with the most current sub unit of work value includes creating a change record including said sub unit of work value.

45. The method of claim 42, further comprising:

the application completing, wherein the application completes normally;

examining the table to determine a status of each of the sub unit of work values; and

wherein said propagating includes propagating either a commit or abort for any units of work or sub units of work that are active.

46. The method of claim 45,

wherein said propagating includes:

creating an end sub-packet for changes corresponding to an inactive sub UOW value, wherein the end sub-packet includes an abort flag; and

creating an end sub-packet for changes corresponding to an active sub UOW value, wherein the end sub-packet includes a commit flag.

47. The method of claim 41, further comprising:

determining if any sub unit of work values are active in response to receiving said at least one backout call; and

creating a new sub unit of work value in response to receiving said at least one backout call from the application and in response to determining that no sub unit of work values are active;

wherein subsequent changes after said backout call use a most current sub unit of work value in response to determining that one or more sub unit of work values are active.

48. The method of claim 41, further comprising:

receiving a plurality of nested set calls and one or more backout calls, wherein said plurality of nested set calls and said one or more backout calls create a plurality of changes;

wherein said sub unit of work values are useable to monitor a commit or abort of each of said plurality of changes.

49. The method of claim 37, wherein changes received after a respective one of said set calls and prior to a subsequent one of said set calls are stored with the corresponding one of said sub unit of work values.

50. The method of claim 37, wherein the source database is an IMS database system;

wherein each of the one or more set calls comprises one of an IMS SETS call or an IMS SETU call; and

wherein the at least one backout call comprises an IMS ROLS call.

51. A memory media comprising program instructions for propagating data in an enterprise computer system, wherein the program instructions are executable to implement:

capturing a plurality of changes made to a source database, wherein the changes are made by an application, wherein the application maintains a unit of work (UOW) for the plurality of changes;

propagating each of said plurality of changes to a target database, wherein each change includes a unit of work identifier;

receiving one or more set calls from the application during said capturing said plurality of changes, wherein each of said set calls operates to establish a point in time for backing out subsequent changes;

creating a corresponding sub unit of work value for each of said one or more received set calls;

wherein said propagating includes propagating changes received after a respective one of said set calls including the corresponding one of said sub unit of work values.

52. The memory media of claim 51, wherein said sub unit of work values are useable to monitor a commit or abort of one or more of said plurality of changes made to the source database.

53. The memory media of claim 51, wherein the program instructions are further executable to implement:

the application completing;

wherein said propagating includes propagating either a commit or abort for any units of work or sub units of work that are active.

54. The memory media of claim 51,

wherein said capturing further includes storing changes received after a respective one of said set calls including the corresponding one of said sub unit of work values.

55. The memory media of claim 51, wherein the program instructions are further executable to implement:

receiving at least one backout call from the application during said receiving said plurality of changes, wherein the at least one backout call corresponds to a first set call, wherein the at least one backout call is operable to back out changes made since the first set call was received;

wherein the first set call corresponds to a first sub unit of work; and

propagating an abort message for said changes corresponding to said first sub unit of work, wherein said propagating an abort message operates to abort said changes made since the first set call was received.

56. The memory media of claim 55, wherein said creating the corresponding sub unit of work value for each of said one or more set calls includes storing the sub unit of work values in a table;

wherein said propagating an abort message includes marking the sub unit of work value corresponding to said changes as aborted.

57. The memory media of claim 56, wherein said capturing includes:

examining said table to determine a most current sub unit of work value in response to receiving a change; and

storing said change with the most current sub unit of work value.

58. The memory media of claim 57, wherein said storing said change with the most current sub unit of work value includes creating a change record including said sub unit of work value.

59. The memory media of claim 56, wherein the program instructions are further executable to implement:

the application completing, wherein the application completes normally;

examining the table to determine a status of each of the sub unit of work values;

wherein said propagating includes propagating either a commit or abort for any units of work or sub units of work that are active.

60. The memory media of claim 59,

wherein said propagating includes:

creating an end sub-packet for changes corresponding to an inactive sub UOW value, wherein the end sub-packet includes an abort flag;

creating an end sub-packet for changes corresponding to an active sub UOW value, wherein the end sub-packet includes a commit flag.

61. The memory media of claim 55, wherein the program instructions are further executable to implement:

determining if any sub unit of work values are active in response to receiving said at least one backout call;

creating a new sub unit of work value in response to receiving said at least one backout call from the application and in response to determining that no sub unit of work values are active;

wherein subsequent changes after said backout call use a most current sub unit of work value in response to determining that one or more sub unit of work values are active.

62. The memory media of claim 55, further comprising:

receiving a plurality of nested set calls and one or more backout calls, wherein said plurality of nested set calls and said one or more backout calls create a plurality of changes;

wherein said sub unit of work values are useable to monitor a commit or abort of each of said plurality of changes.

63. The memory media of claim 51, wherein changes received after a respective one of said set calls and prior to a subsequent one of said set calls are stored with the corresponding one of said sub unit of work values.

64. The memory media of claim 51, wherein the source database is an IMS database system;

wherein each of the one or more set calls comprises one of an IMS SETS call or an IMS SETU call;

wherein the at least one backout call comprises an IMS ROLS call.