Caching Considerations
There are two important caching considerations when using CMA to migrate administrative data.
The "apply" batch processes update data. As described in Batch Cache, if any batch job is updating data marked as "cached for batch" it must be run in a special thread pool. Contact your system administrator and ask for the name of a thread pool that has turned off caching. This thread pool name must be entered in the batch controls used for CMA processing in the Thread Pool Name parameter.
After a successful migration, the target region now has new administrative data which needs to be part of various caches. It is recommended to flush the server cache (which will trigger a 'global' flush of the cache). If the thread pool workers in the target region are configured to refresh their caches when a global flush is requested, then this is the only step required. If not, then the F1-FLUSH batch job should also be submitted to refresh the caches used in batch processing.
Fastpath:
Refer to Caching Overview for more information.
Fastpath:
Refer to Running Batch Jobs for more information about running CMA batch jobs.