For pre-v6.0 data files that are larger than 768 MB, there is a conflictĪmong locking mechanisms.For example, if you name the data files CUSTOMER.ONE and CUSTOMER.TWO,īoth files have pre-image files named CUSTOMER.PRE. For pre-v6.0 data files, there is one pre-image file for multiple dataįiles.Transaction, and there is not enough disk space for a write to the pre-image For pre-v6.0 data files, there is a large pre-image file inside a.Refer to the Advanced Operations Guide for more information on The file is damaged, and you must recover it.This status code typically indicates a corruptįile, an error while reading from or writing to the disk. 002: The application encountered an I/O error If this is the case, you must uninstall your databaseĮngine and install the general release version. General-release version of the V8 client software against a pre-release version You may receive this error if you are running a The specified operation does not exist or is not That is to say, if you try to search Btrieve Error Code 25, you should search "025" instead of "25." 001: The operation parameter is invalid All status codes are provided in 3-digit formats since the search on this website cannot search 1 or 2-digit words correctly. This section describes status codes that the ← Pervasive PSQL MicroKernel (Btrieve) Database Engine Status Codes
0 Comments
Leave a Reply. |