Anand wrote:Step 2 was a ROLLBACK. If there were any pending transactions at that time, the ROLLBACK would have cancelled them. So, if you didn't get another error that the ROLLBACK itself failed, then the changes must have been committed already, in step 1.
SP2-00642 occurred at the time of the commitment of data.
Then, although the rollback was input, SQLPlus was forced to terminate.
And it connected again after that and data was checked, the renewal of data was in the situation (finishing of a commitment). It reflected the commit.
In this case,the following flow has been executed my customer
1. SP2-XXX error occured during executing commit.
2. Executed rollback.
3. Shutdown SQl*Plus forcefully
4. Confirmed that commit has been done after re-connect
Could someone tell on which timing commitment had happened? Was the timing of 1 committed or did the commitment start implicitly in forced termination of 2 and 3?