If the Data Warehouse hangs or displays a Btrieve Error 100 (No cache buffers are available) when synchronizing some projects, increase the Pervasive Cache Allocation Size setting on the server running the Data Warehouse Controller.
If the combined size of the .RRH and .RRD tables or .RRH and .WRD tables is greater than 72 MB, then you should increase the Cache Allocation Size parameter from the default 33554432 bytes (32 MB) to 45% or more of the combined size of the two tables.
MicroKernel uses this cache when accessing any data files
MicroKernel uses values that are multiples of 16 KB or 16,384 bytes
Overall performance is usually best when the Cache Allocation Size is a value less than 40% of the physical memory on the system, and the Configuration setting Max MicroKernel Memory Usage is set to a value greater than 40%.
Example:
RRH = 22 MB
RRD = 77 MB
Total = 99 MB
45% of 99 MB = 44.55 MB
45.55 MB * 1024 = 45619.2 KB
45619.2 KB * 1024 = 46714060.8 bytes
Round to a multiple of 16,384 bytes:
46714060.8 bytes / 16384 = 2851.2 = 2852 (rounded up)
2852 * 16384 = 4660168 bytes
In this example, 4660168 bytes is the suggested Cache Allocation Size if less than 40% of total physical memory.
Complete the following procedure from the Data Warehouse Controller (DWC) server console. Do not use Remote Desktop (or any other remote program).
To change the Pervasive Cache Allocation Size setting, complete the following steps:
Open the Pervasive.SQL 10 Control Center (PCC).
Under Engines, right-click the server name for the server running the DWC and click Properties.
Select Performance tuning.
Change Cache Allocation Size in byte(s) to the recommended Cache Allocation Size.
Click Apply.
Close PCC.
Stop and restart the Pervasive engine on the DWC server (or reboot the DWC server).
Try to synchronize the project again.
Introduction to Data Warehouse
Changing the Project Synchronization Retry Interval Settings