DB2 Everyplace Version 8.2 Fix Pack 5 Readme

Welcome to the DB2® Everyplace® Version 8 Release 2 Fix Pack 5 Readme.

This document describes the enhancements in, and fixes that are addressed by, DB2 Everyplace Version 8 Release 2 fix pack 5 (hereafter referred to as DB2 Everyplace V8.2.5). It also provides instructions for installing, configuring and uninstalling DB2 Everyplace V8.2.5, and instructions for installing DB2 Everyplace on SuSE Linux® 9.1, AIX® 5.3, Solaris 10, and Red Hat Enterprise Linux 4. A list of known defects and restrictions is also documented.

Contents

IBM DB2 Everyplace Enterprise Edition Version 8.2.5 Release Notes
Fixes contained in this fix pack
Installation and configuration instructions
Uninstalling DB2 Everyplace V8.2.5
Known considerations and restrictions
Trademarks

Fixes contained in this fix pack

The following APARs are fixed in DB2 Everyplace V8.2.5.

APARs

  • APAR IC50152: When you use the iUpgrade utility to update the database engine or DB2 Everyplace Sync Client, the iUpgrade utility will keep sending the request until it fails with the "Network Error" message.
  • APAR IC50717: For a JDBC subscription, if the database URL is very long (the maximum length depends on the screen resolution, but it is usually between 200 and 245), when you try to edit the subscription, the whole Edit panel appears as a blank panel and does not respond. The same problem happens to file subscriptions if the file name is very long (the maximum length depends on the screen resolution, usually around 160).
  • APAR IC51180: If a table contains a large number of rows that have been updated or deleted, performing a REORG TABLE operation on the table might cause index corruption. Executing a statement that uses the corrupted index to access the table fails with SQLState 58004, native error -1.
  • APAR IC51701: The DB2 Everyplace database engine might return SQLState 58005 (native error -8190) when accessing tables in a database that was created using DB2 Everyplace version 8.1.2 or earlier.
  • APAR IC51704: If a database is stored on a removable external storage device (such as a USB stick), and the device is being removed prior to disconnecting from the database, the DB2 Everyplace database engine might stop abnormally when trying to close the database connection. This error only happens on Linux platforms, and results in a segmentation fault.
  • APAR IC51708: On Windows Mobile 2005 devices, the database engine performance for DML operations (insert/update/delete) is very slow, even if the database is stored in device-internal memory.
  • APAR IC51713: For certain queries that contain predicates allowing for multiple indexes to be used during query processing, DB2 Everyplace database engine might not always select the appropriate indexes to generate the most efficient access plan. This might lead to slow performance for these queries.
  • APAR IC51717: The DB2 Everyplace database engine allows applications to force immediate close of connections with the SQL_ATTR_FORCE_DISCONNECT connection attribute. This might not work properly if the connection to be closed is currently processing a long-running query that involves the creation of temporary tables. Examples for such queries are complex SELECT statements or queries that generate scrollable result sets. If such a connection is forced to be closed by calling SQLDisconnect(), it might take some time for SQLDisconnect() to return control to the application.
  • APAR IC51719: When the user tries to modify properties of a source database in JDBC subscriptions with XML scripting tool, the new properties are not applied to the DSY.JDBC_MASTER table in DSYCTLDB and the XML scripting tool does not report the error.
  • APAR IC51890: The subscription cannot be deleted if there is an alias on the dsy.EHxxx table in mirror database and the schema name and table name of the alias happen to be the same as the source table. The delete panel is displayed as a blank panel.
  • APAR IC52074: If a master conflict happens, Sync Server will send a conflict reject message to Sync Client. And Sync Client will notify the conflict reject event to the user application through ISync.NET API. When ISync.NET API (in function syncListenerF) handles the conflict reject event, an exception is thrown out.
  • APAR IC52226: The command DSYConfig update-config chooses the wrong dsyconfig.properties file. It should use <instance_dir> instead of the <install_dir>.
  • APAR IC52298: During data synchronization to a SD card on a Palm OS device, DB2 Sync indicated that synchronization succeeded, but there was no data in the client database.
  • APAR IC52486: Under logic delete mode, after you insert a few records ($dirty=2) into a table that has original records ($dirty=0), if you delete and insert all these records again, you will get different record counts of this table between table scan and count(*) function. If you delete and insert the same records again for many times, database engine will fail with SQLState 58004, native error -8667.
  • APAR IC54135: If a database create more than 86 tables on Palm OS 5.4 hidden volume root directory, the DB2 Everyplace database engine might stop abnormally. This error only happens on Palm OS 54 platforms, and results in a device reset.
  • APAR IC54247: If a user tries to synchronize more than 32 tables to Palm OS 5.4 devices, Sync Client could only synchronize 32 tables to the device, and the synchronization will fail with 413 error.
  • APAR IC54915: If the user does not use database selection button to set mirror database and just fill in all the information on mirror page, after the password field is filled in, the test connection button is still disabled. It should be enabled.
  • APAR IC54916: DB2 Everyplace Java Sync Client cannot execute the lock table SQL statement successfully if the lock table is triggered. The failure information is recorded in the trace-isyn file similar to the following 2007-10-23 10:19:39.171 DSYC400E: Failed to lock tables SQL Exception.
  • APAR IC54924: Synchronization might fail when Sync Client syncs from an old client data image that is copied from another client.
  • APAR IC54926: If a user updates two rows in the same ADO.NET DataSet, the value in the second row will be partially overwritten by the value in the first row.
  • APAR IC54971: Under physical delete mode, DB2 Everyplace database engine has done some optimization work on statement DELETE FROM tablename. It would delete the whole table file and recreate it. If you terminate the operation of DELETE FROM tablename inside a transaction under physical delete mode, after the database recovers, you might get the SQLState 58005 (-1) on operations on this table.
  • APAR IC55057: When dsysample.sh is run to create sample subscriptions for DB2 Everyplace on UNIX/Linux systems, the process won't exit even when the verification of parameters fails.

