DB2 Everyplace Release Notes for Version 8.1.4

Welcome to the DB2 Everyplace Version 8.1.4 release notes. The new DB2 Everyplace Information Center for Version 8.1.4 is available and is located in the %DSYINSTDIR%\doc\lang\infocenter directory.

These release notes contain information about new features, enhancements, and updated procedures in the Version 8.1.4 release of the DB2 Everyplace.

• New fixes and features for the DB2 Everyplace database
• Known considerations and restrictions
• Trademarks

New fixes and features for the DB2 Everyplace database

The following section begins with a list of features which is followed by recent fixes for the DB2 Everyplace database.

New features for the database engine

• ADO.Net support for PocketPC and Windows platforms
• DB2 Everyplace has two new system defined scalar functions which enable you to perform an SQL query regardless of the case of the data that you are querying. These new functions are LCASE() and UCASE().
• You can now have multiple connections to different databases within the same process.
• Auto-increment (Identity Column) support
• Piecemeal retrieval of large data through CLI
• Support for Symbian OS Version 7
• Remote Stored Procedure support on Symbian OS Versions 6 and 7, and its JDBC support
• Support for additional processor types on Neutrino and Linux platforms
• More JDBC support, as well as JSR 169 compatibility
• Additional CLI support including: SQLColumns, SQLGetConnectAttr, SQLGetInfo, SQLGetStmtAttr, SQLNumParams, SQLSetConnectAttr, SQLSetStmtAttr, and SQLTables.
• Support for local data encryption on all platforms, including Neutrino, Linux, Symbian OS 6 and OS 7.

Fixes for the database engine

Problems fixed in DB2 Everyplace Version 8.1, FixPak 1, FixPak 2, and Version 8.1.4, with an APAR number for your reference if applicable:

• (APAR IC34759) Data encryption problems:
  • If an application accesses more than 8 tables (one of which is an encrypted table) during a single connection session, DB2 Everyplace fails.
  • Select queries using scrollable cursor on encrypted tables fail.
  • GROUPBY queries (with grouping columns) on encrypted tables fail.
  • Update queries fail on columns of encrypted tables with indexes.
• (APAR IC34782) The DB2 Everyplace database engine abnormally terminates when you use the LIKE predicate with a parameter marker when there is an index on the column (for example, C1 LIKE ?). The index structure may be corrupted due to an update statement. The failure occurs when there is more than 1 index on table and a SET value does not change the original value of the row. If you change the column value, then this problem does not occur.
• (APAR IC35328) Tables in the DB2 Everyplace engine became inaccessible while using the DELETE statement, when the following actions occur:
  • performing a physical delete
  • reading logically deleted records
  • no WHERE clause is used with the DELETE statement
