Syniti Replicate supports use of IBM Db2 for i for:
Refresh replications, both source and target
Mirroring replications, both source and target. For source connections, Syniti Replicate offers the use of the transaction log/journal, and the Log Server Agent
When setting up IBM DB2 for i for use with Syniti Replicate:
Set user ID authorities appropriately (DBMS tools)
Make sure tables are journaled and receivers are set up appropriately (DBMS tools)
Create a library on Db2 (Management Center)
This section contains topics that describe:
IBM Db2 for i Transactional Replication Settings (in the Enable Transactional Replication wizard or the Manage Transactional Log Settings dialog)
IBM Db2 for i Journal Information (in the Create Replication wizard and Create Multiple Replications wizard Source Log Info screen)
Troubleshooting Articles
Limitations
With all current versions of Syniti Replicate you can replicate IBM Db2 for i (iSeries/AS400) logical files and views in REFRESH mode. They cannot be used for incremental (transactional) replication because the appropriate journal/receiver information is not recorded. For the purposes of replication, treat logical files/views in the same way as physical files.
Syniti Replicate does not support LOB data types.
Connection Properties
Required Information
Property | Description |
|---|---|
Data Source | IBM i/System i IP Address or Host Name |
User ID | Database username |
Password | User Password |
Optional Information
Property | Description |
|---|---|
Libraries | Comma separated list of Libraries. |
Passphrase | When True, it allows case-sensitive passwords with length up to 128 chars. Notice that, in order to work correctly, it will be necessary to set the property “Case Sensitive UserPWD” to True as well. |
Case Sensitive UserPwd | Indicates if the password is case sensitive. |
Isolation Level | Isolation level, used for bulk inserts to IBM i/System i, the following levels are available 0 - None, No commitment control. 1 - All, records are locked until commit/rollback is performed. 2 - Change, records all locked while they are being modified. 3 - Cursor, records are locked while they are being fetched. |
Host Code Page | Code page (host language) that is currently set on the IBM i/System i. |
Port Number | IBM i/System i database server port number. |
Init Timeout | Maximum length of time the provider waits before assuming an error has occurred and a TCP/IP 10060 error is returned. |
APPC Buffer Size | Maximum size for the buffer that is used in the conversation with the host. |
Fetch Block Size | Maximum number of records (maximum block size) to retrieve in any fetch operation. The value is expressed in kilobytes and the default is 32KB. When server access speed is not an issue, increase this 32KB value to reduce network overhead. The value must always be greater than the size of a single record in the result set. |
Max Rows | Maximum number of rows returned from a select statement. 0 indicates no limit. |
Data Compression | The data compression option allows the server to compress the data being sent to the client. Data being sent from the client to the IBM i/System i is still in a compressed format. |
Pooling | The connection pooling allows the re-using of an existing connection from a pool, instead of repeatedly establish a new connection with the database. |
Use Packages | When True, packages are used to store compiled parameters statements the first time they are excluded. This is useful if your application executes the same statements a number of times. The second and subsequent times a statement is executed, the IBM i/System i reuses the compiled statement from the package, saving the compile time and the time it takes to create the links between the tables. For example, if an application execute the following statement: UPDATE TABLE SET FIELD = ? using a data source where “Use Packages” is true, the providers registers the compiled statement in a package. When the statement is executed again, the IBM i/System i reuses the compiled statement in a package. A package is created at connection time if it does not already exist. |
Package Library | Library name that should contain the package and the package name. If library names is set to <Default>, the package is registered in the first library in the connection library list defined on the IBM i/System i. If no library is specified in the library, the package is registered in QGPL. |
Package Name | If it set to <Default>, the provider will create a package name as follow: ‘RITMOPKG’ + <0, 1, 2, 3 depending on the isolation level>. |
Allow Package Update | When True, every SQL parameter statement is added to the package. When unchecked, the data source does not add SQL statements to the package, but statements already in the package are used when applicable. |
Hold Cursors | Normally, when a commit occurs, all cursors are closed. Some applications do not function appropriately if cursors are closed. In such cases you can check this option to keep cursors open. For example, if “Hold Cursors on Commit“ is true, and you fetch rows from a result set, then commit, cursors remain open so you can continue to fetch additional rows from the result set. |
Binary Chars | If True, the provider converts the values found in CCSID 65535 fields using the current ASCII table (character set). If unchecked, no conversions occurs. |
Convert Date Time | When True, enable client application to read date/time fields as chars fields. |
Remove Blanks | When True, the provider automatically removes any blanks found at the end of a character field (CHAR, VARCHAR, LONGVARCHAR) before returning the field value to the application that has requested it. |
Use Unicode SQL | If True, the provider send SQL statements to the server in unicode (UCS-2) CCSID. |
Catalog Name | indicates the auxiliary storage iASP to be used when running the catalog queries. |