Monitoring business transaction failures involving database procedure calls

• US 9,652,353 B2
• Filed: 11/20/2014
• Issued: 05/16/2017
• Est. Priority Date: 10/15/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Kapur, Kunal
• Primary Examiner(s): TRUONG, LOAN
• Application Number:
  US14/548,980
• Publication Number:
  US 20150106348A1
• Time in Patent Office: 908 Days
• CPC Class Codes: G06F 11/3089 Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents software debugging using additional hardware using a specific debug interface G06F11/3656; performance evaluation by tracing or monitoring G06F11/3466
• CPC Class Codes: G06F 11/3404 for parallel or distributed programming
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/36 Preventing errors by testing or debugging software
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/865 Monitoring of software
• CPC Class Codes: G06F 2201/87 Monitoring of transactions

Abstract

Systems, methods, and other embodiments associated with modifying applications and monitoring exceptions are described. In one embodiment, a computer implemented method searches an executable code for code representing a database procedure call within the executable code. At a location in the executable code prior to the database procedure call, exception capturing code is inserted into the executable code that is configured to cause information to be collected about an exception when the exception occurs during execution of the database procedure call. After the database procedure call, termination code is inserted in the executable code, wherein the termination code is configured to terminate the collection of the information caused by the exception capturing code.

Claims

1. A non-transitory computer-readable medium with stored computer-executable instructions that when executed by a computer cause the computer to perform a method, the instructions comprising instructions configured for:

searching an executable code, using at least hardware of the computer, for code representing a database procedure call within the executable code;

at a location in the executable code prior to the database procedure call, inserting into the executable code an exception capturing code that is configured to cause information to be collected about an exception when the exception occurs during execution of the database procedure call; and

inserting termination code after the database procedure call in the executable code, wherein the termination code is configured to terminate the collection of the information caused by the exception capturing code.

2. The non-transitory computer-readable medium of claim 1, wherein the instructions for inserting the exception capturing code include instructions that when executed by the computer cause the computer to transform the executable code to include an exception capturing function;

and

wherein the exception capturing code is code that calls a remote program and causes the remote program to collect the information relating to the exception during execution of the database procedure call.

3. The non-transitory computer-readable medium of claim 1, further comprising instructions that when executed by the computer cause the computer to assign an identifier for the database procedure call, wherein the identifier is used to correlate the database procedure call with the collected business transaction information about the exception.

4. The non-transitory computer-readable medium of claim 1, wherein the computer-executable instructions that when executed by the computer cause the computer to search for the code representing the database procedure call by searching for a Procedural Language/Structured Query Language (PL/SQL) block of code, and wherein the instructions are configured to search for and identify the Procedural Language/Structured Query Language (PL/SQL) blocks in the executable code.

5. The non-transitory computer-readable medium of claim 4, wherein the instructions when executed by the computer cause the computer to search for and identify a selected type of the Procedural Language/Structured Query Language (PL/SQL) blocks in the executable code.

6. The non-transitory computer-readable medium of claim 1, further comprising instructions that when executed by the computer cause the computer to load the executable code into a memory for execution, wherein the loading is performed prior to the searching.

7. The non-transitory computer-readable medium of claim 1, wherein the exception capturing code is in an executable form and is inserted into the executable code.

8. The non-transitory computer-readable medium of claim 1, wherein the instructions that when executed by the computer cause the computer to search is performed by the computer, which is a first computing device, and the searching is performed on the executable code that is loaded on a second computing device remote from the first computing device.

9. The non-transitory computer-readable medium of claim 1, further comprising instructions that when executed by the computer cause the computer to insert the exception capturing code into the executable code by bytecode instrumentation.

10. A computer-implemented method, comprising:

loading executable code in a memory for execution;

searching the executable code in the memory for code representing a database procedure call;

prior to executing the database procedure call that is found, initiating exception capturing for collecting and storing data related to an exception that occurs during the execution of the database procedure call; and

upon completion of executing the database procedure call, disabling the exception capturing to cease collecting of the data related to the exception.

11. The method of claim 10, wherein the database procedure call is a Procedural Language/Structured Query Language (PL/SQL) call, and wherein the searching includes searching for one or more Procedural Language/Structured Query Language (PL/SQL) blocks of code in the executable code.

12. The method of claim 10, wherein initiating exception capturing includes inserting exception capturing code into the executable code that is configured to cause the data to be collected relating to the exception when the exception occurs during execution of the database procedure call;

and

wherein the exception capturing code is inserted at a location prior to the database procedure call in the executable code.

13. The method of claim 10, wherein disabling the exception capturing includes inserting termination code after or as part of the database procedure call in the executable code, wherein the termination code is configured to terminate the collection of the data.

14. The method of claim 10, further comprising assigning an identifier for the database procedure call, wherein the identifier is associated with the collected data to correlate the database procedure call with the collected data relating to the exception.

15. The method of claim 10, wherein the searching includes searching for a plurality of database procedure calls in the executable code;

for a database procedure call that is found in the executable code, determining if the database procedure call is associated with a business transaction that is being executed; and

if the database procedure call is associated with a business transaction, then inserting exception capturing code in the executable code for initiating the exception capturing;

otherwise the method further comprises searching for the next database procedure call and repeating.

16. A computing system comprising:

a processor configured to at least execute instructions;

a memory operatively connected to the processor;

reconfiguration logic, implemented with at least hardware of the computing system, configured to;

search executable code for code representing a database procedure call; and

at a location in the executable code where the database procedure call is found, insert into the executable code an exception capturing code that is configured to cause data to be collected about an exception when the exception occurs during execution of the database procedure call; and

transforming the executable code by inserting termination code as part of the database procedure call in the executable code, wherein the termination code is configured to terminate the collection of the data caused by the exception capturing code.

17. The computing system of claim 16, wherein the database procedure call is a Procedural Language/Structured Query Language (PL/SQL) call, and wherein the reconfiguration logic is configured to search for one or more Procedural Language/Structured Query Language (PL/SQL) blocks of code in the executable code that are included in a database procedure call.

18. The computing system of claim 16, wherein the exception capturing code includes code for initiating exception capturing and is configured to cause the data to be collected relating to the exception when the exception occurs during execution of the database procedure call;

and

wherein reconfiguration logic is configured to insert the exception capturing code at the location which is prior to the database procedure call in the executable code.

19. The computing system of claim 16, wherein the termination code includes a call to a remote program, wherein the call includes a parameter that tells the remote program to stop capturing the exception data.

20. The computing system of claim 16, wherein the reconfiguration logic is further configured to assign an identifier for the database procedure call, wherein the identifier is associated with the collected data to correlate the database procedure call with the collected data relating to the exception.