Create a new server for Db2/UDB - Connect_CDC - connect_cdc_mimix_share - 6.x

Name

Use alphanumeric characters to specify a unique server name for use in the model.

Note: The slash (/), backslash (\), colon (:), left caret (<), right caret (>) and spaces cannot be used in a server name.

DBMS Type

Select DB2/UDB from the dropdown list.

DBMS version

Select the version number from the dropdown:

• 9

• 10

• 11

Location name

Specify the DB2/UDB database name.

DBMS instance port

Configured by the database administrator.

• On UNIX, check the dbm cfg file:

$ su - <db instance admin name>
Password: <password>
$ db2

Look at the file, using the command:

db2 => get dbm cfg

Locate lines similar to the following:

TCP/IP Service name (SVCENAME) = 60010

The port number in this example is 60010

Note: SVCENAME is the parameter contains the name of the TCP⁄IP port which a database server will use to await communications from remote client nodes. This name must be the reserved for use by the database administrator.

JDBC Driver

Select a driver from the dropdown.

• UDBType4. This is the default.

Driver Version

View the JDBC Driver version. This information is obtained each time a connection to the database is made, including a Test Connection. (Informational only)

DBMS logon IDs and DBMS logon password

Specify the Default and Rep user IDs.

1. Input the user login ID for accessing this server.

2. Specify the owner of the metabase on this server.

3. Select Default and Rep user (they may be different).

• The Default user is what Connect CDC Director uses to connect to the server.

• The Rep user is what the kernel uses to connect to the server.

Note: When adding, updating, or deleting rows on the source table, do not use the replication user ID to make these changes. Changes made by the replication user are ignored by change capture triggers.

Specify additional IDs.

1. In DBMS logon password, enter the logon password for the ID.

2. In DBMS logon IDs, for the second user ID, select Type in a new ID.

3. Specify an ID that can access and query the source or target tables on this server for testing or informational purposes.

   Note: Do not select Default or Rep user.

4. Specify the ID password in DBMS logon password.

Metabase schema

Specify the name of the metabase schema. It is the qualifier of the metabase tables, in the format qualifier.tablename. This is the owner of the metabase. The default is rpuser.

Enable prepared statements

If selected, prepared statements are enabled for the entire database server. A prepared SQL statement is a statement in which the steps to parse, analyze, validate, and determine the access path are only done once, when the statement is first prepared. On subsequent executions of the statement, the database has this information stored in memory and can skip the initial preparation steps. After a statement is prepared, only the column values change from one execution of the statement to the next.

Each table can have as many as seven prepared statements: one for insert, up to five for update, and one for delete. The first time an insert, update, or delete is encountered, the statement is prepared, added to the cache, and is used to update the table. The statements are kept in the cache until removed.

Using prepared statements provides a significant performance improvement when the same SQL statement is executed over and over. However, in some cases data for unchanged columns will be captured and sent across the network.

Individual tables can disable prepared statements. This is useful for managing the size of the cache file.

Database limit

Displays the maximum size allowed by the database for open statements in the cache. The Specified limit, below, cannot exceed this value. The correct value is provided after you run a Test Connection. To do so, right-click the server name, then select Test Connection.

Specified limit

Enter the maximum size allowed for open statements in the cache. When the statement cache is full, the least recently used statement is removed from the cache, closed, and destroyed. If Journal batching is enabled, prior to removing the statement, pending batch updates are executed, If the statement that was removed is later referenced, a new prepared statement is created and added to the cache.

Note the following:

• The default is 700.

• The minimum value is 7.

• The maximum value is specified in Database limit, above. If you set the specified limit to a value lower than the number of prepared statements in the model, performance may decrease.

Model using metabase

Displays the name of the model. (Informational only)

Model version

Displays the version number, updated after each commit. (Informational only)

Metabase version

Displays the version of the metabase (for example, 40d). (Informational only)

GMT offset (minutes)

Displays the amount of time, in minutes, that local time differs from Greenwich Mean Time (GMT). For example, Boston is 300 minutes less than GMT. (Informational only)