STARQUEST DATA REPLICATOR PLUS for iSeries v3.40 April 2008 (c)Copyright 1994-2008 StarQuest Ventures, Inc. All Rights Reserved. StarQuest Ventures, Inc. PO Box 1076 Point Reyes Station, CA 94956 Telephone: 415-669-9619 FAX: 415-669-9629 Sales & Support: contact@starquest.com URL: http://www.starquest.com StarQuest Data Replicator (SQDR) is a replication software product that allows you to copy data between IBM DB2, Oracle, and Microsoft SQL Server database environments. The base StarQuest Data Replicator software runs on Windows and provides full refresh replication, which copies all the source data that you specify for replication, regardless of when that data was last replicated. This provides a “snapshot” of the specified source data at the time of replication. Now StarQuest has introduced the separately licensed component, SQDR Plus for iSeries, the first of several versions of the SQDR Plus family that provides incremental replication support for SQDR users. Incremental replications copy only the data that has changed, reducing the amount of data that is transferred and allowing the replication to occur more frequently. This ReadMe.txt file contains important information about installing SQDR Plus for iSeries. Refer to the SQDR Plus for iSeries guide (PDF format) for complete information. The base StarQuest Data Replicator software (for Windows) contains its own readme.txt file and online documentation; refer to those documents for information about the SQDR base software. --------------- Readme Contents --------------- o System Requirements o Installing StarQuest Data Replicator Plus for iSeries o Contacting StarQuest Technical Support o Known Issues ------------------- System Requirements ------------------- Following are the requirements for installing SQDR Plus on an iSeries computer: • OS/400 v5r2, v5r3, v5r4, v6r1 • recent cumulative PTF package • recent DB2 Group PTF package (SF99502, SF99503, SF99504) * Qshell (5722SS1 option 30) • Java Developer Kit v1.4 (5722JV1 option 6) • recent Java Group PTF package (SF99169, SF99269, SF99291) v5r2 only: After installing the cum PTF or DB2 Group PTF from December 2005, you may experience extremely high temporary storage usage when an ODBC application (such as SQDR) using StarSQL connects to the iSeries machine. If you encounter this problem, install PTF 5722SS1-SI23370 for APAR SE25005. v5r2 & v5r3: There is a known issue with Java stored procedures and the reuse of DRDA server jobs if os400.awt.native (used for GUI applications) is true for the userID being used by SQDR Subscriptions. This problem affects OS/400 v5r2 & v5r3. Solutions: * Apply the PTF for APAR SE20821 v5r2: PTF 5722SS1-SI18724 v5r3: PTF 5722SS1-SI18947 * make sure that os400.awt.native is false for the SQDR Subscriber User(s) by checking: /QIBM/UserData/Java400/SystemDefault.properties (system-wide) or /home//SystemDefault.properties (user-specific). Note that if os400.awt.native is false, that user will not be able to run Java GUI applications. * change the number of uses of a DRDA server job (QRWTSRVR) from 200 to 1, such as shown below. This may affect performance. CHGPJE SBSD(QUSRWRK) PGM(QRWTSRVR) MAXUSE(1) v5r3: To use v5r3 you must install PTF 5722SS1-SI18139 for APAR SE20127. v5r4: Install the following PTF's: * 5722SS1-SI22551 * If you are working with BLOB data, install PTFs 5722SS1-SI22324 and 5722SS1-SI22335 v6r1: Install cum level C8064610 or later. Install 5761SS1-SI30581 or a superceding PTF. CCSID values: Both the installing user and the Capture Agent user must be configured for a CCSID (Coded character set identifier) other than the AS/400 default of 65535 (*HEX). The default behavior of the installer is to create the Capture Agent user with a CCSID of 37. During installation, this value can be changed to any valid CCSID or to *SYSVAL (use the system value QCCSID). During installation, the CCSID of the installation job is changed to 37. If you wish to use a different CCSID during installation, this value can be changed to any valid CCSID or to *SYSVAL. To examine what CCSID value is normally used by the installing user, use WRKUSRPRF and scroll to the last page. If "Coded character set identifier" is set to *SYSVAL, then check the system value with DSPSYSVAL QCCSID. Java versions: If you have multiple Java versions installed, make sure that the correct version is being used - Java version 1.4 or later is required for correct operation. You can specify the Java version (for the Classic JVM) with the java.version property in /QIBM/UserData/Java400/SystemDefault.properties (system-wide) or /home//SystemDefault.properties (user-specific). Type "java -version" at a QSH or PASE command prompt to display the java version being used. The default JDK version is typically the latest version present, except on OS/400 v5r2. On v5r2, the SQDR Plus installer will modify the system-wide file /QIBM/UserData/Java400/SystemDefault.properties to contain the line java.version=1.4; the previous version will be saved as /QIBM/UserData/Java400/SystemDefault.prev. Please review any existing Java applications that might be affected by this change. ---------- What's New ---------- Features New to This Version Version 3.3 includes the following new features and behavior. If you are upgrading from a prior release of SQDR Plus for iSeries, be sure to review Updating the SQDR Plus Software on page 23 before you install the new version of the software. * An express update option which automatically installs a new version of SQDR Plus using the settings specified for the existing installation. * Ability to mirror the source database. In addition to configuring how frequently SQDR Plus polls for changes to the source database you can now configure subscriptions to be notified when change data is available and reduce the latency such that updates occur at the target database almost instantaneously after they are committed on the source database. * Additional flexibility in specifying which unique identifier is used to replicate changes to the target database. With v3.3 you can choose to use a Relative Record Number instead of a unique index or primary key. In some cases, such as when different precisions are supported for the same or similar data type by different database systems, an index or primary key that is unique on the source database is not unique on the target database. Using the RRN can help ensure the incremental changes are correctly applied to the target database. * Ability to restrict which database tables can be subscribed to for replication. The SQDR Plus Capture Agent utility provides centralized control for publishing and unpublishing database tables. If you enable the publishing feature, SQDR users can subscribe only to tables that have been published for replication. * Improved error reporting and troubleshooting facilities. Multiple error messages from the same operational problem are now suppressed to avoid filling the event log and sending a large number of repetitive email notifications. Additional facilities are also included for capturing a finer level of detail about change data that is being replicated to the target database -------------------------------- Installing SQDR Plus for iSeries -------------------------------- The SQDR Plus installer requires a GUI environment, so it is typically run on a remote system, such as on a computer that is running Windows, MacOS X, or UNIX with X Windows. The computer from which you run the installer must have Java JVM installed and in the PATH. (Enter java at the command line to verify that Java is installed and can be located.) To run the installer directly from the AS/400 you must configure a remote GUI environment with X or VNC (Virtual Network Computing). The SQDR Plus for iSeries installer consists of data1.jar, media.inf, and the batch/shell scripts setup.bat and setup.sh. Copy these files to the computer from which you are running the installation. The setup script invokes java on data1.jar with the -os400 parameter, prompting for login to the AS/400. Execute the batch or shell script, depending on whether you are running the installation from a Windows, MacOS X, or UNIX computer. Do not invoke data1.jar directly, as the -os400 parameter is required. If you are installing from a Windows system, the installer files should be copied or extracted to a temporary directory on the system drive (e.g. C:\). If you run the installation from a drive other than the system drive, you may see the following error message at the end of the installation; this error is harmless and can be ignored: [java.io.FileNotFoundException: \DOCUME~1\user\LOCALS~1\Temp\2\ismp001\1923345.tmp (The system cannot find the path specified)] -------------------- Contacting StarQuest -------------------- Please use the following methods to contact StarQuest Ventures if you need to obtain a license key, or have suggestions or need information about StarQuest products. If you need to obtain a license key and have access to the Internet, the License Configuration utility included with Data Replicator offers an online licensing feature. StarQuest Ventures, Inc. PO Box 1076 Point Reyes Station, CA 94956 Telephone: 415-669-9619 FAX: 415-669-9629 Email: contact@starquest.com Web: http://www.starquest.com -------------------------- Known Issues for SQDR v3.4 -------------------------- ---------------- Revision History ---------------- 3.40.0410 4/10/08 10174 DNS/TCP checking code should not throw SEVERE message unless the issue prevents connectivity. 10306 Detect incorrect journal settings 10329 i5/OS v6r1: Ignore "F CB" after row deletes 10170 send email notification to starquest if "support" files are posted 10245 Detect invalid logging options for files when adding a subscription 10358 issue w/IR subs if daylight savings time is not set correctly 10366 Treat Duplicate Subscription as warning not error 10372 CHANGES & HEALTHCHK: use internet address of local host without name looku 10234 Installer: verify existence of SQL Catalog tables when installing 10263 Installer: misleading error msg after changing email notification checkbox 10297 Installer changes for i5/OS v6r1 9947 Installer: check that exec-user has access to its home directory 10376 Split CADLTRCV into two programs with different ownership 10377 Installer: Change ownership of CADLTRCV1, grant *EXECUTE authority 10378 flag subscription as altered if journal option is not acceptable 3.37.1212 12/12/07 repackage of 3.37 with new JRNLREADER 10306 Detect incorrect journal settings 3.37.1030 10/30/07 10221 Return error on TableInfo call if Catalog Tables not found 10258 Data type mismatch error on getShort 10204 dump journal/receiver sequence numberinformation when unexpected log records 3.36.0731 7/31/07 9670 need option to FTP/email relevant product files to customer support 10100 Remove "unnecessary" dependency on local TCP/DNS configuration 10108 Display the job CCSID when starting the capture agent 10110 Provide a more robust verification of the local communication channel 10111 Unknown log format causing tables to be flagged 3.35.0402 4/2/07 10005 support SP access to log via RMI 10018 provide status of subscriber/subscription acknowledgment via AgentUtil 3.34.0206 9986 Allow add and overide of primary keys AgentUtil: add StarSQL for Java to JDBC driver search 3.33.0117 9558 TableInfo specifies "with hold" incorrectly for result sets 9955 Use return statement in favor of exit in TABLEINFO SP 9968 TABLEINFO incorrectly identifies Primary Keys 3.32.1229 9768 DB2/400 reporting Cursor not open error while SQDR polls for Changes 9950 Check name resolution of Capture Host when starting up Capture 9951 Quit after "n" attempts to create CAQ