Setting the Executor Command Cache Size

Use exec_max_cache_size to specify the amount of memory to allocate for the Executor command cache.

Insufficient memory allocated for the cache affects replication performance, and you see this error message appearing frequently:

Executor Command Cache exceeds its maximum limit defined by exec_max_cache_size (current value is current_exec_max_cache_size).

To avoid further replication performance degradation, either add more memory to the cache with exec_max_cache_size, or disable table metadata reduction in your Replication Agent .

You can set values from 0 to 2,147,483,647 bytes for a 32-bit Replication Server, and 0 to 2,251,799,813,685,247 bytes for a 64-bit Replication Server. The default is 1,048,576 bytes for both 32-bit and 64-bit Replication Servers.

For example, to set the Executor command cache size to 2,097,152 bytes at the:

Server level – for all primary database connections to Replication Server, enter:
```
configure replication server
set exec_max_cache_size to '2097152'
```

Connection level – for a specific primary database connection, enter:

alter connection to dataserver_name.database_name
set exec_max_cache_size to '2097152'

Replication Server always uses the connection level setting if there are settings at both levels. You need not restart Replication Server for the change to take effect.