IBM^(R) DB2^(R) Everyplace Version 8.2, fix pack 1

Release Notes

DB2 Everyplace release notes for version 8.2, fix pack 1

Welcome to the DB2 Everyplace Version 8.2 release notes for fix pack 1.

These release notes contain information about new features, enhancements, and fixes to the Version 8.2 release of the DB2 Everyplace.

Application instructions

The application of DB2 Everyplace version 8.2, fix pack 1 involves two major steps:

1. Installation and update of the server configuration
2. For IBM WebSphere Application Server users only, update 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.

Fix pack 1 is available as a self-extracting executable for Windows systems and a tar file for Unix systems. The client files are also available in a separate file, clients_8214.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 Version 8.2, and updates only the DB2 Everyplace components that were previously installed on your system. Fix pack 1 includes updates for DB2 Everyplace Sync Server and all DB2 Everyplace client components. The documentation has not been updated in this fix pack.

Pre-application considerations

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

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

• The order in which you apply fix pack 1 (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 1 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 prior to starting DB2 Everyplace processes (for example, the DB2 Everyplace Sync Server, and the Mobile Devices Administration Center).
• Fix pack 1 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.

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.

To install and configure DB2 Everyplace Version 8.2, fix pack 1:

• For Windows:
  1. Login as a user with Windows administrative authority.
  2. Download the file DB2Everyplace_8_2_1_4.exe into a temporary directory, and double-click on it. DB2Everyplace_8_2_1_4.exe is a self-extracting executable which places the DB2 Everyplace files under %PROGRAMFILES%/DB2Everyplace_8_2_1_4 and launches the Update Installation Wizard.
  3. Proceed by following the Update Installation Wizard's 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 updates the server configuration. If the server 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_1_4.tar in a temporary directory.
  2. Login as the root user for the following steps. The tar file must be untarred using the root user.
  3. Un-tar the DB2Everyplace_8_2_1_4.tar file in a temporary directory.
  4. Execute DB2EveryplaceUpdateInstallerWizard.sh located in the DB2Everyplace_8_2_1_4 directory that was created as a result of step 3. This script launches the DB2 Everyplace Update Installation Wizard which applies the fix pack 1 updates to DB2 Everyplace Version 8.2.
  5. Proceed by following the Update Installation Wizard's 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 updates the server configuration. If the server configuration update process fails, you must manually update the configuration prior to using DB2 Everyplace Sync Server processes.

To update the server configuration manually:

• For Windows:
  1. Login 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. Execute the command DSYConfig update-config. This command updates the DB2 Everyplace Sync Server configuration. In case of 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. Login 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. Execute 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. In case of 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.

To update the DB2 Everyplace application when run from the WebSphere Application Server:

• 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 the DB2 Everyplace application (/db2e).

Updating an application that has already been installed is a routine task for WebSphere Administrators. Please refer to the WebSphere documentation for more information about this task.

Keep in mind that there are additional steps beyond updating the DB2 Everyplace application. Be sure to do the following:

1. Save the new configuration to commit the changes.
2. Update the WebSphere Plug-in Configuration file. On the command line, execute:<WAS_HOME>/bin/GenPluginCfg.[bat/sh].
3. 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.
4. Start or restart the DB2 Everyplace application server.

To uninstall DB2 Everyplace version 8.2, fix pack 1:

• For Windows:
  1. Login as a user with Windows administrative authority.
  2. Download DB2Everyplace_8_2_1_4.exe into a temporary directory. DB2Everyplace_8_2_1_4.exe is a self-extracting executable that places the DB2 Everyplace files in %PROGRAMFILES%/DB2Everyplace_8_2_1_4 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_1_4.tar in a temporary directory.
  2. Login as the root user for the following steps. The tar file must be untarred using the root user.
  3. Un-tar the DB2Everyplace_8_2_1_4.tar file in a temporary directory.
  4. Execute DB2EveryplaceUpdateInstallerWizard.sh located in the DB2Everyplace_8_2_1_4 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 To update the DB2 Everyplace application when run from the WebSphere Application Server for more information about completing this task.

New features for the DB2 Everyplace Sync Server

New features for the DB2 Everyplace Sync Client

New features for the DB2 Everyplace database

Fixes to the code

This section contains the list of APARs which have been created since the release of DB2 Everyplace version 8.2 and are included in fix pack 1. For detailed information on each APAR, you can perform a search at http://www.ibm.com/software/data/db2/everyplace/support.html.

• APAR IC43236: The Sync Client (all platforms) may terminate abnormally during synchronization if a table with many columns is subscribed (application exits unexpectedly or device locks up). The actual number of columns that causes this problem varies depending on the length of the column names. In the average customer scenarios, it is approximately 200 columns.
• APAR IC43323: If the system administrator renames a file subscription with the Mobile Device Administration Center, clients who have previously synchronized the file subscription will not be able to update the subscription name in a synchronization after the subscription name change.
• APAR IC43356: An interrupted synchronization might result in missing data on the Sync Client.
• APAR IC43357: When creating or editing subscriptions in version 8.2 which have mirror to target device filters and contain multiple table references, the warning DSYD029W appears in the Sync Server logs. This warning is unnecessary and will not be logged after you install fix pack 1.
• APAR IC43380 Customers who have tens of thousands of rows in DSY.LOG and do not have an aggressive pruning schedule may encounter SQL0964C Transaction log for database is full when pruning is invoked.
• APAR IC43382: The type mapping for IBM Cloudscape Boolean types is fixed. IBM Cloudscape Boolean types now map to a DB2 SMALLINT type.
• APAR IC43415: Creating and synchronizing a subscription on a table with an Oracle DATE column fails.
• APAR IC43487: IBM Cloudscape client uses new type mappings that send BLOB types as VARCHAR FOR BIT DATA types. A switch statement in the getObject() method was missing the cases for these types.
• APAR IC43521: A JDBC subscription creation or edit fails in the Mobile Devices Administration Center or XML Scripting tool, resulting in possible corruption to the mirror database.
• APAR IC43536: When you create or edit subscriptions, the following problems occurs:
  • It takes a long time to create or edit subscriptions even when the replicate now option is turned off.
  • The create or edit subscription fails due to insufficient transaction log information in the mirror database. The following error is logged in the Mobile Devices Administration Center log folder: The transaction log for the database is full. SQLSTATE=57011.
• APAR IC43566: When resetting all devices with the dsyreset tool or with the XML Scripting tool, device information is deleted and not reset. This causes the devices to be refreshed the next time they synchronize and the data on the device is lost. Resetting a single device, user, or group does not cause this problem.
• APAR IC43684: Palm HotSync cannot back up two Palm resource files, CryptoPlugin.prc and PBSPkcs11.prc, from a PalmOS device to a host machine. These two PRC files do not have their backup bits set and therefore are not backed up during a HotSync operation.
• APAR IC43966: The DB2 Everyplace database engine fails or gets into an infinite loop when using the CLI function, SQLFetch(). If there is an open cursor on a table and another statement handle causes an implicit REORG on the same table, the next SQLFetch() operation on the open cursor will cause the DB2 Everyplace database engine to abnormally terminate or get into an infinite loop. The same behavior can be observed when a DROP TABLE triggers an implicit REORG on the system catalog tables.
• APAR IC443998: Join queries on decimal columns runs progressively slower on PalmOS devices due to excessive memory allocation/deallocation.
• APAR IC44053: When synchronizing with DB2 Everyplace Sync Server configured on a HTTP/1.0 server, the Sync Client incorrectly reports the connection error (DSYC601E). In addition, if a customized authentication proxy is configured on the server site, the client does not handle authentication cookies correctly, and incorrectly reports either the forbidden server error (DSYC611E) or the authentication error (DSYC304E).
• APAR IC44118: During the creation of a JDBC table subscription to a z/OS DB2 source table, the DB2 Everyplace Sync Server produces an incorrect SQL Statement substring "COLNAME CHAR FOR SBCS DATA(50)". The correct form should be "COLNAME CHAR (50) FOR SBCS DATA". This problem occurs when the DB2 Everyplace Sync Server encounters column of types CHAR, VARCHAR, or LONG VARCHAR with a subtype of "FOR SBCS DATA" or "FOR MIXED DATA" at the source database.
• APAR IC44145: Some or all of the clients may receive time outs during synchronization when a DB2 database is used as the message store.
• APAR IC44146: Conflicts are incorrectly reported for client updates which have been successfully synchronized.
• APAR IC44147: DB2 Everyplace DataPropagator Replication fails during recovery with the following error message logged: DSYS005E Replication failed for database <database>: SQL0803N One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "1" constrains table "DSY.EH<suffix>" from having duplicate rows for those columns. SQLSTATE=23505 .
• APAR IC44223: When using the Sync Client to synchronize the VNurse sample to the Japanese Win32 device, the VNSchedule table is created at a location different from all other tables.
• APAR IC44451: After a REORG operation on a table, the table is no longer accessible. Queries that use an index will return SQLState 58004 or cause the database engine to terminate abnormally.
• APAR IC44580:For Pocket PC databases residing on the secure digital card, there is a chance that using suspend mode will permanently damage your data. This problem occurs when the power is toggled in the middle of a database operation. In some cases the database or part thereof will not be accessible after you resume the operation. The data remains lost, even after you reset and reconnect to the database.
• APAR IC44581: When the connection to a database is abruptly terminated (for example, if the application is killed or a power outage occurs) after a successful table reorganization (triggered either implicitly or explicitly), some index files might be corrupted after the recovery.
• APAR IC44582: After successfully connecting to the database on a secure digital card, every SQL statement fails. Reconnecting to the same database resolves the problem, even though the database is healthy.
• APAR IC44591: Any of the following symptoms might indicate this problem.
  • There are missing committed rows.
  • Existing tables cannot be found in the system catalog.
  • SQL execution hangs, or terminates the application.
  • Data and index files have been wrongly truncated to a file size of 0.
• APAR IC44848: DB2 Everyplace Sync Client Version 8.1.4.2 and Version 8.1.4.3 fail to authenticate against DB2 Everyplace Version 8.2, fix pack 1 Sync Server.
• APAR IC44850: Clients receive a time-out during synchronization, with the server logging the message DSYG001E with the DB2Exception SQL0204N.
• APAR IC44851: A replication process fails to complete successfully. The DB2 Everyplace error message DSYG001E is logged for a DB2Exception SQL0104N, where the token "acs" was found instead of the token "ASC".
• APAR IC44873: The DB2 Everyplace Sync Client erroneously resumes on failed subscriptions. An "internal server error" might occur when the subscription is removed from the Mobile Devices Administration Center, after which the Sync Client resumes and causes the server to send an HTTP 500 error because the subscription no longer exists. The Sync Client should first synchronize the configuration information to detect that the subscription is removed.
• APAR IC45118: Lotus Domino Server Version 6.0 and above does not allow anonymous access to the HTTP server. As a result, the mobile device obtains the server's initial object as an IOR using the HTTP protocol will fail. Instead of using HTTP protocol, DB2 Everyplace now uses the DIIOP protocol.
• APAR IC45399: Some SQL statements might cause the DB2 Everyplace database engine to terminate abnormally. This termination might occur when you use an index scan operation that involves composite indexes, and uses them to evaluate "<=" predicates on columns other than the first column and last column that are supported by the index.
• APAR IC45400: Synchronizations fail if you complete both of the following steps:
  • drop a subscribed table on the mobile device
  • call iscConfigPurge() by clicking on Subscription Set Settings->Purge in DB2Sync
• APAR IC45403: When using the Linux Sync Client, if a row is inserted into the client database that contains the value -2147483648 in an integer column, the row will not be synchronized to the server.
• APAR IC45560: Sync fails with SQLState 58004 or creates inconsistent client and server tables.
• APAR IC45584: When retrieving a BLOB column that is defined to be greater than 32763 bytes from the GetBytes() method of the DB2eDataReader, DB2 Everyplace throws an out-of-memory exception.
• APAR IC45686: The PalmOS limit for memory allocation is 64 KB. If you set the message size close to that limit, the message that is built might be greater than the 64 KB limit. In that case, the Sync Client reports an out-of-memory error.
• APAR IC45847: If your application getHost() or getPort(), the Sync Client API for Java or .NET throws exception EXC_NOT_SUPPORT.
• APAR IC45944: Synchronization fails if all of the following conditions are true:
  • You are using the Sync Client for the Windows CE Version 4.x operating system.
  • The mobile device synchronizes using SSL.
  • The input for the server URL uses a host name, not an IP address.
• APAR IC46160: An application receives a SQLState 58004 in SQLConnect() call after the application issued a large number of database connect and disconnect. This problem occurs only on Linux platforms.
• APAR IC46233: If your database has encrypted tables, you might experience data corruption or SQLState 57011 (native code -7180).
• APAR IC46267: When DB2 Everyplace cannot find the target column name in the control database, DB2 Everyplace hangs. In this case, DB2 Everyplace now uses the source name that is obtained from the source database.
• APAR IC46315: If you specify an incorrect values for the TCP/IP connection port, hostname, user ID, or password for the remote control database, the Configuration Wizard and the command line configuration tool fail. You must specify these values for distributed server configuration, remote administration configuration, and cluster configuration.
• APAR IC46316: When using the DB2 Everyplace Update Tool for the Symbian 7 emulator (Metrowerks CodeWarrior variant), many messages incorrectly appear in the wrong language.
• APAR IC46319: In the DB2 Everyplace Sync Client .NET API, IBM.Data.Sync.DB2e.ConflictReader.GetRejectedRows().GetBytes() returns an incorrect value.
• APAR IC46359: The DB2 Everyplace JDBC driver for Palm consists of two files, DB2eJDBC.prc and DB2eJDBCNatives.prc. On the first HotSync, the files are properly transferred to the Palm device and saved in the user's backup folder on the desktop. On the next HotSync, there is an error in the HotSync log showing "Possible database overwrite problem." In the user's backup folder on the desktop, the DB2eJDBCNatives.prc is missing.
• APAR IC46360: The wrong version of the Symbian JDBC driver was shipped with DB2 Everyplace Version 8.2.1. As a result, DB2 Everyplace Java application might not work.
• APAR IC46374: Mobile devices might receive incorrect data in a table subscription with join filtering enabled when MaxSyncPeriod.days is set.

Known considerations and restrictions

For version 8.2, installation and configuration

• The DB2 Everyplace Version 8.2 Uninstall Wizard does not uninstall the files that were modified by subsequent fix packs applied to the system. The files under the <DSYPSATH>\Clients and <DSYPATH>\version directory will not be deleted and will remain on the system even after uninstalling Version 8.2. The DB2 Everyplace installation directory, <DSYPATH>, must be deleted prior to re-installing DB2 Everyplace Version 8.2.
• On UNIX systems, re-configuration fails for distributed-database-config when the DB2 Everyplace fix pack is uninstalled and restored to DB2 Everyplace Version 8.2. In order to recover from this error, drop the instance and create it again.

For the Sync Server

• DB2 Everyplace synchronization converts table and column names from the source database to uppercase when applying them in the mirror and target (device) databases. In rare cases, this can result in an inability to create a table due to non-uniqueness. In other rare cases it can result in a conversion of a character to multiple characters, as in the case of the German 'sharp s' (ß), which will be converted to 'SS'
• The DB2 Everyplace database does not support a default value clause on the source database for BLOB data types. Source columns which map to DB2 Everyplace BLOB data types, specifically LONG VARCHAR FOR BIT DATA, cannot specify a default value.
• In DB2 Everyplace version 8.1.4 and below, the mapping for Microsoft SQL Server BIT data type is inconsistent between JDBC and upload subscriptions. In JDBC subscriptions, the Microsoft SQL Server data type BIT is mapped to the DB2 Everyplace data type SMALLINT. In upload subscriptions, the Microsoft SQL Server data type BIT is mapped to the DB2 Everyplace data type VARCHAR(1). In DB2 Everyplace version 8.2.1, the BIT is mapped to SMALLINT in both cases. If you desire the old, inconsistent behavior, run the following script and restart the Sync Server: dsysetproperty "DatatypeMappings Generic Target:*" -7="12 VARCHAR"
• The DB2 Everyplace Sync Server does not synchronize times or timestamps with an hour of 24 correctly due to differences in how time is represented in Java and a data source. A time of "24:00:00", for example, is converted to "00:00:00" and causes the data saved in the mobile database to differ from the data saved in the source database. You should avoid using such an hour in your applications. This applies to JDBC, DataPropagator, and upload subscriptions.
• DB2 Everyplace remote stored procedure calls only supports DB2 UDB stored procedures on Windows and Unix platforms.
• If you are using an iSeries Linux system, and the Mobile Devices Administration Center does not start, comment out the entry "::1" in the "/etc/hosts file." This entry identifies the local machine in an IPv6 network. DB2 Everyplace Version 8.2.1 does not support the IPv6 protocol.
• The CLCorrespondent array that is passed to the execute method of the BeforeDbPolicy and AfterDbPolicy policies contains a CLCorrespondent object for each client that has submitted input data for replication and not an object for each client that has synchronized since the last replication. This affects the BeforeDbPolicy and AfterDbPolicy classes in the com.ibm.db2ess.cl package.

• The schema names, column names, and table names of tables that are added to subscriptions cannot be keywords, reserved words, or special registers in SQL, DB2, or the data source.
• IBM Cloudscape and Lotus Domino tables that have columns with non-null default values cannot be included in a subscription.
• To create a JDBC subscription with DB2 on AS/400 (on iSeries server), the user ID for the database connection requires *ALLOBJ privilege on the iSeries machine.
• To create a JDBC subscription with DB2 UDB on z/OS, the user ID for the database connection requires DBADMIN plus CREATEIN privilege for the schema DSY.
• When a JDBC subscription is created on DB2 UDB for z/OS, DB2 Everyplace creates tables and indexes on these tables in the source database. It creates the indexes with the default attributes, so DB2 assigns the index data sets to the default storage groups using default space attributes. Since this can affect the performance of mass inserts, you can alter the attributes of the indexes that start with the prefix DSY. For example:

  ALTER INDEX DSYI19099874167 PIECESIZE 256M using STOGROUP DB2ERSTG PRIQTY 80000 SECQTY 40000

• For all DB2 Everyplace table subscriptions, a mirror database must only replicate with a single source database.
• If a JDBC subscription is defined on a DB2 UDB source table, the "DB2_RR_TO_RS" registry variable of the source database server must be set to "NO."

For the Sync Client

• The DB2 Everyplace Sync Client Version 8.1.4.2 and Version 8.1.4.3 are not compatible with Version 8.2.1 of the Sync Server. Please upgrade the Sync Client to Version 8.1.4.4 or Version 8.2.1.
• When connecting a mobile device to the network using ActiveSync Version 3.7, the network connection might become unusable after a few synchronizations. Disconnect and reconnect in ActiveSync Version 3.7 to reestablish a usable network connection.

For the database

• The DDL and DML operations in auto-commit mode on Palm OS might be slower than previous releases due to data integrity improvement.
• Pocket PC SH4 processor is not supported. Please ignore the installed image that contains the SH4 directories.
• DB2 Everyplace does not support a default escape character. The escape clause must be used to indicate the escape character.
• DB2 Everyplace TIMESTAMP format:

  The DB2 Everyplace database JDBC getString() method called on a TIMESTAMP column returns a timestamp in ISO format "YYYY-MM-DD-HH.MM.SS.ZZZZZZ". This is different from the JDBC timestamp escape format "YYYY-MM-DD HH:MM:SS.FFFFFFFFF". DB2 UDB version 8 JDBC returns a timestamp in the format "YYYY-MM-DD HH:MM:SS:FFFFFF".

• The CryptoPlugin.dll (provided by DB2 Everyplace) requires Microsoft High Encryption Pack for Pocket PC V1.0 (http://www.microsoft.com/windowsmobile/downloads/highencryption.mspx) to work. This pack is part of Pocket PC 2003, but you must install it on Pocket PC 2002. If the CryptoPlugin.dll library is present, but the encryption pack is not installed, applications cannot connect to any database (for example DB2eCLP cannot start). If an application requires encryption, install the Microsoft High Encryption Pack for Pocket PC. If encryption is not needed, delete the CryptoPlugin.dll from the Windows directory on the Pocket PC device.
• For PalmOS, applications that were compiled for DB2 Everyplace Version 8.1.4 and previous releases must be re-linked with the db2e.lib file that is included in DB2 Everyplace Version 8.2 before you can use these applications.

Trademarks

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

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

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