• Running the Rebuild Utility Interactively---When you run the Rebuild utility interactively, it checks the values you enter to ensure they are within the proper ranges.
• Running the Rebuild Utility from the Command Line---When you use this method, the utility checks your entries and displays messages if the values you entered are not within the proper ranges. With this method, you can specify a command file.

The following sections discuss running the utility using both these methods.

IMPORTANT:  Before running the Rebuild utility, make sure you have unloaded your previous version of Btrieve (as described on Unloading an Earlier Version of NetWare Btrieve), started Btrieve 6.1x (as described in Starting NetWare Btrieve 6.x), and backed up all your data files. Having backup copies ensures against data loss if a power interruption occurs while you are running the utility.

To ensure that your backup is successful, perform any one of the following operations:

• Close all Btrieve files before running the backup utility.
• Use continuous operations.
• Use a backup utility that opens the Btrieve files in exclusive write mode so that other processes can not write to the files. Ensure that the backup utility has exclusive rights to the files.

Running the Rebuild Utility Interactively

• Configuring the Rebuild Utility
• Executing the Rebuild Utility
• Viewing the Rebuild Log File

Configuring the Rebuild Utility

1. After starting Btrieve 6.1x, load the Setup utility by entering the following command at the prompt: load bsetup

   When the Available Options menu appears, select Set Rebuild Configuration to run the Rebuild utility.

   
   

   A warning, shown in Figure 9, appears, indicating you should back up your Btrieve data files before proceeding.

   Figure 9
   Setup: Backup Warning for Rebuild Option
   

   NOTE:  If you do not have current backups, press Esc three times. When the Exit Btrieve Setup? prompt appears, select Yes. Create backups and then return to this utility.

2. Provided you have current backups of your data files, press Esc to advance to the Rebuild Options menu.

   
   

   Figure 10
   Setup: Rebuild Configuration Setup Form Screen
   