• (APAR IC35106) Re-executing a prepared SELECT statement using a scrollable cursor fails to return any rows.
• (APAR IC35043) On Palm OS, if you have PVCPKCS11.prc library installed and you repeatedly press the On/Off button the device will eventually display a system alert and requires a reset.
• (APAR IC35585) Index corruption can occur on Palm OS with error message SQLSTATE=58004 when performing update and delete operations when the index is created on columns with column numbers in one of the following sets: 17-32, 48-64, 80-96, 112-128, 144-160, 176-192, 208-226, 240-256.
• (ARAR IC35710) When you create a DB2 Everyplace Visual Basic application using the db2ecli.bas file for the Pocket PC platform, the application hangs when it is running on the Pocket PC 2002 emulator.
• (APAR IC35966) Remote stored procedure call problem on Palm. A fatal error occurs when SQLBindParameter containing SQL_PARAM_OUTPUT is used, and when acquiring the ResultSet.
• (APAR IC36026) Executing a prepared statement of a SELECT query with aggregate function without a GROUPBY clause returns an incorrect answer.
• (APAR IC36027) A searched DELETE (with a WHERE clause) fails to remove all of the qualified rows when an index on a TIMESTAMP column is used in the searching of qualified rows.
• (APAR IC36083) The CREATE TABLE and CREATE INDEX statements cause a failure, if you create an index or primary key on columns with a column number which is greater or equal to 128.
• (APAR IC36069) If an index is created on a column position that exceeds 256, data corruption may occur or SQLSTATE 58004 will be returned. This fix also prevents creating a table with more than 256 columns.
• (APAR IC36070) The REORG statement executed against a table with variable-sized records (for example, VARCHAR or BLOB) can lead to unpredictable data file corruption or an application failure. This will most likely occur when record sizes are increased by the execution of the UPDATE statement.
• (APAR IC36256) DB2 Everyplace sample applications cannot be built successfully with Microsoft eMbedded Visual C++ 3.0.
• (APAR IC36270) DB2 Everyplace does not optimize some ORDER BY queries because it fails to choose available indexes.
• (APAR IC37280) The DB2 Everyplace database engine terminates abnormally when an application tries to connect to a database that contains an empty DB2eSYSUSERS table. The same behavior can be observed when an application tries to establish a database connection and provides a wrong password immediately after the first user ID is created.
• (APAR IC36430) DB2 Everyplace may terminate abnormally during the execution of a GROUP BY query when the number of SELECT items exceeds the number of GROUP BY items.
• (APAR IC36695) Connection attempt to an encrypted database causes the DB2 Everyplace database engine to terminate abnormally.
• (APAR IC36570) The DB2 Everyplace database engine returns SQLState 57011 or 58004 when trying to access a database that is stored on an external media (for example, SD Card, CompactFlash Card, and IBM Microdrive) on a PalmOS device.
• (APAR IC36688) DB2 Everyplace database engine returns SQLState 58004 when joining two tables with a join condition that involves VARCHAR colums containing empty strings (when an index is being used for fetching data).
• (APAR IC36702) DB2 Everyplace does not match the predicate "LIKE '%'" against an empty string.
• (APAR IC37281) DB2 Everyplace SampleCLP may return an error or invalid data when importing a VARCHAR/CHAR column that ends in a quotation mark.
• (APAR IC37045) DB2 Everyplace does not return SQL State 23505 when the application inserts two decimal numbers in a primary key column whose values are slightly different. DB2 Everyplace erroneously accepts them as the same value.
• (APAR IC37046) DB2 Everyplace returns a syntax error for the string concat '¶llel.' operator.
• (APAR IC37048) DB2 Everyplace doesn't accept Traditional Chinese characters on Acer S60 device with Palm Chinese OS.
• (APAR IC37329) When an UPDATE SQL statement that uses the primary key index, followed by an DELETE SQL statement that uses the dirty bit index are executed, subsequent queries to the DB2 Everyplace database engine will return incorrect result.

Known considerations and restrictions

This section contains a list of known considerations and restrictions that apply to this release of DB2 Everyplace:

• Users of the DB2 Everyplace client database may experience performance degradation in autocommit mode for UPDATE, INSERT, or DELETE statements. A workaround for this problem is to explicitly use manual transaction and group multiple changes in a single commit operation.
• For Ado.NET on the database engine:
  • Result set retrieval using a remote stored procedure call has a limitation on the size of the result set. This restriction will be removed in a future release.
  • For methods or properties that are not supported, a "System.NotSupportedException" will be thrown.
• When the Sync Client is synchronizing to multiple target databases, local database encryption is not supported when more then one database contains encrypted tables.
• The Cloudscape client does not support all the features the DB2 Everyplace client supports. For example, multiple server, ordering of subscription sets/subscriptions/tables, and local data encryption are not supported.
• The Join Filtering feature does not support multiple table references. If a user WHERE clause contains multiple table references, the Join Filtering feature will be disabled for that WHERE clause and the warning DSYD029W will be logged. The WHERE clause continues to work without the Join Filtering feature.
• Referential Integrity is not supported for DataPropagator Table Subscriptions.
• For DataPropagator Table Subscriptions, replication must always be run on the mirror database server. This means that if replication needs to be performed during administrative actions, the the Mobile Devices Administration Center must be run on the mirror database server.
• Database object names which are required to be enclosed in double quotes are not supported.
• In general, the maximum size of a row in a table is limited by the data source. Adding the table to a JDBC subscription further restricts the maximum row size. The additional restriction on the maximum row size is approximately 125 bytes.
• In general, the maximum size of a row in a table is limited by the data source. Adding the table to a JDBC subscription further restricts the maximum row size. The additional restriction on the maximum row size is approximately 2KB.

Trademarks

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

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.