Hi Sangamesh Hanumantha Sangamad
We're facing the same issue here with some procedures we use the following code:
INSERT INTO TABLE a ...
EXECUTE IMMEDIATE 'COMMIT';
...
Without this forced commit, it runs fine!
The problem is that our procedure execute several heavy processing steps and we use this insert statement to log between the steps.
Did you overcome this issue somehow?