This content has been marked as final. Show 2 replies
always commit after executing stored procedures calls that change data in your database. There is no guarantee that after passivation you get the same AM or database connection back. Passivation only keeps state, not data unless changed in the entity cache.
I agree with Frank.
In our application we always commit after calling PL/SQL procedures which performs DML-Statements (insert, update, delete).
Without commits you will - beside the passivation problem - face problems with locked records in the database.
To refresh the values from DB we use the "restore current row after rollback" approach (which is applicable for commit too).