The transaction log file filename cannot be written. Check the disk space. If the disk is full, free some space by deleting any unnecessary files. When an error occurs while writing to the transaction log file, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.
To perform this task, open PSQL Control Center (see Starting PCC on Windows in
PSQL User's Guide). Right-click the database engine you wish to configure then click
Properties. Click
Performance Tuning then set the desired value for
Number of Input/Output Threads.
The MicroKernel returns this message when the value specified for the Cache Allocation Size option is invalid. Use the configuration properties and specify a valid value for this option. In Pervasive.SQL 8 and later, this value can be managed dynamically by the MicroKernel.
The MicroKernel returns this message when the value specified for the Largest Compressed Record Size option is invalid. Use the configuration properties to specify a valid value for this option.
The MicroKernel returns this message when the value specified for the Number of Open Files option is invalid. Use the configuration properties and specify a valid value for this option.
The MicroKernel returns this message when the value specified for the Operation Bundle Limit option is invalid. Use the configuration properties and specify a valid value for this option.
The MicroKernel returns this message when the value specified for the Number of Handles option is invalid. Use the configuration properties and specify a valid value for this option.
The MicroKernel returns this message when the value specified for the number of Number of Input/Output Threads option is invalid. Use the configuration properties and specify a valid value for this option.
The MicroKernel returns this message when the value specified for the Active Clients option is invalid. Use the configuration properties and specify a valid value for this option.
The MicroKernel returns this message when the value specified for the Sort Buffer Size option is invalid. Use the configuration properties and specify a valid value for this option.
The MicroKernel returns this message when the value specified for the Working Directory option is invalid. Use the configuration properties to specify a valid path.
The MicroKernel returns this message when log file filename cannot be written. Check the disk space. If the disk is full, free some space by deleting any unnecessary files. When an error occurs while writing to the transaction log file, the MicroKernel attempts to resume transaction logging after every update to a data file containing system data. Therefore, when the condition causing the error is corrected (for example, when more disk space is made available), the MicroKernel automatically resumes transaction logging.
The MicroKernel returns this message when the file filename is rolling back. Rolling back is the procedure the MicroKernel uses to restore a file to a consistent state after a system crash. This procedure undoes the most recent changes to the file (changes in the most recent system transaction).
The id corresponds to a section of code in the MKDE where the OS call took place. There are different id ranges depending on which egnine is being used:
The second piece of the system error is the operation code. This corresponds to the Btrieve request that was being processed when the error occurred. For example, a 5 is a GetEqual operation. See Btrieve API Guide for more information about Btrieve operation codes. If the system error occurs while the MicroKernel Engine is performing some task that is not specifically associated with a Btrieve operation, the op will be set to -1.
This is an informative message the MicroKernel returns when it must create more worker threads than the number specified by the Number of Worker Threads configuration option. To avoid receiving this message, increase the value for the
Number of Worker Threads option.