ORACLE REWIND: METADATA-DRIVEN UNDO

• US 20130117238A1
• Filed: 11/18/2011
• Published: 05/09/2013
• Est. Priority Date: 11/03/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Gower, Stefan
• Granted Patent: US 8,484,166 B2
• Time in Patent Office: Days
• US Class Current: 707/684
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence
• CPC Class Codes: G06F 2201/80 Database-specific techniques

Abstract

Metadata-driven undo is described. In an embodiment, a metadata repository stores metadata that is associated with operations. Attributes associated with each operation are also stored in the metadata. Each operation is associated with an undolet that includes instructions for generating undo entries for operations of a particular operation type. Undo log entries are generated using the metadata and the undolet when a request is intercepted that includes an undoable operation. When an undo command is issued, the instructions in the undo log that are associated with a particular business transaction are executed to “rewind” the transaction.

Claims

1. A system, comprising:

one or more processors;

a computer-readable non-transitory storage media;

a metadata repository that stores metadata associated with a plurality of operations, wherein each operation is associated with an operation type, wherein the metadata associated with each operation identifies at least;

a) one or more attributes associated with that operation, and b) an undolet associated with the operation type of the corresponding operation, wherein the undolet includes instructions for generating undo entries;

undo logic configured to c) generate one or more entries in an undo log based at least in part on the metadata in the metadata repository and the undolet, wherein a first entry in the undo log is based on a first operation in a first request that is intercepted by the system and that is a request to change the value of a first object on a target system from a second value to a third value, and includes a first attribute value for a first attribute associated with the operation, and d) in response to intercepting the first request, generate a second request to the target system to retrieve the second value from the target system before the second value is changed in response to the first request.

3. The system of claim 1, wherein the first attribute value in the first entry in the undo log is identical to the second value, wherein the entry comprises a first instruction which, when executed by the one or more processors, causes the value of the first object to be set to the first attribute value.

4. The system of claim 3, wherein the first entry in the undo log further includes a second instruction which, when executed by the one or more processors, causes the undo logic to determine whether the value of the first object on the target system is identical to the third value, and, in response to determining that the value of the first object on the target system is identical to the third value, execute the instruction,

5. The system of claim 4, wherein the target system is a first target system, and wherein the undo logic is further configured to:

generate a second entry in the undo log based on a second operation in a second request intercepted by the system, wherein the second request is a request to change the value of a second object on a second target system from a fourth value to a fifth value, wherein the second entry includes the fourth value;

wherein the first request and the second request include session-identifying information that associates both the first and second requests with a first session;

wherein the second entry includes a second instruction which, when executed by the one or more processors, causes the value of the second object to be set to the fourth value;

wherein the system is configured to send the first request to the first target system and the second request to the second target system;

wherein the undo logic is configured to cause the first, second, and third instructions to be executed on the one or more processors in response to receiving a third request to perform an undo operation associated with the first session.

6. The system of claim 5, wherein the undo logic is further configured to:

generate a third entry in a second undo log based on a third operation in a third request that is intercepted before the second request and after first request, wherein the third request is a request to change the value of a third object on the first target system, and the third request is associated with a second session;

wherein the undo logic is configured to cause the first, second, and third instructions to be executed on the one or more processors without changing the value of the third object.

7. The system of claim 1, wherein the first operation is a constructor operation, and the first attribute value is the name of the object to be constructed on the target system in response to the first request, wherein the first entry in the undo log includes instructions which, when executed by the one or more processors, cause the object to be removed from the target system.

2. (canceled)

8. A computer-readable non-transitory storage medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform:

maintaining a metadata repository that stores metadata associated with a plurality of operations, wherein each operation is associated with an operation type, wherein the metadata associated with each operation identifies at least;

a) one or more attributes associated with that operation, and b) an undolet associated with the operation type of the corresponding operation, wherein the undolet includes instructions for generating undo entries;

generating one or more entries in an undo log based at least in part on the metadata in the metadata repository and the undolet;

wherein a first entry in the undo log is based on a first operation in an intercepted first request to change the value of a first object on a target system from a second value to a third value, said first request including a first attribute value for a first attribute associated with the operation; and

