To reorganize classes and database files
Perform one of the following actions to reorganize your current schema when it is marked for reorganization (indicated by a red light).
Click the Schema Needs Reorg toolbar button. When the schema is not marked for reorganization, the toolbar button changes to a green light and bubble help for the button displays Reorg Is Not Required.
Select the Reorg command from the Schema menu and then select the Reorg Schema command from the submenu that is displayed.
If you perform either of these actions when a reorganization is in progress, the progress dialog of the currently executing reorganization is displayed (that is, a new reorganization is not started, as only one reorganization can be in progress at any one time).
The Classes Needing Reorg dialog, shown in the following image, is then displayed, listing all classes in all schemas that require reorganization. The database files and their sizes are also displayed at the end of the list, to enable you to estimate the potential disk requirements and time that the reorganization requires.
If you do not want the reorganization progress dialog displayed during the reorganization, uncheck the Show progress check box. When this is checked (the default value), you can monitor the progress of the reorganization and you can cancel the reorganization at any time. You can close the progress dialog by clicking the close icon at the top right corner in the window title bar. This does not cancel the reorganization.
If you want to wait until the reorganization is complete, check the Wait for reorg to finish check box. By default, this check box is not checked; that is, other work can continue in the JADE development environment during the reorganization. In multiuser mode, you can exit from the JADE development environment and the reorganization continues.
If a reorganization is required before a form and data definition (.ddb
If you do not want to allow other users to continue development and update the database while the reorganization is in progress, uncheck the Allow updates check box. (The Initiate transition check box is then checked if it was unchecked and it is disabled.)
The Allow updates check box is checked by default, to allow updates to proceed up until the reorganization transition is initiated; for example, other users can still modify (that is, edit and compile) methods in the development environment. This check box is disabled and unselected when the
If you do not want the reorganization to initiate the transition, uncheck the Initiate transition check box. For details, see "
When performing a reorganization in production mode, the transition must be initiated in single user mode. For details, see "
If you do not want to perform a replayable reorganization, uncheck the Replayable check box. If archival recovery is enabled (that is, the
Click the Reorg button. Alternatively, click the Cancel button to abandon the reorganization.
The reorganization of all classes and database files in all schemas requiring reorganization is then initiated. After a delay (depending on the number of class instances requiring reorganization), a message box advises you of the reorganization completion status.
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 a reorganization is in progress and you select the Reorg command from the Schema menu, the progress dialog is displayed.
If a schema load or the removal of versioning from a schema is attempted when a reorganization is in progress (regardless of whether the reorganization progress dialog is displayed), the load or version removal fails.
For details about:
Reorganizing all schemas that require reorganization, see "Reorganizing All Schemas that Require Reorganization", in the following section.
Reorganization in a single user, production mode database, see