Product Documentation

c-treeACE V10.0 Update Guide

Previous Topic

Next Topic

Transaction Processing

Independent Parallel Transactions

Independent Parallel Transactions

The ability was added to perform a unique type of transaction. This special case feature is an extension to traditional database transaction processing. After you “begin” a transaction (Transaction A), and perform operations, you may now “begin” what we call an Independent Parallel Transaction (Transaction B). When this secondary transaction is committed or aborted, only the operations performed within it are affected. Operations performed within the primary transaction (Transaction A) retain their traditional scope.

This allows you to perform a transaction that is not necessarily part of the atomicity requirements of the primary transaction. If the primary transaction is aborted, the Independent Parallel Transaction will not be reverted. One could also abort the secondary transaction as a clever technique to clean up and remove temp files created by it.

For more information, see Independent Parallel Transactions.

Automatic Recovery

Advances in Automatic Recovery ensuring integrity of your data include:

  • Improved Performance - A number of improvements to the performance of Automatic Recovery are included in this release.
  • Redirecting filenames during automatic recovery - c-treeACE now supports a file originating in one directory structure to be repositioned into another directory location during automatic recovery.
  • Automatic Recovery Details - Automatic Recovery is used to bring transaction controlled c-tree data and index files back to a consistent state in the event of an unplanned server outage. The recovery process occurs over several phases. Various details of these phases can now be observed with the RECOVER_DETAILS YES server configuration option.
  • Additional Recovery Logging - c-treeACE recovery has been further modified to enhance the logging of details with additional messages specifying phase and progress during the automatic recovery process. Index recomposition can frequently be a phase that takes the longest amount of recovery time. As it is useful to know the proceedings of this phase, specific messages are now output describing the status of this phase, and the index member involved as it occurs.

For more information, see Auto Recovery.

Additional enhancements to Transaction Processing include:

  • Global transaction number threshold warnings
  • Increased number of SAVEPOINTS
  • Prevent excessive accumulation of transaction logs
  • Avoid overlapping Checkpoints
  • Deferred Transaction File Number Assignment
  • And many more...

TOCIndex