Installation and configuration instructions

This section contains instructions for installing and configuring DB2 Everyplace V8.2.5.

The application of DB2 Everyplace V8.2.5 involves two major steps:

  1. Installing and updating the server configuration.
  2. IBM® WebSphere® Application Server only: updating the DB2 Everyplace application.

If DB2 Everyplace is installed on an external application server, instead of the embedded application server that comes with DB2 Everyplace, the DB2 Everyplace application must be updated on the application server.

Important: The following changes are not preserved when you migrate to DB2 Everyplace V8.2.5:
  • The Java™ classpath to drivers for non-DB2 JDBC data sources
  • Customizations to ports used by the WebSphere Embedded Application Server - Express

Follow the instructions in the Sync Server Administration Guide for the settings.

Fix pack 5 is available as a self-extracting executable for Windows® systems and as tar files for UNIX® systems. The client files are also available in a separate file, clients_8_2_5_0.zip. The zip archive contains files for all the languages on each supported mobile device platform. The zip archive is provided for users who would like to download only the client files. This fix pack can be applied to all editions of DB2 Everyplace V8.2, and updates only the DB2 Everyplace components that were previously installed on your system. Fix pack 5 includes updates for DB2 Everyplace Sync Server and all DB2 Everyplace client components. The documentation has been updated for this fix pack, but it is not included with the fix pack files. The latest documentation is available on the DB2 Everyplace Web site at http://www.ibm.com/software/data/db2/everyplace/library.html.

Pre-application considerations

