
2-30
Messages
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.
MKDE-1157: System Error: nn.nn.nn
The MicroKernel Database Engine returns this message when a
system error occurs. See MKDE-2039: System Error: nn.nn.nn for
more information.
MKDE-1161: 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).
MKDE-1164: Error creating/accessing semaphore
The MicroKernel returns this message if an internal error occurs.
MKDE-1165: Error creating execution thread
Decrease the value of the Number of Input/Output Threads
configuration option.
To perform this task, open Pervasive PSQL Control Center (see
Starting PCC on Windows in Pervasive 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.
MKDE-1166: Could not open Pervasive Event Log file.
This file is created in the home directory. Verify that the
directory is present and sufficient space is available.
The MicroKernel returns this message when it cannot create the
Pervasive Event Log (PVSW.LOG) in the directory. Make sure that
the disk on your computer is not full.
The home directory is defined as \WINNT\SYSTEM32 (Windows
32-bit platforms).
Komentarze do niniejszej Instrukcji