DB2 Everyplace Version 8.2 Fix Pack 4 Release Notes

Support for Palm OS 5.4

Support the new U.S. Daylight Saving Time rules

This release of DB2 Everyplace integrated the latest IBM^? Java? SDK, which supports the U.S. Daylight Saving Time 2007 change. This features ensures that applications will retrieve the correct time when the new rules go into effect.

APARs

• APAR IC48949: Reserved word "MODE" is not allowed as an identifier.
• APAR IC48959: Possible data corruption on Windows^? CE if the database is stored on a storage card.
• APAR IC49108: If an application uses a large number of statements with scrollable cursors, the following events might cause the DB2 Everyplace database engine to terminate abnormally:
  • A call to the CLI SQLFetch() function
  • A call to the JDBC ResultSet.next() method
  Under rare circumstances, random corruptions of the database might happen. In this case, the database engine will return SQLState 57011 (native error code -7183).
• APAR IC49118: An application that issues queries requiring the materialization of temporary results might experience performance degradation. Examples of such queries are those queries that contain a GROUP BY clause or an ORDER BY clause that is not supported by an index and queries generating a scrollable cursor or a scrollable JDBC ResultSet.
• APAR IC49192: Messages from incomplete synchronization might not be deleted from the message database.
• APAR IC49196: Symbian7 and Symbian7s DB2eCLP stops when it displays the columns of a table that includes long CHAR or VARCHAR data types.
• APAR IC49277: When the structure of a database file is not in the correct format, the database engine stops without returning an error code.
• APAR IC49771: If you use the $file command to run an SQL script that contains the connect to command, DB2eCLP will return the error message Could not get sqlstate! for subsequent commands that you run at the DB2eCLP command prompt.
• APAR IC49916: The DB2 Everyplace Sync Client abnormally stops during file synchronization if the absolute filename path on the client is 100 characters or longer.
• APAR IC49991: Incorrect data message might be sent to clients after prior synchronization failures, and this message will cause DB2 Everyplace Sync Client to report DSYC414E: Unexpected end of data.
• APAR IC49992: After a NULL value is inserted into an index column, the database engine cannot retrieve the information correctly. When trying to delete the data from table after the insertion, the database engine will return SQLState 58004 (native error code -8667).
• APAR IC50002: Executing a query through a recently established database connection might return SQLState 58004 (native error -1) if the database engine was stopped abnormally before this connection was established. If there are leftover temporary files (DSY_ResultXX and DSY_iResultXX) that have not been removed from the file system because the database engine terminated abnormally, issuing another query that requires temporary tables might fail. However, subsequent executions of the same query through the same database connection will succeed.
• APAR IC50025: The DB2 Everyplace database engine might not access files correctly on devices running Microsoft^? Windows Mobile 5.0 platform. Because of the introduction of flash-based permanent storage in Windows Mobile 5.0, the database engine needs to implement certain precautionary measures when interacting with the file system. However, this scheme does not work properly if the database is stored locally on the device instead of on an external storage card. As a result, there might be data integrity issues if a device failure (e. g. a soft reset or power loss) occurs during heavy database engine activity.
• APAR IC50060: After the column length is changed using the alter table command, the column length information in the syscolumns table is not updated.
• APAR IC50350: If an administrator resets users or groups that have Data Propagator subscriptions defined, after the users perform synchronization, the data of the tables in the Data Propagator subscriptions will be cleared on devices.
• APAR IC50368: Mirror database prune task might reset some devices incorrectly. It happens under the following condition: the mirror prune task is enabled (MaxSyncPeriod.Days is set to a positive value), filters are defined for subscriptions and join filter feature is enabled. If the administrator deletes the old device IDs that are related with a user in Mobile Devices Administration Center, the next time when the user performs synchronization, a new device ID will be generated for the user and a refreshing synchronization will be initiated to retrieve all the data from the server side. If the mirror prune task runs at the time exactly when the refreshing synchronization is being processed, this device will be reset.
• APAR IC50471: Client update might be overwritten by the server incorrectly if horizontal mirror filter is defined and join filter feature is enabled on the table which is updated. The problem happens in the follow scenario:
  1. A customer inserts or updates a data record in a mobile device.
  2. The customer performs synchronization and the update is transmitted to the server side.
  3. The replication is completed on the server side.
  4. The customer updates the same record that they updated in step one.
  5. The customer performs synchronization. After the synchronization, the record that is updated in step 4 might be overwritten and the values change back to what they are before step 4's update.
• APAR IC50596: After you upgrade the DB2 Everyplace database engine on a client device (for example, from version 8.2.2 to 8.2.3), you might notice memory leaks the first time that the new DB2 Everyplace database engine is used on an existing database. The memory leaks disappear the second time that the new DB2 Everyplace database engine is used on the database.
• APAR IC50698: When the DB2 Everyplace Sync Server is running on a Linux operation system, especially on Linux kernel 2.4, the replication thread might exit abnormally. In this case, the replication between the mirror database and the source database stops. You can find the exceptionCOM.ibm.db2.jdbc.DB2Exception:[IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE=08003 in trace files.
• APAR IC50717: For a JDBC subscription, if the database URL is very long (the maximum length depends on the screen resolution, but the maximum is usually between 200 and 245 characters), when a customer tries 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, but the maximum is approximately 160 characters).

For Windows

1. Log in to Windows as a user with Windows administrative authority.
2. Download DB2Everyplace_8_2_4_0.exe into a temporary directory. DB2Everyplace_8_2_4_0.exe is a self-extracting executable that places the DB2 Everyplace files in %PROGRAMFILES%/DB2Everyplace_8_2_4_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_4_0_<platform>.tar into a temporary directory.
2. Log in as the root user.
3. Untar the DB2Everyplace_8_2_4_0_<platform>.tar file in a temporary directory.
4. Execute DB2EveryplaceUpdateInstallerWizard.sh located in the DB2Everyplace_8_2_4_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 Applicatio Server for more information about this task.

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.4:
  • 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.4 of the DB2 Everyplace Sync Server. You must upgrade the DB2 Everyplace Sync Client to V8.1.4.4 or V8.2.4.
• 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_4_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.