REBUILD

This section lists the messages that the Rebuild utility generates.

REBUILD-2: The utility could not allocate memory

Check the amount of available memory and exit any applications or processes not needed to provide more memory.

REBUILD-3: The utility could not rename file_name to file_name. The MicroKernel Database Engine status code was code_number.

Check the meaning of the status code to help determine why the file could not be renamed.

REBUILD-4: The utility could not retrieve the MicroKernel Database Engine version information. The MicroKernel Database Engine status code was code_number.

Ensure that the database engine is running and check the meaning of the status cod, then try the rebuild again.

REBUILD-5: The utility could not delete file_name

Check file and directory permissions to help determine why the file could not be deleted.

REBUILD-7: The utility could not open file_name. The MicroKernel Database Engine status code was code_number.

Check the meaning of the status code to help determine why the file could not be opened.

REBUILD-8: The utility could not open file_name in the Accelerated mode. The MicroKernel Database Engine status code was code_number.

Check the meaning of the status code to help determine why the file could not be opened.

REBUILD-9: The utility could not create the new file or files with the MicroKernel Database Engine 6.x advanced features

Ensure that the correct version of the database engine is loaded and the file format option is not prior to 6.0.

REBUILD-10: An invalid parameter or value was specified, or the command line was invalid

Check the parameters and values passed to the utility.

REBUILD-14: The utility did not rebuild file_name for the following reason:

Take corrective action based on the reason provided and try the rebuild operation again.

REBUILD-15: MicroKernel Database Engine returned status code_number while operating on the following file: file_name

Check the meaning of the status code to help determine the result of the rebuild operation.

REBUILD-16: The file_name file is already in 6.x format

The file to be rebuilt is already in a 6.x format. Select a different format.

REBUILD-17: The file_name file is not a valid MicroKernel data file. The utility cannot rebuild the file.

Ensure that the file to be rebuilt is a valid MicroKernel data file and try the rebuild operation again.

REBUILD-18: The utility could not obtain the characteristics of file_name. The MicroKernel Database Engine status code was code_number.

Check the meaning of the status code to help determine the result of the rebuild operation.

REBUILD-19: The utility could not access the output directory specified. Directory_name might not exist or did not allow write access.

Verify that the directory exists and that the person running the rebuild utility has read/write permissions to the directory.

REBUILD-20: The utility is processing file_name

For a successful rebuild, the utility reports “The file was rebuilt successfully.”

REBUILD-24: An error occurred accessing file_name. Make sure you specified a valid file name.

Verify that the file name is correct and try the rebuild operation again.

REBUILD-25: The utility is setting the owner name of an empty target file

Verify that file being rebuilt and the target file are what you want.

REBUILD-26: The utility is dropping the indexes of an empty target file

The rebuild process outputs the following information to provide a status of its operation.

REBUILD is reading the first record from the old file.

REBUILD is inserting records into the new file.

REBUILD is reading records from the old file.

REBUILD is putting back indexes on the new file.

REBUILD-27: The utility could not create the temporary file in the output directory during conversion

Verify the directory and that the person running the rebuild utility has read/write permissions to the directory.

REBUILD-31: The utility could not create file_name. The MicroKernel Database Engine status code was code_number.

The rebuild utility also outputs the following information to help you troubleshoot the operation:

REBUILD copied a total of number records.

The rebuild operation start time is time.

REBUILD-34: Key number code_number is invalid

Verify that the keys in the file to be rebuilt are valid.

REBUILD-35: Page size page_size is invalid. The page size will be changed to page_size. The rebuild process has ended.

The rebuild utility detected an invalid page size for the desired format and changed the page to a valid one.

REBUILD-38: The utility was terminated by the user

The rebuild utility was stopped.

REBUILD-39: The utility may not be unloaded. Use Control-C to stop the utility.

An attempt to stop the rebuild utility could not be honored by the utility. Use Control-C to stop the utility.

REBUILD-44: The utility could not clone file_name. The MicroKernel Database Engine status code was code_number.

Check the meaning of the status code to help determine the result of the rebuild operation.

REBUILD-45: The command file file_name does not have an <end> or [end] delimiter.

Each entry in the command file must contain the utility parameters (if any) and the set of files to convert followed by <end> or [end].

REBUILD-48: The utility could not initialize the user interface library

Close other applications to free up memory.

REBUILD-63: The utility could not initialize the localized message table

Close other applications to free up memory.

REBUILD-65: The utility could not open file file_name for the following reason:

Take corrective action based on the reason provided and try the rebuild operation again.

REBUILD-66: Operation(s) complete. See file_name for results.

Review the item specified for the results.

REBUILD-67: Errors occurred. See file_name for results.

Review the results for the errors. The rebuild operation also provides the following information to help with troubleshooting:

File: file_name Records Processed: number_processed

REBUILD-68: Status code code_number was returned while copying records from the following file: file_name.

Check the meaning of the status code to help determine the result of the rebuild operation.

REBUILD-69: Internal status internal_code was returned while copying records from the following file: file_name

Check the meaning of the status code to help determine the result of the rebuild operation. If the internal status code is not listed in the PSQL documentation, contact PSQL Technical Support.

REBUILD-71: The file file_name is already in a later format than the current MicroKernel Database Engine setting

Configure the MicroKernel to create files using the file format version to which you want the specified file to be converted. See Create File Version in Advanced Operations Guide.

REBUILD-72: The utility only converts files to file_format or later

Verify the file format to which you want to convert the file.

REBUILD-73: The MicroKernel Database Engine is configured to create files in the same format as the source file. This is allowed only for file_format or later files.

Configure the MicroKernel to create files using the file format version to which you want the specified file to be converted. See Create File Version in Advanced Operations Guide.

REBUILD-74: The source file file_name does not contain system key. The utility could not rebuild the file as specified by user. The MicroKernel Database Engine returned status code_number.

Check the meaning of the status code to help determine the result of the rebuild operation.

REBUILD-75: File_format is not a valid file format value. Valid inputs for file format parameter are 6, 7, 8, 9 and 95.

Specify a valid file format value and try the rebuild operation again.

REBUILD-78: The logfile specified, file_name, is not valid. It is longer than maximum path length allowed.

Specify a shorter full path name for the log file.

REBUILD-79: Invalid database name specified. Database name cannot be longer than length bytes.

Verify the database name and try the rebuild operation again.

REBUILD-80: Password specified is longer than the maximum limit of length bytes

Verify the password name and try the rebuild operation again.

REBUILD-81: User ID specified is longer than the maximum limit of length bytes

Verify the user name and try the rebuild operation again.

REBUILD-82: Login to database failed. MicroKernel status code_number was returned.

Check the meaning of the status code to help determine the result of the rebuild operation.

REBUILD-85: The size of the output file exceeds the available disk space

Check the amount of disk space and create additional space on the physical storage.

REBUILD-86: Long owner name cannot be set on pre-9.5 file formats

Clear the owner name then try the rebuild operation again.