DB2 Everyplace Version 8.1 FixPak 1 README
==========================================

Welcome to IBM DB2 Everyplace FixPak README!


This README provides the list of fixes that are included in FixPak 1. 
Where applicable, an APAR number is provided for your convenience. 

To stay informed of all the latest features, fixes, and news to 
DB2 Everyplace, be sure to visit our Web site @ www.software.ibm.com/data/db2/everyplace.


Prerequisites
-------------

Before you install the FixPak 1, consider the following: 

 - You must have DB2 Everyplace Version 8.1 installed. 
   You cannot install FixPak 1 on an earlier version of DB2 Everyplace. 
 - Be sure to shutdown all applications that access DB2 Everyplace and 
   the DB2 Everyplace Control Database. 
 - Stop the DB2 Everyplace servlet. 

Note: DB2 Everyplace supports DB2 Universal Database FixPak 3,FixPak 4,FixPak 5,
      FixPak 6,FixPak 7, and FixPak 8. We recommend that you have FixPak 5 or later 
      for Window, AIX, and Linux. 
      For Solaris, we recommend that you install FixPaK 7 or later.


Database engine fixes
----------------------

 - (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 crashes if 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 actually change the column value then this problem does not occur.

 - (APAR IC35328) Tables in the DB2 Everyplace engine become inaccessible while using the 
   DELETE statement, when:
   = preforming 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 failed to return the fetched rows. 

 - (APAR IC35043) On Palm OS, a new version of PBSPkcs11.prc library has been created which contains 
   fixes for a problem that occurs when you perform a repeated launch followed by a shutdown. 

Sync Server and Sync Client fixes
---------------------------------

 - (APAR IC35310) If a vertical-filtering parameter name is undefined or misspelled in 
  the Group definition, the Sync Server hangs during synchronization.
 
 - (APAR IC35329) If you reset a file subscription in the Mobile Device Administration Center 
   and then preformed a synchronization, the new file change on the on the server is not
   synchroniszed to the client. 
   
 - (APAR IC34823) The Mobile Device Administration Center did not start if you were using 
   DB2 Universal Database with FixPak 7.

 - (APAR IC35308) The Palm device automatically powers off when the synchronization takes longer
   than the specified transport timeout (plus 30 sec.).

 - (APAR IC35309) The XML Scripting Tool fails to drop a subscription if the source is down.

 - (APAR IC35334) A certain sequences of clicks in the Palm OS GUI will cause the GUI to crash. 

 - (APAR IC35335) File subscriptions do not work with Symbian 6 mobile devices.