To understand trouble spots using the Engine Trace Utility
Select a trouble spot in the list to reveal and highlight the trouble spot on the tree view. Information about the Trouble Spot appears in the details box.
Interpreting the trouble spots requires knowledge of the triggers and transactions defined for your system. Through the trouble spots list, the Trace Utility can draw attention to places where experience has shown that triggers can unexpectedly halt progress and generate outcome different from what is expected. The trouble spots list does not represent where things went wrong, only where things may not have gone as expected.
A short list of examples:
Trigger controls prevent a trigger from firing more than a defined number of times. The limit might be enforced earlier than expected, or the existence of the trigger limit may have been forgotten.
Rule durations (start and end dates, period modes) might expire, preventing a trigger from firing.
Some triggers can have a reset event that restarts the state of the trigger for that entity. The firing of a reset event can cause a trigger to not fire when expected.
Copyright IBM Corporation 2012. All Rights Reserved.
