Re: ORA-14403 cursor invalidation detected after getting DML partition lock - lots of retries

An update,
In the end I followed the suggestion of MOS Doc 2057107.1 and changed the code to first insert into a global temporary table and from there into the original target table and this is so far working. I did notice for one run that the all of the child cursors got marked INVALID_UNAUTH and feared for the worst, but the insert completed a few minutes later.

So the problem shows up with DML against an interval partitioned tablle, where the insert (or whatever) is suitably complex and therefore takes a longish time to run and uses parallel query. Of course the title of the Oracle Doc has the word "Complex" in it but no definiton of what that really means. I have noted in the past that Oracle refer to any query with more than one predicate as "complex", since the selectivity is harder to compute. I am currently guessing that the significant point is the use of an interval partitioned table.

Regards
Pete

--
http://www.freelists.org/webpage/oracle-l