in response to intercepting the first request, generating a second request to the target system to retrieve the second value from the target system before the second value is changed in response to the first request.

10. The computer-readable non-transitory storage medium of claim 8, wherein the first attribute value in the first entry in the undo log is identical to the second value, wherein the entry comprises a first instruction which, when executed by the one or more processors, causes the value of the first object to be set to the first attribute value.

11. The computer-readable non-transitory storage medium of claim 10, wherein the first entry in the undo log further includes a second instruction which, when executed by the one or more processors, causes undo logic to determine whether the value of the first object on the target system is identical to the third value, and, in response to determining that the value of the first object on the target system is identical to the third value, execute the first instruction.

12. The computer-readable non-transitory storage medium of claim 11, wherein the target system is a first target system, and wherein the instructions further include instructions for:

generating a second entry in the undo log based on a second operation in a second intercepted request, wherein the second request is a request to change the value of a second object on a second target system from a fourth value to a fifth value, wherein the second entry includes the fourth value;

wherein the first request and the second request include session-identifying information that associates both the first and second requests with a first session;

wherein the second entry includes a second instruction which, when executed by the one or more processors, causes the value of the second object to be set to the fourth value;

sending the first request to the first target system and the second request to the second target system;

causing the first, second, and third instructions to be executed on the one or more processors in response to receiving a third request to perform an undo operation associated with the first session.

13. The computer-readable non-transitory storage medium of claim 12, wherein the undo logic is further configured to:

generate a third entry in a second undo log based on a third operation in a third request that is intercepted before the second request and after first request, wherein the third request is a request to change the value of a third object on the first target system, and the third request is associated with a second session;

wherein the undo logic is configured to cause the first, second, and third instructions to be executed on the one or more processors without changing the value of the third object.

14. The computer-readable non-transitory storage medium of claim 8, wherein the first operation is a constructor operation, and the first attribute value is the name of the object to be constructed on the target system in response to the first request, wherein the first entry in the undo log includes instructions which, when executed by the one or more processors, causes the object to be removed from the target system.

9. (canceled)

15. A method, comprising:

maintaining a metadata repository that stores metadata associated with a plurality of operations, wherein each operation is associated with an operation type, wherein the metadata associated with each operation identifies at least;

a) one or more attributes associated with that operation, and b) an undolet associated with the operation type of the corresponding operation, wherein the undolet includes instructions for generating undo entries;

generating one or more entries in an undo log based at least in part on the metadata in the metadata repository and the undolet;

wherein a first entry in the undo log is based on a first operation in an intercepted first request to change the value of a first object on a target system from a second value to a third value, said first request including a first attribute value for a first attribute associated with the operation; and

in response to intercepting the first request, generating a second request to the target system to retrieve the second value from the target system before the second value is changed in response to the first request;

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

17. The method of claim 15, wherein the first attribute value in the first entry in the undo log is identical to the second value, wherein the entry comprises a first instruction which, when executed by the one or more processors, causes the value of the first object to be set to the first attribute value.

18. The method of claim 17, wherein the first entry in the undo log further includes a second instruction which, when executed by the one or more processors, causes undo logic to determine whether the value of the first object on the target system is identical to the third value, and, in response to determining that the value of the first object on the target system is identical to the third value, execute the first instruction.

19. The method of claim 18, wherein the target system is a first target system, and further comprising:

generating a second entry in the undo log based on a second operation in a second intercepted request, wherein the second request is a request to change the value of a second object on a second target system from a fourth value to a fifth value, wherein the second entry includes the fourth value;

wherein the first request and the second request include session-identifying information that associates both the first and second requests with a first session;

wherein the second entry includes second instruction which, when executed by the one or more processors, cause the value of the second object to be set to the fourth value;

sending the first request to the first target system and the second request to the second target system;

causing the first, second, and third instructions to be executed on the one or more processors in response to receiving a third request to perform an undo operation associated with the first session.

20. The method of claim 15, wherein the first operation is a constructor operation, and the first attribute value is the name of the object to be constructed on the target system in response to the first request, wherein the first entry in the undo log includes instructions which, when executed by the one or more processors, cause the object to be removed from the target system.

16. (canceled)