This content has been marked as final. Show 1 reply
This is expected behavior. This operation is not allowed primarily to prevent data from potentially changing within a child workspace during a rollback operation. This is the same reason we prevent rollback over an implicit savepoint for a non-CR workspace. If you need to have the rollbackToSP functionality, you cannot currently use a CR workspace.
Instead of creating a savepoint in the parent workspace, have you tried to set auto_commit=>FALSE and rollback the open transaction?