At times a large transaction may be broken down into smaller logical units for the purpose of rolling back a part of the transaction if needed. Such units are marked by the keyword “SAVEPOINT”. This results in partial rollback of the transaction. This solution delves on how Shareplex handles the transaction when such transaction is meant to be ignored by Capture with the use of SHAREPLEX_IGNORE_TRANS feature and when that transaction results in a partial rollback due to the use of “SAVEPOINT” option. The question assumes significance when large transactions meant to be ignored by Capture have been rolled back only partially due to the presence of SAVEPOINTs.
é necessário estar conectado e ter um contrato de manutenção atual para visualizar os artigos de conhecimento premium.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center