When you install DB2 Everyplace V8.2.5, ensure that you meet the following dependencies.

  • Fix pack 5 must be applied on all systems on which DB2 Everyplace is installed.

    For example, in a distributed environment, apply fix pack 5 to both the distributed database workstation and the distributed server. In a cluster environment, fix pack 5 must be applied to all nodes in the cluster.

  • The order in which you apply fix pack 5 (installation and server configuration update) is critical. For example:
    • In a distributed environment, the server configured for the Distributed database must be applied first, followed by the server configured as the Distributed server.
    • In a remote administration environment, the server that is configured in order to run the DB2 Everyplace Sync Server must be updated first followed by the server configured for Remote Administration of Mobile Devices Administration Center.
    • In a cluster environment, the main node (which has the Network Deployment manager installed) must have fix pack 5 applied first followed by the rest of the nodes.
  • For systems that have DB2 Everyplace Enterprise Edition or Express Edition installed, you must update the server configuration successfully prior to starting DB2 Everyplace processes (for example, the DB2 Everyplace Sync Server, and the Mobile Devices Administration Center). If the configuration wizard fails to configure successfully, use the command line configuration tool to complete the configuration process.
  • Fix pack 5 updates files for the mobile devices. These updates must be deployed to each mobile device. Follow the instructions in DB2 Everyplace Installation and User's Guide or the DB2 Everyplace Information Center.

Installing and configuring DB2 Everyplace V8.2.5

Follow these steps to install and configure DB2 Everyplace V8.2.5 on Windows and UNIX.

Prerequisites:
  • Stop all DB2 Everyplace processes. For example, stop the DB2 Everyplace Sync Server and the Mobile Devices Administration Center.
  • If you are using WebSphere Application Server, stop the DB2 Everyplace application server.
  • Stop all native operating system processes accessing DB2 Everyplace files. For example, stop Windows Explorer.

For Windows

  1. Log in to Windows as a user with Windows administrative authority.
  2. Download the file DB2Everyplace_8_2_5_0.exe into a temporary directory, and double-click the file. DB2Everyplace_8_2_5_0.exe is a self-extracting executable that places the DB2 Everyplace files under %PROGRAMFILES%/DB2Everyplace_8_2_5_0 and launches the Update Installation Wizard.
  3. Follow the Update Installation Wizard prompts. The wizard applies updates only to the DB2 Everyplace components that have been previously installed on the system. If the DB2 Everyplace installation has been successfully configured, the Update Installation Wizard informs you that it is ready to update the server configuration.
    • For distributed configurations: If you are using DB2 Everyplace in a distributed database configuration, you do not need to update the configuration of DB2 Everyplace. Click Cancel to skip the configuration process.
    • For all other configurations: Click Next to update the system configuration. If the configuration update process fails, you must manually update the configuration prior to using DB2 Everyplace Sync Server processes.

For UNIX

  1. Download DB2Everyplace_8_2_5_0_<platform>.tar in a temporary directory, where <platform> is:
    • aix for AIX-based systems
    • linux for Linux-based systems
    • iLinux for iLinux-based systems
    • solaris for Solaris-based systems
  2. Log in as the root user.
  3. Untar the DB2Everyplace_8_2_5_0_<platform>.tar file in a temporary directory.
  4. Execute DB2EveryplaceUpdateInstallerWizard.sh located in the DB2Everyplace_8_2_5_0_<platform>.tar directory that was created as a result of step 3. This script launches the DB2 Everyplace Update Installation Wizard, which applies the fix pack 5 updates to DB2 Everyplace V8.2.
  5. Follow the Update Installation Wizard prompts. The wizard applies updates only to the DB2 Everyplace components that have been previously installed on the system.
Important: After you install fix pack 5, only the root users can read the Javadocs located in the <DSYPATH>/doc/doc directory. Change the permission of those Javadocs to 755 so that the other users can view the javadocs.

Updating the server configuration manually

If the configuration update was cancelled or failed during the fix pack installation, follow these steps to update the server configuration manually.

Prerequisites: You must execute this task only if the configuration update was cancelled or failed during the fix pack installation. If the configuration update fails, correct the errors in the log files indicated on the Update Installation Wizard panel before you complete this task. You can skip this task if your workstation does not have the DB2 Everyplace Sync Server support installed.

For Windows

  1. Log in to Windows as a user with Windows administrative authority.
  2. Open a command window. Change the directory to <DSYPATH>/config where <DSYPATH> is the root installation directory for DB2 Everyplace.
  3. Issue the command: DSYConfig update-config

    This command updates the DB2 Everyplace Sync Server configuration. If you get any errors, refer to the trace file ConfigTrace.log located in the <DSYPATH>\log directory. After you have corrected the error that is listed in the trace file, run the DSYConfig update-config command again.

