Pervasive psql v13 cache client update#
Pervasive psql v13 cache client 32 bit#
Pervasive psql v13 cache client windows#

However, the MicroKernel does return this status code on the very first Get Next, Get Next Extended, Get Previous, or Get Previous Extended operation performed after the deletion or update, even if that Get operation uses the same key value the application passed to the Delete or Update operation. If the application changes the value of the key number in the Delete or Update operation (from the value used with the preceding Get operation), the MicroKernel deletes or updates the record as requested and does not return this status code, at least not at this point. In a related situation, the MicroKernel returns this status code when an application performs a Delete or Update operation immediately following a Get operation. The operation requires the same key number parameter as the previous operation, because the MicroKernel uses positioning information relative to the previous key number. 7: The key number has changed The key number parameter changed before a Get Next, Get Next Extended, Get Previous, or Get Previous Extended operation. The key number must correspond to one of the keys defined for the file. 6: The key number parameter is invalid The value stored in the key number parameter is not valid for the file being accessed. The MicroKernel also returns this status code when it cannot create an index that does not allow duplicate key values because a duplicate key value already exists. To resolve, fill the KeyBuffer with the same fill char type as the field.ДҐ: The record has a key field containing a duplicate key value The MicroKernel cannot add or update a record because the record has a key field that contains a duplicate key value for an index that does not allow duplicate values. It is caused by a mismatch of two fields at the char level. The MicroKernel returns this status code when an application performs a Get Equal operation to search on field type char.

Occasionally, a corrupt key can cause this status code. When you receive this status code on an Update or Delete operation, it usually means that the file is damaged, and you must recreate it. The MicroKernel also returns this status code if the application passed an invalid position block for the file, or if the application passed a position block with a client ID other than the client ID used to open the file.Д¤: The application cannot find the key value The MicroKernel cannot find the specified key value in the index path. The application must perform a successful Open operation before the MicroKernel can process any other operations. 3: The file is not open The operation cannot execute because the file is not open.

Pervasive psql v13 cache client windows#

There is an FTF for Pervasive.SQL v.7.0 Windows NT and Service Pack 3 for Pervasive.SQL 2000i Windows NT. You may receive status 2 or corruption on very busy SMP boxes, when a user is deleted from the Btrieve Monitor and the user immediately reopens the files. There was a conflict with the assignment of token handles and permissions.

Pervasive psql v13 cache client 32 bit#

With Btrieve for Windows NT Server Edition v6.15.445, 32 bit Windows application may return Status 2 or 'MKDE Terminated with Service Specific Error 0' after running an application for an extended period of time. A pre-v6.0 Btrieve engine attempted to open a v6.x or later MicroKernel file. Your application can retry the operation until the conflict is resolved (when the competing application releases the lock your application requires). For pre-v6.0 data files that are larger than 768 MB, there is a conflict among locking mechanisms. For example, if you name the data files CUSTOMER.ONE and CUSTOMER.TWO, both files have pre-image files named CUSTOMER.PRE. For pre-v6.0 data files, there is one pre-image file for multiple data files. For pre-v6.0 data files, there is a large pre-image file inside a transaction, and there is not enough disk space for a write to the pre-image file. If you flag your MicroKernel data files as Shareable, data corruption can occur.

As the only user, the MicroKernel can control the integrity of the data files. The MicroKernel is the only user that accesses the files (on behalf of many users). All MicroKernel data files should be flagged as Non-Shareable. In NetWare, at least one MicroKernel data file is flagged as Shareable. Refer to the Pervasive.SQL Advanced Operations Guide for more information on recovering files. One of the following has occurred: The file is damaged, and you must recover it. 2: The application encountered an I/O error This status code typically indicates a corrupt file, an error while reading from or writing to the disk. This section describes status codes that the MicroKernel returns.ДЎ: The operation parameter is invalid The specified operation does not exist or is not valid.