New supported products

Support for the Windows^® Vista operating system

Windows Vista has been tested with DB2 Everyplace database and DB2 Everyplace Sync Client. You can install these two components of DB2 Everyplace on Windows Vista. DB2 Everyplace Sync Server is not supported on it.

Support for Palm OS 5.4

DB2 Everyplace now supports Palm OS 5.4. In Palm OS 5.4, data is stored in the NVFS (non-volatile file system), which ensures data integrity when the battery completely loses power. This new feature includes the following updates:

• The new connection attribute SQL_ATTR_ACCESS_HIDDEN_VOLUME for the CLI function SQLSetConnectAttr()
• The new connection method isEnabledAccessHiddenVolume() for DB2eConnection class
• The new property ISCPROP_DB2eAccessHiddenVolume for the DB2 Everyplace Sync Client API iscServiceOpenEx()

Support for Apache Derby database

DB2 Everyplace Enterprise Edition now supports Apache Derby as a client database. You can use Derby database instead of the DB2 Everyplace database to synchronize data. DB2 Everyplace V9.1.1 includes Apache Derby under the directory <DSYPATH>\Clients\derby, where <DSYPATH> is the root installation directory of DB2 Everyplace. Data type mapping information between Apache Derby and the various source databases is added in the documentation.

Configuration with WebSphere Application Server Version 6.1

Configuring DB2 Everyplace with WebSphere^® Application Server Version 6.1 has been tested and is now supported.

Synchronization

Support for triple Data Encryption Standard (triple DES)

With the support for triple DES, DB2 Everyplace provides enhanced security during data transport.

Support for Type 4 JDBC driver and Type 2 Universal JDBC driver

DB2 Everyplace now supports access to DB2 as a source database through Type 4 JDBC driver and Type 2 Universal JDBC driver.

Support for synchronization of BLOB data types

You can now synchronize BLOB data types between your devices and source databases. Palm OS devices and Symbian devices are not supported for this feature; DB2 for z/OS^® as a source database is not supported either.

Database and application development

Improved query performance

Support for triple Data Encryption Standard (triple DES)

With the support for triple DES, DB2 Everyplace provides enhanced security for tables on mobile devices.

New system catalog base table DB2eSYSINDEXES

This new system catalog base table stores the index information of the database. You can now view the detailed index information by using SELECT statement. When developing applications, you can use the DB2 CLI function SQLStatistics and the JDBC method DatabaseMetaData.getIndexInfo to retrieve the information.

New connection attribute SQL_ATTR_FORCE_DISCONNECT

You can stop long-running database operations by using this new connection attribute.

JSR-169 package

JSR-169 package is necessary to develop Java™ applications with DB2 Everyplace if you use IBM^® J9 virtual machine. DB2 Everyplace includes a JSR-169 package for your convenience.

License changes and new error messages

The Software License Agreement terms are changed in this release. During installation, the license panel will display the complete terms.

The following error messages are new in this release and are available in English only.

DSYC700E: Data too large for synchronization.

DSYM186I: This is a key-only table and the join filter is disabled automatically.

DSYS033E: The device cannot synchronize because the subscription contains BLOB data. BLOB data type cannot be synchronized on Palm or Symbian devices.

DSYS034E: The source data row with primary key value in table table name exceeds data size limit. Either one BLOB in replication is bigger than 4 MB or the row size is bigger than 4 MB because of the BLOB data.

SQLSTATE 08008: Connection is closed.

SQLSTATE 42510: Invalid encryption algorithm.

SQLSTATE HY100: Uniqueness option type out of range.

APARs

• 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. If there are leftover temporary files (DSY_ResultXX, DSY_iResultXX) that have not been removed from the file system due to an abnormal termination of the database engine, issuing another query that requires temporary tables might fail. However, subsequent executions of the same query through the same database connection will succeed.
• APAR IC50014: Using escape characters in a LIKE clause that references an indexed column might cause the DB2 Everyplace database engine to return incorrect results. This only happens if the search pattern specified in the LIKE clause starts with a character different from the underscore (_) or percent sign (%). When the index on the column that's referenced by the LIKE clause is dropped, the same query will return the correct result.
• 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 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 IC50350: If an administrator resets users or groups that have DataPropagator™ subscriptions defined, after the users perform synchronization, the data of the tables in the DataPropagator subscriptions will be cleared on the device side.
• APAR IC50368: Mirror database pruning task might reset some devices incorrectly. It happens under the following condition: the mirror pruning 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 devices' IDs that are related with the user in Mobile Devices Administration Center, the next time when the user performs a synchronization, a new device ID will be generated for the user and a refreshing synchronization will be initiated to retrieve all the data from server side. If the mirror pruning task runs at the time exactly when the refreshing synchronization is being processed, this device will be reset.
• APAR IC50471: Client update could be overwritten by 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 server side.
  3. The replication is completed on the server side.
  4. The customer updates the same record that is updated in step 1.
  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 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 engine is used on an existing database. The memory leaks disappear the second time that the new DB2 Everyplace engine is used on an existing database.