For UNIX

  1. Log in as the root user.
  2. Open a shell. Change the directory to <DSYPATH>/config, where <DSYPATH> is the root installation directory for DB2 Everyplace.
  3. Issue the command: DSYConfig update-config

    This command updates the configuration for all of the DB2 Everyplace Sync Server instances that are created on the system. If you get any errors, refer to the trace file ConfigTrace.log located in the <DSYPATH>\log directory. After you have corrected the error that is listed in the trace file, issue the DSYConfig update-config command again.

Updating the DB2 Everyplace application when run from the WebSphere Application Server

If you are using IBM WebSphere Application Server, follow these steps to update the DB2 Everyplace application.

  • For WebSphere Application Server Version 6 only: When you are prompted for the relative path to the application, use the relative path of the currently-installed DB2 Everyplace application.
  • The location of the new DB2 Everyplace WAR file: <DSYPATH>/config/work/was/IBM_DB2_Everyplace.war.
  • The context root for theDB2 Everyplace application (/db2e).
Tip: In the WebSphere Administration console, most of the changes that you need to make are found on the Preparing for Application Installation page in WebSphere Application Server Version 6 and Preparing for Application Update page in WebSphere Application Server Version 5. You can get there by selecting Applications > Enterprise Applications on the left frame of WebSphere Administration console. In the right frame, select the check box next to the DB2 Everyplace application and click Update.

Do the following:

  1. Update the WebSphere Plug-in Configuration file. On the command line, execute: <WAS_HOME/bin/GenPluginCfg.[bat/sh]
  2. For WebSphere Application Server Version 6 only: Execute the configurewebserver1.[bat/sh] script to associate the new DB2 Everyplace configuration with the web server. This script can be found in the WebSphere Application Server plug-in installation directory.
  3. Start or restart the DB2 Everyplace application server.

Uninstalling DB2 Everyplace V8.2.5

This section describes how to uninstall DB2 Everyplace V8.2.5.

For Windows

  1. Log in to Windows as a user with Windows administrative authority.
  2. Download DB2Everyplace_8_2_5_0.exe into a temporary directory. DB2Everyplace_8_2_5_0.exe is a self-extracting executable that places the DB2 Everyplace files in %PROGRAMFILES%/DB2Everyplace_8_2_5_0 and launches the Update Installation Wizard.
  3. Follow the Update Installation Wizard prompts. Select Uninstall to uninstall DB2 Everyplace. The wizard uninstalls the fix pack and restores the DB2 Everyplace components to the version that you had previously installed on your system. It also configures the system with the previous version.

For UNIX

  1. Download DB2Everyplace_8_2_5_0_<platform>.tar into a temporary directory.
  2. Log in as the root user.
  3. Untar the DB2Everyplace_8_2_5_0_<platform>.tar file in a temporary directory.
  4. Execute DB2EveryplaceUpdateInstallerWizard.sh located in the DB2Everyplace_8_2_5_0_<platform> directory that was created as a result of step 3. This script launches the DB2 Everyplace Update Installation Wizard.
  5. Follow the Update Installation Wizard prompts. Select Uninstall to uninstall DB2 Everyplace. The wizard uninstalls the fix pack and restores the DB2 Everyplace components to the version that you had previously installed on your system. It also configures the system with the previous version.

If you use IBM WebSphere Application Server, you must update the DB2 Everyplace application. See Updating the DB2 Everyplace application when run from the WebSphere Application Server for more information about this task.

Support for SuSE Linux 9.1, AIX 5.3, Solaris 10, and Red Hat Enterprise Linux 4

This section contains instructions for installing DB2 Everyplace on SuSE Linux 9.1, AIX 5.3, Solaris 10, and Red Hat Enterprise Linux 4.

