Do not set the CACHEBUFFERSIZE option to the CACHEMGR parameter (Doc ID 1262366.1)

Last updated on JANUARY 13, 2017

Applies to:

Oracle GoldenGate - Version 10.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Applies to:

Extract and replicat for Oracle GoldenGate, versions 10.0 and later. All databases except DB2 on z/OS and NonStop SQL/MX.

Symptoms:

The CACHEBUFFERSIZE option to the CACHEMGR has been explicitly set.

(1) extract/replicat abends with an ENOMEM. This will be logged in the report file, or

(2) extract/replicat runs slowly with significant file caching.

(3) when setting the option high (10M), it fills up the dirtmp directory.

 

Changes

Solution:

Do not set the CACHEBUFFERSIZE option to the CACHEMGR parameter.

CACHEBUFFERSIZE will likely be deprecated in future releases.

 

Determining the extent of file caching:

To determine the extent of file caching use the command:

GGSCI > send <extract-group> CACHEMGR CACHESTATS

This will log the cachemgr statistics to the report file. Under the section "CACHE File Caching" the "disk caching" field will indicate the number of requests to use the temporary file cache.

 Alternatively, look in dirtmp to see if there are many and/or large files ending in '.cm'.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms