Originally posted by DaPi
I would have thought it should be OK in this case since the table being updated is not in the cursor. Have I missed something?

Mind you, you will have a problem sorting out how much has been inserted and commited if it crashes in the middle . . .
Always a difficult point, this, but i don't think it makes any difference -- if the SCN taken as the consistency point for the cursor is not available in the rollback, because committing the changes to the target table allowed the rollback to be overwritten, then a snapshot error would result. Different databases for source and target,no problem -- same database, problem.