ODBC_CONN_PARAMS=(DBTYPE={MSQL|MYSQL|PG}
,SERVER=
server_pattern[,
port_pattern]
,ADDL_PARAMS=
parameter1,
parameter2,...
)

DBTYPE

Specifies the type of source database for which to specify additional DataDirect ODBC connection parameters. This value must match the TYPE parameter value in the CAPI_CONNECTION statement for the source. Options are:

MSQL
. For Microsoft SQL Server sources.
MYSQL
. For MySQL sources.
PG
. For PostgreSQL sources.

No default is provided.

SERVER=

server_pattern

[,

port_pattern

]

Identifies the database server or servers for which to use the additonal ODBC parameters for connecting to the source database. Optionally, you can include a port number or port number pattern.

To specify a server or port pattern, include the asterisk (*) wildcard, which represents zero or more characters, or the question mark (?) wildcard, which represents a single character. Separate the server and port values with a comma.

ADDL_PARAMS

Specifies one or more ODBC parameters to add to the connection string that is sent to the DataDirect driver for connecting to the source. These parameters are used on the servers that match the server name pattern and have an available port that matches the port pattern.

Specify parameters that your DataDirect driver supports in odbc.ini files. For more information, see the DataDirect documentation for your driver type. However, do

not

use any of the following ODBC parameters that are not supported by this DBMOVER statement:

For Microsoft SQL Server sources
: DRIVER, HOST, PORT, DB, AM, DOMAIN, UID, and PWD
For MySQL sources
: DRIVER, HOST, PORT, DB, UID, and PWD
For PostgreSQL sources
: DRIVER, HOST, PORT, DB, UID, and PWD

No validation is performed on the ODBC parameters you add. Verify that your parameter entries are valid.

CAPI_CONNECTION=(NAME=
capi_connection_name 
         ,TYPE=(UDB
             [,LIMITRESCAN={
N|Y}] 
             [,LOGBUFSIZE=[
kilobytes][,
kilobytes]]
             ...))

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.