Allowing Updates

By default, other users can continue development and update the database while the reorganization is in progress; for example, other users can still modify (that is, edit and compile) methods in the development environment). However, you can specify that updates are not allowed during the reorganization. Updates are not allowed when the FastBuildBTreeCollections parameter in the [JadeReorg] section of the JADE initialization file is set to true.

Changes that would require a reorganization cannot be made while a reorganization is in progress (for example, adding or removing properties).

Instances of classes being reorganized can be created, updated, or deleted prior to the transition.

If concurrent updates are disallowed, reorganization cannot be initiated if there are any outstanding transactions. If other users are using the JADE database, you must wait until all transactions are complete before you initiate the reorganization. No transactions can be started when a reorganization that disallows concurrent updates is in progress.

If updates are disabled while the reorganization is in progress, the reorganization must initiate the transition. Any error occurring during the reorganization results in the reorganization being aborted; that is, the reorganization cannot be restarted.