Selected files

The data and dictionary files listed for rebuilding according to your selections using the Add button.

To select data and dictionary files for rebuilding

Add button

Adds a data or dictionary file to the list of files to be rebuilt.

To select data and dictionary files for rebuilding

Remove button

Removes the selected data or dictionary file in the list.

To select data and dictionary files for rebuilding

Clear button

Clears the entire list of selected data and dictionary files.

To select data and dictionary files for rebuilding

System Data

Specify 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 specify rebuild options

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 specify rebuild options

Save Settings on Exit

Saves the current values in this dialog box for use in subsequent Rebuild sessions.

To specify rebuild options

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.

Page Size

Specifies the page size (in bytes) of the new files. Choose either EXISTING, 512, 1024, 2048, 3072, or 4096. 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.

The database engine may ignore the page size specified and automatically upgrade the page size. For example, for the 9.5 file format, the odd page sizes such as 1536 and 3072 are not supported. The database engine automatically upgrades to the next valid page size because the next valid page size is more efficient. For older file formats, the database engine may upgrade the page size based on other conditions.

File Format

Previous, the Rebuild utility built the data and dictionary 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.

Choose 6x, 7x, or 8x for the file version of the rebuilt file.

To specify rebuild options

Output Path

Specifies an alternate location for the rebuilt data and dictionary files. (The default location is the current directory.) You must specify a directory that already exists. The directory also must be on a machine that is running the Pervasive PSQL database engine.

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 specify rebuild options

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.

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