STARQUEST DATA REPLICATOR PLUS for DB2 UDB v3.37 October 2007 (c)Copyright 1994-2007 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 DB2 UDB, the newest member 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. SQDR Plus for DB2 UDB also provides the following advanced features: * Comprehensive statistics and easy-to-use graphical interface and Wizards. * Enterprise-level security, allowing only operations that are permitted by the operating system, database system, and network. * Ability to replicate what you want, when you want, with horizontal and vertical partioning and flexible subscription scheduling. * Ability to “mirror” the source database. In addition to configuring how frequently SQDR Plus polls for changes to the source database you can 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. * Ability to restrict which database tables can be subscribed to for replication. SQDR Plus provides centralized control for publishing and unpublishing database tables. If you enable the publishing feature, SQDR users can create replication subscriptions only to tables that have been published for replication. This ReadMe.txt file contains important information about installing SQDR Plus for DB2 UDB. Refer to the SQDR Plus for DB2 UDB 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 DB2 UDB o Contacting StarQuest Technical Support o Known Issues ------------------- System Requirements ------------------- Following are the requirements for installing SQDR Plus on a UNIX or Windows system running DB2 for UDB: • DB2 UDB for Linux, UNIX and Windows v8.2 with FixPak10 or later, or v9.1 or later. • Java Virtual Machine (JVM) installed and specified in the PATH. JVM 1.4.2 or later is required during installation, and recommended for use by the Capture Agent and Java stored procedures. • A Linux, UNIX, or Windows operating system version that meets the system requirements for the version of DB2 UDB that you are running. See the IBM Web site, http://www-306.ibm.com/software/data/db2/udb/sysreqs.html, for detailed system requirements for DB2 UDB and to obtain the latest DB2 UDB fixes. Please contact StarQuest at contact@starquest.com if you wish to run SQDR Plus on a platform other than one of the currently supported platforms listed below. Platforms * Windows Server 2003, Windows XP, Windows 2000 * Linux x86 * Linux x86-64 (AMD64 & Intel EM64T) * Solaris SPARC 8 & later * HP-UX PA-RISC 11.11i & later * AIX 5.2 & later ---------- What's New ---------- -------------------------------- Installing SQDR Plus for DB2 UDB -------------------------------- The SQDR Plus installer requires a GUI environment. On a UNIX computer, this means configuring X Windows or VNC (Virtual Network Computing). The Java JVM should be installed and in the PATH. (Enter java at the command line to verify that Java is installed and can be located.) The "db2" command should be in your path, and on UNIX, you should initialize the the DB2 environment by sourcing db2profile or db2cshrc in the sqllib directory of the DB2 instance owner. In addition, you may need to perform additional steps on UNIX to enable Java stored procedures within DB2. Refer to the SQDR Plus for DB2 UDB guide for more information. The SQDR Plus for DB2 UDB installer consists of data1.jar, media.inf, and the batch/shell scripts setup.bat and setup. Copy these files to the computer from which you are running the installation. Execute the batch or shell script, depending on whether you are running the installation from a Windows or UNIX computer. 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.3 -------------------------- * The installer prompts for a tablespace to be used for the SQDR control tables. This value is not currently used. * "Option 6 - Start Capture Agent" of the Capture Agent Maintenance Utility (CAMAINT) does not start the Capture Agent service. On Windows, use the Services control panel (in Administrative Tools) to start the Capture Agent. On UNIX, use the appropriate rc script e.g. # /etc/init.d/sqdr-MYRDB start * If you select "Allow SQDR to Manage Logs" during installation, which installs an exit program in the database, and later uninstall the SQDR Plus product, you must change the logging of your database to an appropriate setting (e.g. cirular or archive logging); the exit program will not function after removing SQDR Plus. * Shortcuts on UNIX may not function. There are alternate methods of performing the same functions; refer to the SQDR Plus for UDB Users Guide. * There is a known IBM bug (APAR JR24668) in UDB 8.2 fixpak 13 that causes incorrect operation if you select "Allow SQDR to Manage Logs". If you plan to use SQDR-managed logs, upgrade to fixpak 14 or later. * On AIX, you must use a 32 bit JVM during installation. * On Linux for x86-64, we recommend the use of a 64 bit JVM during installation. * If are using DB2 9.1 on Linux for x86-64, and choose managedLogs, you must use a 64 bit JVM during installation. If you run the installer with a 32 bit JVM, the wrong exit program will be installed. To verify that the correct exit program was installed, run the following command: # file ~/sqllib/adm/db2uext2 The result should be: db2uext2: ELF 64-bit LSB executable, AMD x86-64 * On Windows for x86-64, we recommend the use of a 32 bit JVM during installation. The Capture Agent uses a 32 bit JVM during operation, and it is important that the same bitwidth JVM be used during uninstall or upgrades as that used during the original installation. * The following issue has been noticed on Windows Server 2003 x64: If the Program group shortcut for "Capture Agent Maintenance" does not function, examine the properties of the shortcut (right click on the shortcut and select Properties). If java.exe is not located in the directory listed in the shortcut, change the shortcut to use a directory that does contain a JVM. For example, on Windows Server 2003 x64, the shortcut may be trying to invoke "C:\Windows\java.exe"; change this to "C:\Program Files\IBM\SQLLIB\java\jdk\bin\java.exe". ---------------- Revision History ---------------- 3.37.1030 10/30/07 10204 dump journal/receiver sequence numberinformation when unexpected log records 10232 add uninstaller JRE resolution for JRE 1.6 & 1.7 3.36.0813 8/13/07 9670 need option to FTP/email relevant product files to customer support 10100 Remove "unnecessary" dependency on local TCP/DNS configuration 10110 Provide a more robust verification of the local communication channel 10111 Unknown log format causing tables to be flagged 10027 UDB Installer: change backslash to double backslash for qualified userID 10126 UDB Installer: camaint changes for ftp option 3.35.0402 4/2/07 10005 support SP access to log via RMI 10006 log UDB GetChanges return information 10018 provide status of subscriber/subscription acknowledgment via AgentUtil 10028 UDB Installer: need mechansim to change DB2 userID