In normal circumstances, online reorganizations are audited in the audit trail, as is any change to the DMS II database. Auditing provides the benefit of being able to rebuild through a reorganization, although it does incur a performance overhead. You can choose to perform your online reorganization without auditing.
This choice is defined by the options you select in the Reorganisation Type configuration property, under the Installation category, of the Segment. There are equivalent properties on the Environmental Options screen of the Configure Utility and in the Database Management Utility (DMU). Refer to Transferring and Configuring a System Transferring and Configuring a System and Diagnostic and Management Utilities.
Choosing Audited Reorganizations
To choose audited reorganizations, select the Online Reorg option for the Reorganisation Type Segment configuration property under the Installation category.
Choosing Unaudited Reorganizations
To choose unaudited reorganizations, select one of the following options in the Reorganisation Type Segment configuration property under the Installation category:
ReorgDB
ReorgDB allows essentially uninterrupted user access to the database while a background reorganization is in progress. The reorganization is done on a copy of the database structure and Extended Edition must be set. A significant amount of space might be required
Offline
With the DMS Offline option, reorganizations might be faster, but your database is unavailable for a longer time, and your reorganization is not audited. A backup of your database is not required (but recommended), as a failed reorganization can be restarted. If the reorganization fails for any reason, correct the cause of the failure, and restart the reorganization in full.
Your database undergoing reorganization can be opened in inquiry mode. In either case, your database is not accessible by your application during the reorganization process, because your application always opens the database in update mode.
The Offline NoPostdump option ensures that your reorganization completes without prompting you for a decision on whether you want a dump.
A database that is undergoing an Offline unaudited reorganization can be opened only in inquiry mode. It is therefore not accessible by your application throughout the reorganization process, because your application always opens the database in update mode. (During an audited or ReorgDb reorganization, a database can be used online, although parts might be unavailable at times).
Unaudited Reorganizations and Remote Database (RDB)
When using the Remote Database (RDB) facility:
It is recommended that you enter Online, as auditing is required to transfer database runtime changes to your secondary database.
If you do not enter Online Reorg in the Reorganisation Type configuration property and you are using RDB, you must reclone your secondary database with every reorganization.
If you do not enter Online Reorg in the Reorganisation Type configuration property but you have not chosen to clone your database (by entering N in the Clone DB option on the A Series Configuration Options screen), a warning message is displayed by Builder, the Configure Utility, DMU, or reorganization WFL. This message allows you to continue, if you want to clone your database, or to discontinue the reorganization procedure.
Refer to Remote Database Facility (RDB) for more information on cloning and RDB.