Skip to main content Skip to complementary content

Setting advanced connection properties

In the Advanced tab, you can set advanced connection properties such as overriding CCSID to Character Set mapping, setting Change Data Capture properties, and setting internal Replicate parameters.

Overriding CCSID to character set mapping

In some cases, character data in source tables may be encoded in a different CCSID than what is declared in the source database table definition. For example, a specific table or column definition might indicate that its uses CCSID 500 (EBCDIC International) whereas in fact, it uses CCSID 1148 (ENCDIC International with EURO). In this case, you can tell Replicate that the source definition CCSID 500 should be treated as CCSID 1148 (specifically, the character set named IBM-1148).

Note that when the source table definition specifies CCISD 65535 (meaning character set is unknown), you must specify what character set should be assumed when reading data from that table or column.

Information note

If there is a conflict between the character set mapping for a specific column and the character set mapping defined in the endpoint settings, the column-level character set mapping takes precedence.

For more information on overriding character set mapping at column level, see Using the Transform tab.

To do this:

  1. In the Override CCSID to Character Set Mapping section, click the New button.

    A row is added to the table.

  2. Enter the CCSID in the CCSID column and the code page in the Character set column.

    The Character set (code page) must be specified in the proper format (e.g. ibm-1148_P100-1997). For a list of valid formats, see the ICU Converter Explorer.

  3. Repeat to map additional CCSID values.

Converting to a custom code page

Perform the following procedure if your source endpoint tables are defined with an incorrect CCSID and the correct definition is actually in a UCM file.

  1. Create a mapping data file with the file extension .ucm.

    Information note

    If you edit an existing UCM file, you must also change the values of the <code_set_name> and <icu:alias> properties. If the file does not contain an <icu:alias> property, then you only need to change the value of the <code_set_name> property.

  2. Create a CNV file for the UCM file by running the following command:

    <product_dir>\bin\makeconv.exe -v <file_name>.ucm


    "c:\Program Files\Attunity\Replicate\bin\makeconv.exe" -v 1047_EX.ucm

    This will create a CNV file with the same name as the UCM file (for example, 1047_EX.cnv).

  3. Create a new subfolder named icudt<XX>l under <product_dir>\bin where the XX is the same as the number in the icudt<XX>.dll file name.

    For example, If the DLL file name is icudt69.dll, create a new subfolder named icudt69l.

  4. Copy the CNV file to the subfolder you just created (<product_dir>\bin\icudt69l in the example above).

    Information note

    When using the Replicate File Channel, the file should be copied to the same location on both Replicate servers.

  5. Add a new character set mapping as follows:
    1. In CCSID column, enter the original source CCSID number (e.g. 1047)
    2. In the Character set column, enter the name of the CNV file without the extension (e.g. 1047_EX).
  6. Restart the Qlik Replicate UI Server service.

Change data capture properties

  • Check for changes every: How often to check for new changes when the database is quiet. When the database is active, changes are captured as soon as they are detected.
  • CDC reader UDTF name: The name of the Qlik-supplied User-Defined Table Function, which is used for CDC. Specify the two-part name using the values you have chosen for schema name, &R4ZSCNM, and the function name, &R4ZIFITF.
  • UDTF result set size (MB):

    Specify the maximum size to be accumulated by result rows returned by the Qlik-supplied User-Defined Table Function, through CDC tasks using this endpoint. A larger result set will cause less overhead time establishing the IFI session, but will result in greater memory consumption by DB2. Specifically, because the result set is a LOB, you might need to increase the LOBVALA limit in the DB2 configuration (DSNZPARM), specifying the maximum LOB size allowed per user. Assuming all CDC tasks are configured with the same ODBC user-ID, to accommodate for all tasks running concurrently, set LOBVALA to 2 × 1024 × the following size:

    SUM[(i=all endpoints) : resultset size in endpoint(i) × #_tasks using endpoint(i)]

    (Resultset size is in Mbytes, so it needs to be multiplied by 1024 to reflect LOBVALA size, which is in Kbytes).

    Another DSNZPARM limit, LOBVALS, specifies the total size when across all user-IDs; so, if there are multiple user IDs, you need to monitor this value as well. Note, however, that LOBVALS is specified in Mbytes, unlike LOBVALA.

  • Automatically enable Data Capture Changes (requires admin privileges): For Qlik Replicate to be able to capture changes, the Data Capture Changes attribute needs to be set on all relevant source tables. You can either do this manually or allow Replicate to perform this action by leaving this option enabled (the default). When this option is enabled, the connecting user must have ALTER permission on the source tables being captured.

Setting internal parameters

Internal parameters are parameters that are not exposed in the UI. With the exception of the parameters listed in Authorized internal parameters at the end of this section, you should only use them if instructed by Qlik Support.

To add internal Qlik Replicate parameters:

  1. Click the Internal Parameters link.

    The Internal Parameters dialog box opens.

  2. In the edit box, type the name of the parameter you need to add and then click it.

    The parameter is added to the table below the search box with its default value.

  3. Change the default value as required.
  4. To add more parameters, repeat steps 2 and 3 above.

  5. To reset a parameter value to its default, click the "Restore default value" icon at the end of the row.

Authorized internal parameters

The following table provides a list of internal parameters that can be used as required.

Internal parameters
Parameter name Values Default; Max; Min.

0 – No DEBUG traces;

1 – include DEBUG traces;

9 – full DEBUG

0; 0; 9.


Size (in bytes) of Log data buffer used for IFI reading

65536; 65536; 1048576.





(empty string)

R4Z configuration dependency on host

This table in this section provides a list of R4Z configuration values, which can be set during installation or as part of the CDC service setup, or as part of the endpoint definition.

R4Z configuration values
R4Z Topic Depends upon Property Defined at/Inquired by Resolution

Total Size of R4Z ECSA structures

Available ECSA size



Make sure ECSA size is not exceeded.

MAXRESULTSETSECS parameter in the CDC service

Maximum time DB2 thread waits for a locked resource


Set at least two seconds below the SSID spec.

MAXRESULSETSIZEparameter in the CDC service Maximum LOB size available per user-ID


2 * (resultset size * max. session)

Decimal point: period or comma

Designates the decimal editing separator


If the decimal separator is a comma, set the additionalConnectionProperties internal parameter to patch2=15.

More options

These options are not exposed in the UI as they are only relevant to specific versions or environments. Consequently, do not set these options unless explicitly instructed to do so by Qlik Support or product documentation.

To set an option, simply copy the option into the Add feature name field and click Add. Then set the value or enable the option according to the instructions you received.

Settings summary

You can view a summary of your settings by clicking the Setting Summary link. This is useful if you need to send a summary of your settings to Qlik Support.


Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!