• APAR IC51704: If a database is stored on a removable external storage device (such as a USB stick), and the device is being removed before 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 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 IC51215: On a database that was created with DB2 Everyplace V8.2 and is now used with DB2 Everyplace V9.1, processing a CREATE INDEX statement results in SQLState 42887.
• APAR IC51217: Running a Java application that uses the DB2 Everyplace V9.1 JDBC driver in JRE 1.3 or earlier versions causes a java.lang.NoClassDefFoundError exception to be thrown. This exception is thrown as soon as the JVM starts running such an application. The top of the stack trace looks as follows:

  java.lang.NoClassDefFoundError: java/sql/Savepoint
  at com.ibm.db2e.jdbc.DB2eDriver.connect(DB2eDriver.java:160)
  at java.sql.DriverManager.getConnection(DriverManager.java:512)
  at java.sql.DriverManager.getConnection(DriverManager.java:141)

• APAR IC51232: The DB2 Everyplace database engine might corrupt the content of large BLOBs after a database recovery operation. Parts of a large BLOB might be overwritten with null bytes.
• 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 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 IC517013: For certain queries that contain predicates allowing for multiple indexes to be used during query processing, the 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 you modify properties of a source database in JDBC subscription 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 IC51967: For replication of DataPropagator subscriptions that are created with the same apply qualifier but different mirror databases, you sometimes might notice that data are not replicated to source databases although the replication is successful. You can find apply errors, such as "ASN0552E", in the DataPropagator trace file. However, DB2 Everyplace Sync Server didn't report the apply failure. And you might find that the password file asnpwd.aut becomes very large.
• APAR IC52081: Inserting rows that have null values into an empty table that has a multi-column index defined on it may lead to an inconsistent index. This may only happen under the following conditions:
  1. The first row inserted into an empty table contains a null value in at lest the first indexed column.
  2. At least two more rows that contain a null value in at least the first indexed column are inserted into the table.
  3. At least one of these rows is being updated deleted from the table.
• APAR IC52298: The data could not be synchronized to SD cards on Palm OS devices.
• APAR IC52300: Autoincrement of identity columns does not work for INSERT INTO TABLE1 SELECT FROM TABLE2 statement.
• APAR IC52303: Executing a connect command in CLP like "connect to c:\temp\user1\;" which contains the string "user" or "USER" in the path, the error message Incorrect command format will be reported.
• APAR IC52376: If the source database type is DB2 and it contains data type of LONG VARCHAR, when Java Sync Client tries to do synchronize, it will report error in the synchronization process.
• APAR IC52379: If you insert "current timestamp" to a table's VARCHAR column, DB2eCLP will crash.
• APAR IC52389: A subsequent call to CLI function SQLGetDiagRec doesn't return different warning messages between a registered user's successful connection and a un-registered user's successful connection.
• APAR IC52418: When you creates a JDBC subscription whose source database is SQL Server 2000, it fails with error message DSYG028E.
• APAR IC52423: When you create a subscription that uses Microsoft SQL Server 2000 as the source database and in one of the subscribed tables there is a money data type column, it fails with error message DSYM137E.
• APAR IC52424: In Mobile Devices Administration Center, when the user uses database selection button to choose a local database, the driver combo box does not change to IBM DB2 TYPE 2 legacy CLI-based ( or IBM DB2 UDB LOCAL before 9.1) automatically.
• APAR IC52425: In Mobile Devices Administration Center, the JDBC subscription cannot be created if a previous subscription had the same mirror database and source database and failed to be created. For example, if you try to create a subscription which has a wrong filter, this subscription cannot be created successfully. Then you try to create another subscription with the same mirror and source database which has correct filters, this subscription still cannot be created.
• APAR IC52456: The BUILDTIME field in the table DSY.SYNC_SUBS_STAT is not collected correctly.
• APAR IC52458: During the synchronization, when the number of subscribed table is large, the synchronization time of DB2 Everyplace Java Sync Client will be very long.
• APAR IC52486: Under logic delete mode, after you insert a few records ($dirty=2) into a table that has some 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.