Issue :
Goldengate Extract Abends with “CACHESIZE TOO SMALL” upon Startup but Succeeds upon Immediate Restart
Observation :
Multiple Goldengate Extract and Datapump processes processes abend with “CACHESIZE TOO SMALL” but startup succeeds upon immediate restart.
Reason :
The problem is caused by the default probe of the available swap space performed when the extract processes start up on certain platforms. It depends on the operating systems commit policy with respect to swap as to what will happen on the initial probe.
Fix :
1. Ensure that the system has greater than the default swap required by all the extract processes running on the system.
2. Manually tune the extract parameter CACHESIZE by setting it in the etxract parameter file as follows
EXTRACT ext_1
CACHEMGR CACHESIZE 8G
…
What is should be set to will depend on the CACHEMGR usage as per the information generated when issuing the command SEND … CACHEMGR CACHESTATS to the relevant extract processes.
