Re: Oracle NEXTVAL Best Practice

Frederik Soete


Just a WAG... Physical transactions would be separate, wouldn't they? So what if your upper batch task has instead a deferred transaction, begin at group prefix, and the lower batch task has within active or nested transaction, but it is still executed (I assume) before the upper statement is finally committed? Does grouping all of those related SQL statements into one 'huge' transaction have the desired effect? I do not know Oracle SQL, but am just brainstorming...


Op 16 aug. 2017 18:35 schreef "Steven Blank" <sgblank@...>:

Addendum to this,

The aforementioned batch task is being called from within another batch task's Group Prefix logic unit, and in which Transaction mode is Physical, Begin at a Group level. I subsequently have changed the above batch task to Physical-None, still no luck.

I'm thinking about making the above batch task a parallel task, so it would be called from outside the active transaction, but clearly I'm just throwing shit against the wall now to see if anything sticks.


Steve Blank

Join { to automatically receive all group messages.