Users of Transactions
By default, Journal Analyzer proposes to recover transactions by executing reverse transactions under the currently connected user. However, the Impersonate User of Initial Transaction option allows you to impersonate the user under which each transaction had initially been executed.
Note: This option requires that the connected user is the database administrator or has appropriate privileges.
The Impersonate User of Initial Transaction option affects the way the reverse transactions are executed: that is, normally Journal Analyzer recovers multiple transactions by executing the recover statements of all transactions to be undone in a single, global “recover” transaction. This allows, in case of failure at any point in the recover operation, to cancel the whole operation.
However, given that it is not possible to execute in the same transaction different statements under different users, if this option is used, and the initial transactions had not all be executed under the same user, Journal Analyzer must commit (and change the user) before each reverse statement to be executed under a different user than the previous one.
A possible problem in this case is when a reverse statement fails, once other recover statements have already been committed. In this situation, Journal Analyzer proposes to “undo the undo” of the transactions previously undone. However in case of failure of this last operation, you need to manually “repair” this situation (typically by using Journal Analyzer) by completing or canceling the uncompleted operation.