If you have a code structure similar to this:
update t set start_time=systimestamp;
update t set end_time=systimestamp;
-- run some code here that takes anywhere between 0.1 and 2 seconds to
I have some executions of this code, 40 out of 6000 runs, where I end up
with the end_time being a timestamp BEFORE the begin_time and not just a
microsecond or two. 0.4 seconds, 0.6 seconds. A significant amount of time.
This leads me to believe that Oracle somehow fires autonomous transactions
asynchronously or out of order of the code structure?
Before I go off on a digging spree - has anyone seen this before or has an
Oracle 12.1 on *nix.
zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
Visit us at zztat.net | Support our Indiegogo campaign at igg.me/at/zztat |