•
|
The Pervasive PSQL L2 cache must be turned “off.” That is, the setting for “Max MicroKernel Memory Usage” must be set to zero. See Max MicroKernel Memory Usage. Note that, if XIO is installed, the Pervasive PSQL installation turns off the L2 cache.
|
1HKEY_LOCAL_MACHINE\SOFTWARE\PERVASIVE SOFTWARE\XIO
|
No. Xtreme I/O must not be installed if Pervasive PSQL is being used in a clustering environment. A node with XIO installed can hang when the machine comes online through a failover and leave the shared storage inaccessible.
Therefore, on the installation Setup Type dialog for Pervasive PSQL, select Custom. If “Pervasive Xtreme I/O” displays as an available installation option, click that option. Select “This feature will not be available.”
|
|
No. Xtreme I/O must not be installed if Pervasive PSQL is being used on a Virtual Machine.
|
|
The Options dialog lets you customize certain aspects of the utility, such as the interval in which Xiostats polls its cache. The Options command is accessed from the File menu.
|
|
The Parameters list shows you the various Registry settings for Xiostats. You can customize only two of the settings. See Registry Settings.
Do not modify any XIO registry entries except the two listed under Registry Settings. Unpredictable results can occur.
|
|
Check the setting MaxCacheSizeMB and adjust as required based on the amount of system memory and the data set.
|
2. At a command prompt, execute the command xiomgr -disable to prevent the XIO driver from loading.
(By default, xiomgr is located in the PSQL\bin\ directory in the Pervasive tree under Program Files. See also Where are the Pervasive PSQL files installed? in Getting Started With Pervasive PSQL.)
|
|
The problem is that steps C and D are reversed in sequence. Following an Xiomgr -stop command, you must first issue the Xiomgr -start command and then start the Pervasive PSQL services.
|