Rebuild Utility GUI Reference
This section describes the objects on the Rebuild utility graphical user interface (GUI).
File Options Screen
This screen allows you to add files to the rebuild list.
Figure 39 Rebuild Utility File Selection
GUI Object
Description
Related Information
Selected files
The data and dictionary files listed for rebuilding according to your selections using the Add button.
To rebuild a file or files
Add button
Adds a data or dictionary file to the list of files to be rebuilt.
To rebuild a file or files
Remove button
Removes the selected data or dictionary file in the list.
To rebuild a file or files
Clear button
Clears the entire list of selected data and dictionary files.
To rebuild a file or files
Rebuild Options Screen
This screen allows you to select the options for rebuilding files.
Figure 40 Rebuild Utility File Options
GUI Object
Description
Related Information
System Data
Specifies whether you want Rebuild to create a System Data key in the file.
System data is necessary for transaction durability logging.
Specifies whether the file is rebuilt with System Data or System and Key Data. The MicroKernel cannot perform logging for a file without system data when no user-defined unique key exists.
To rebuild a file or files
Page Compression
Specifies if you want page compression for the file. The choices are on (yes), off (no), and “keep existing.” Keep existing retains whatever page compression the file contains, if any.
Page compression requires a file format of 9.5 or newer.
Record and Page Compression
Record Compression
Specifies if you want record compression for the file. The choices are on (yes), off (no), and “keep existing.” Keep existing retains whatever record compression the file contains, if any.
Record and Page Compression.
Continue on Error
Determines whether the Rebuild utility continues if it encounters an error during the rebuild process. If you select Yes, the utility continues with the next file even if an error occurs. The utility notifies you of non-MicroKernel data files or other errors but continues rebuilding data files. If you select No, the utility halts the rebuild if it encounters an error.

This option is useful if you have specified wildcard characters for the rebuilt files.
To rebuild a file or files
Save Settings on Exit
Saves the current values in this dialog box for use in subsequent Rebuild sessions.
To rebuild a file or files
Key Number
Specifies the key by which the utility reads when rebuilding a file. If you specify NONE for this option, the utility clones the files, drops the indexes, copies the records into the new files, and rebuilds the indexes. Because this method is faster and creates smaller files than specifying a key number, use it whenever possible.

This method may create a new file in which the records are in a different physical order than in the original file.

If you specify a key number, the utility clones and copies the files without dropping and replacing indexes. While this method is slower than specifying NONE, it is available in case you do not want to rebuild your indexes.
•
To rebuild a file or files
•
Key Attributes in PSQL Programmer's Guide.
File Format
Previous, the Rebuild utility built the file version based on the Create File Version configuration setting.
This Rebuild utility allows you to specify the file version type independent of that setting.
To rebuild a file or files
Page Size
Specifies the page size (in bytes) of the new files. Choose either EXISTING, Optimal (disk space), Optimal (data access), or a size in bytes. If you select EXISTING, the utility uses the existing page size. The utility changes the page size if the original size does not work.
For example, assume you have a v5.x file with a page size of 1,024 and 24 keys. Because Btrieve 6.0 and later supports only 23 keys for a page size of 1,024, the utility automatically selects a new page size for the file and writes an informative message to the status file.
•
To rebuild a file or files
•
For optimizing for data access, see Optimizing the Rebuild Process
•
For optimizing for disk space, see Choosing a Page Size in PSQL Programmer's Guide.
Output Path
Specifies an alternate location for the rebuilt files. (The default location is the current directory.) You must specify a directory that already exists.

This option lets you rebuild large files on a different server. The MicroKernel and its communications components must be loaded on the server that contains the rebuilt files. Do not use wildcard characters in the path.

If the Output Directory location is different than the original file’s location, the original file is not deleted during the rebuild. If the output directory is the same as the original file, the original file is deleted upon completion of the rebuild.
DefaultDB w/ DB security: Cannot rebuild outside DB’s file locations in Maintain Named Databases
To rebuild a file or files
Log File
Specifies a location for the rebuild log file. (The default location is the current working directory.) Do not use wildcard characters in the path.
•
To rebuild a file or files
•
Log File
Rebuild Progress Screen
This screen allows you to see the rebuild progress and to view the log file after the rebuild process completes.
Figure 41 Rebuild Utility Progress Screen
GUI Object
Description
Related Information
Message area
Displays the information about the file being rebuilt, or a summary of the operations if rebuilding has completed.
Log File
View Log File
Allows you to see information about the rebuild process for each file. Click View Log File to display the rebuild log using your default text viewer.
Log File