3. Select the files you want to rebuild, as follows:

   1. With your cursor at the Files To Be Converted entry, press Enter and then press Insert.

   2. When the list of available volumes appears, highlight the volume you want and press Enter.

      The utility displays the directories available on the selected volume.

   3. Highlight the directory you want and press Enter.

   4. Continue highlighting directories (that is, subdirectories) and pressing Enter until you have reached the one that contains the file or files you want to rebuild. Then press Esc.

   5. Choose the files you want to rebuild, as follows:

      • To specify more than one file, enter the filenames manually, using wildcard characters (* or ?).

        For example, you might enter /*.* to specify all files in the selected directory, or you could enter /*.BTR to specify all files in that directory with the extension .BTR.

      • To specify an individual file, press Enter to list the filenames in the specified directory. Then highlight the filename you want and press Enter to select it. (The input files that are listed are on the local server.)

4. At Output Directory, specify the location you want to use for the rebuilt files, as described in the following steps.

   The default location is the directory you specified for the Files To Be Converted field.

   1. Press Enter.

   2. Either type the server or directory name manually and press Enter, or choose from the list of available directories on the current server by entering a valid path and pressing Insert. To select a directory name from the list, highlight the name and press Enter.

      If you want to store the rebuilt files on a different server, you must type the output server name, volume, and path manually. Then press Enter.

      Do not use wildcard characters in the pathname that specifies the location for the rebuilt files.

      NOTE:   To store rebuilt files on a different server, Btrieve and the Message Router must be loaded on the server where the original data files reside, and the Btrieve and BSPXCOM NLMs must be loaded on the server that will contain the rebuilt files.

      NOTE:  Wherever you store the rebuilt files, you will need enough disk space for the rebuilt files and the temporary files that the utility creates. The utility deletes the temporary files at the end of the conversion process.

   3. After specifying the output directory, use the Down-Arrow key to move to the Page Size field.

5. At Page Size, type the size manually or choose from the list of valid page sizes.

   1. To list the available page sizes, press Enter.

      In this list, the AUTO option (the default) means the utility will choose the optimum page size for the files. The EXISTING option means the utility will use the same page size as that of the original files.

   2. To select a size from the list, highlight it and press Enter.

      NOTE:  When you use the EXISTING option, the utility changes the page size if the original size will not work. For example, assume you have a Btrieve 5.x file with a page size of 1,024 and 24 keys. Since Btrieve 6.x supports only 23 keys for a file of that page size, the utility selects a new page size for the file and displays an informative message on the screen.

6. At Key Number, specify a number between 0 and 23 on which to sort the records, or specify -1 to sort the records in physical order. Press Enter.

   IMPORTANT:  If you are using Scalable SQL, you must specify a key number of 0 when rebuilding the VIEW.DDF file.

7. At Preserve TTS Setting, specify Y or N to indicate whether you want to preserve the Transaction Tracking System (TTS) bit during conversion. Press Enter.

   If you specify Y, the utility preserves the bit. If you specify N (the default), the utility clears the bit when creating Btrieve 6.x files.

8. At Conversion Method, select the conversion method as follows:

   1. Press Enter.

   2. Highlight either PRIMARY (the default) or SECONDARY, and then press Enter.

      IMPORTANT:  If you are using Scalable SQL, you must specify the SECONDARY method when rebuilding the VIEW.DDF file. Be aware that the SECONDARY method may create a 6.x file in which the records are in a different physical order than in the original 5.x file.

      • The PRIMARY method clones the files, drops the indexes, copies the records into the new files, and rebuilds the indexes.

        Since this method is faster and creates smaller files than the SECONDARY method, you should use this method whenever possible. However, if you are using Scalable SQL, you must not use this method when rebuilding the VIEW.DDF file.

      • The SECONDARY method clones and copies the files without dropping and replacing indexes. This method may be slower than the PRIMARY method.

9. At Continue On Error, specify either Y or N and press Enter.

   If you specify Y, the utility continues if it encounters an error. (The utility notifies you of non-Btrieve files or other errors but continues rebuilding Btrieve files.) If you specify N, the utility stops if it encounters an error and aborts the rebuild process.

10. At Convert Supplemental Indexes, specify Y or N and press Enter.

    IMPORTANT:  Do not use the Convert Supplemental Indexes option if you access your data files through Scalable SQL.

    If you specify Y, the utility converts Btrieve 5.x supplemental indexes (which allow duplicates) to Btrieve 6.x indexes with linked-duplicatable keys. Btrieve 5.x supplemental indexes have, by default, repeating-duplicatable keys.

    If you specify N (the default), the utility does not convert the 5.x supplemental indexes but preserves them as repeating-duplicatable keys.

11. Press Esc to leave the Rebuild Configuration Setup Form screen.

12. When the utility asks whether to save your changes, select Yes to save them and return to the Rebuild Options menu or No to abandon the changes.

    IMPORTANT:  The utility applies the Btrieve 5.x file's owner name and level to the Btrieve 6.x file.

1. At the Rebuild Options menu, select Execute Rebuild to run the utility.

   
   

   The utility executes and also creates a log file. It then notifies you that the process has completed.

2. To return to the Rebuild Options menu, press Esc.

   You can now examine the log file, as discussed in the following section.

1. Select View Rebuild Log File from the Rebuild Options menu.

   
   

   The utility displays a log of any errors that occurred while the utility was executing. This log file, REBUILD.LOG, is similar to the example shown in Figure 11.

   Figure 11
   Setup: Example Rebuild Log File
   

2. When you finish viewing the log, press Esc to return to the Rebuild Options menu.

3. To exit both the Rebuild utility and the Setup utility, press Esc twice more and specify Yes at the Exit Btrieve Setup? prompt.

Before running the Rebuild utility from the command line, make sure you have unloaded your previous version of Btrieve (as described on Unloading an Earlier Version of NetWare Btrieve), started Btrieve 6.x (as described in Starting NetWare Btrieve 6.x), and backed up all your data files. Having a backup copy ensures against data loss if a power interruption occurs while you are running this utility.

NOTE:  After rebuilding your files, be sure to check the utility's log file to see if any errors occurred during the conversion. The log file (BREBUILD.LOG) that the Rebuild utility creates is an ASCII text file, which is placed in the SYS:SYSTEM directory. You can examine the log file using a text editor or by running the Rebuild utility interactively and selecting View Rebuild Log File from the Rebuild Options menu (as explained in Viewing the Rebuild Log File).

To run the Rebuild utility from the command line, enter one of the following commands at the prompt:

LOAD BREBUILD [- option ...] file

or

LOAD BREBUILD @ commandFile

option	Specifies the configuration options for the utility. Precede each option letter with a dash (-). Do not place a space between the dash and the option letter or between the option letter and its value. You can enter the option letter in uppercase or lowercase.
	-B[path]	Specifies an alternate location for the rebuilt files. (The default location is the current directory.) This option lets you rebuild large files on a different volume or on a different server. To locate the files on a different server, the Btrieve NLM and the Message Router must be loaded on the server where the original data files reside. The Btrieve and BSPXCOM NLMs must be loaded on the server that will contain the rebuilt files. Do not use wildcard characters in the pathname you specify with the -B option.
	-C	Instructs the utility to continue with the next file even if an error occurs. The utility notifies you of non-Btrieve files or other errors but continues updating Btrieve files. This option is useful if you have specified wildcard characters for the rebuilt files.
	-D	Converts Btrieve 5.x supplemental indexes (which allow duplicates) to 6.x indexes with linked-duplicatable keys. (By default, the utility preserves the indexes as repeating-duplicatable keys.) If you access your data files only through Btrieve and your files have a relatively large number of duplicate keys, you can use this option to enhance the performance of the Get Next and Get Previous operations. Do not use the -D option if you access your data files through Scalable SQL.
	-M0 | M2	Specifies the conversion method, as follows:
		M0	Clones and copies the files without dropping and replacing indexes. While this method is slower than M2, it is available in case you do not want to rebuild your indexes. f you are using Scalable SQL, you must use the -M0 and - K0 options to rebuild the VIEW.DDF file.
		M2	(Default) Clones the files, drops the indexes, copies the records into the new files, and rebuilds the indexes. Since this method is faster and creates smaller files than the M0 method, you should use it whenever possible. The M2 method may create a 6.x file in which the records are in a different physical order than in the original 5.x file.
	-P[nnn]	Specifies the page size (in bytes) of the new files. I f you specify -P with no page size, the utility chooses the optimum page size for your file. For example, assume you have a Btrieve 5.x file with a page size of 1,024 and 24 keys. Since Btrieve 6.x supports only 23 keys for a page size of 1,024, the utility automatically selects a new page size for the file and displays an informative message on the screen. If you do not specify the -P parameter, the utility changes the page size if the original size does not work
	-K[nn]	Specifies the key by which the utility reads when rebuilding a file. If you do not specify this option, the utility reads the file in physical order. You must use the -K0 option when rebuilding the Scalable SQL VIEW.DDF file.
	-T	Does not preserve the Transaction Tracking System (TTS) bit during conversion. If you specify this option, the utility clears the TTS bit (if set) when converting a Btrieve 5.x file to a Btrieve 6.x file. If you do not specify this option, the utility sets the TTS bit when creating the Btrieve 6.x file if the 5.x file had the TTS bit set.
file	Specifies the set of files to convert. Use full directory names, including the volume name. You may use wildcards (* and ?) in these filenames. The Rebuild utility applies the Btrieve 5.x file's owner name and level to the Btrieve 6.x file.@commandFile
	Specifies a command file for the utility to execute. You can include multiple entries in one command file. Each entry in the command file contains the utility options (if any) and the set of files to convert, followed by <end> or [end]. When specifying the files to convert, be sure to use full directory names, including the volume name. You may use wildcards (* and ?) in these filenames. The following is an example of a Rebuild utility command file:

-C sys:\mydir\*.* <end> -C -P1024 dta:\dir\*.* <end> -M0 -K0 sys:\nwsql\*.* <end>