Important: Do not configure DB2 Everyplace V8.2 after you install it. Instead, install fix pack 5 first. Configure the installation only after you have applied both DB2 Everyplace V8.2 and DB2 Everyplace V8.2.5.
  1. Install DB2 Everyplace V8.2.
    1. Log in as the root user.
    2. Change to the directory of the DB2 Everyplace V8.2 installation image.
    3. Issue the following command:

      dsysetup

      This command starts the DB2 Everyplace Launchpad. Follow the instructions in Installation and User's Guide to install DB2 Everyplace V8.2.
      Remember: After you install DB2 Everyplace V8.2, click Cancel to exit the wizard. Do not configure V8.2.
  2. Install DB2 Everyplace V8.2.5.
    1. Log in as the root user.
    2. Change to the directory of the DB2 Everyplace V8.2.5 installation image.
    3. Start the DB2 Everyplace Update Installer Wizard by issuing the following command:

      ./DB2EveryplaceUpdateInstallerWizard.sh

    4. Install the fix pack by following the wizard prompts. After you install the fix pack, the Update Installer Wizard asks you whether you want to configure your installation.
    5. Click Next to launch the DB2 Everyplace Configuration Wizard.

Known considerations and restrictions

This section contains known defects in this release of DB2 Everyplace. It also provides information on any fix or workaround that exists for these limitations and issues.

Installation and configuration

  • V8.2:
    • The DB2 Everyplace V8.2 Uninstallation Wizard does not uninstall the files that were modified by subsequent fix packs applied to the system. The files under the <DSYPSATH>\Clients and <DSYPSATH>\version directories will not be deleted and will remain on the system even after you uninstall V8.2. You must delete the DB2 Everyplace installation directory, <DSYPSATH>, before re-installing DB2 Everyplace V8.2.
    • On UNIX systems, re-configuration fails for the configuration of the control database when the DB2 Everyplace fix pack is uninstalled and restored to DB2 Everyplace V8.2. In order to recover from this error, drop the instance and create it again.
  • V8.2.5:
    • If the default shell is /bin/sh, the configuration tool might display the following error message when attempting to drop a Sync Server instance: Exception received while updating the login file. Exiting.... Even if the configuration failed, the instance has been dropped. To clean up the environment, delete the four lines that were added by the DB2 Everyplace configuration tool in the file .profile.
      Important: Even if the configuration tool drops the instance successfully without showing the error message, you must perform the manual cleanup step as described above.
  • The DB2 Everyplace Sync Client V8.1.4.2 and V8.1.4.3 are not compatible with V8.2.5 of the DB2 Everyplace Sync Server. You must upgrade the DB2 Everyplace Sync Client to V8.1.4.4 or V8.2.5.
  • When you connect a mobile device to the network using ActiveSync Version 3.7, the network connection might fail after a few synchronizations. Disconnect and reconnect in ActiveSync Version 3.7 to reestablish a usable network connection.
  • The IUpgrade application for Symbian mobile devices is available only in German, English, Spanish, French, and Italian.

DB2 Everyplace Sync Server

  • On Windows, after you refresh an item in the left panel of Mobile Devices Administration Center, an ellipsis "..." might display as part of the item name. For example, Users might change to be Users... or .... Try refreshing the panel to display the item names.
  • Do not use the join filter feature for key-only tables. Key-only tables are the tables in which all columns are part of the primary key.

DB2 Everyplace database

  • The installer does not update the Polish version of the Symbian 7 database. You must retrieve those files from the clients_8_2_5_0.zip file.
  • The Japanese version of the sample application VNurse for PalmOS does not initialize properly during startup. SQLSTATE 42704 is returned.

Documentation

  • If the Sync Server Help page is started in an Internet Explorer browser under Windows XP, the browser displays the following warning: "To help protect your security, Internet Explorer has restricted this file from showing active content that could access your computer. Click here for options...". To display the content, click the warning message and choose the option that shows the Sync Server Help page.

Trademarks

The following terms are trademarks of the International Business Machines Corporation in the United States, or other countries, or both.

AIX
DB2
Everyplace
IBM
WebSphere

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.