In the UDB CAPI_CONNECTION statement in the dbmover.cfg configuration file, you can now specify the following new optional parameters:
LIMITRESCAN={Y|
N
}
Optional. When PowerExchange change capture processing encounters a compressed record for a source table in the Db2 log, controls whether PowerExchange scans the log for records from propagatable tables up to an internally set limit or continues scanning until the buffer is full or until the end-of-log (EOL). Use this parameter to avoid excessive scanning of the log, which can result in PowerExchange capture timeouts and degraded performance.
Y
. Limits PowerExchange scanning of log records for change capture. This option is recommended to avoid potential PowerExchange capture timeouts and failures.
N
. Allows PowerExchange scanning of log records to continue until the buffer is full or until the end-of-log (EOL). In this case, PowerExchange capture processing might end abnormally with a timeout error. This problem is more likely to occur when source tables have a low volume change activity.
Default is N.
LOGBUFSIZE=[
kilobytes_normal
][,
kilobytes_filtered
]
Optional. The buffer sizes, in kilobytes, that the PowerExchange capture process uses for reading Db2 log records in normal-read mode and filtered-read mode. In
filtered-read
mode, PowerExchange scans for compressed records from propagatable tables. You can specify a buffer size for one or both log read modes.
For the first normal-read buffer size, if you enter 0 or do not specify a value,128 KB is used by default. For the second filtered-read buffer size, if you enter 0 or do not specify a value, the first normal-read buffer size is used by default for filtered read operations.
If you set the PowerExchange capdl_bufsize environment variable at the direction of Informatica Global Customer Support, the environment variable value overrides the buffer sizes in the LOGBUFSIZE parameter.
For more information, see the "DBMOVER Configuration File" chapter in the