IBM DB2 Everyplace Enterprise Edition Version 9.1.2
Release Notes
IBM DB2 Everyplace Enterprise Edition Version 9.1.2 Release
Notes
Welcome to the IBM(R) DB2(R) Everyplace(R) Version 9.1.2 Release Notes.
This document contains the enhancements that are in DB2 Everyplace Version 9 Release 1
Fix Pack 2 (hereafter referred to as DB2 Everyplace V9.1.2). You can also
find the link to information about installing, configuring and uninstalling DB2 Everyplace V9.1.2. A list of known
restrictions and considerations is also documented.
DB2 Everyplace V9.1.2 new features
This section introduces the new features that are available in DB2 Everyplace V9.1.2.
New supported products
- Support for new source databases
- DB2 Version
9.1 for z/OS(R), DB2 Version
9.5 for Linux(R), UNIX(R) and Windows(R),
and Informix(R) Dynamic Server Version 11.1 have been tested
with DB2 Everyplace V9.1.2 as
source databases.
- Support for Windows Mobile 6.0 support
- DB2 Everyplace V9.1.2 supports Windows Mobile
6.0 on mobile devices.
- Support for Apache Derby 10.3 database
- DB2 Everyplace Enterprise
Edition V9.1.2 bundles Apache Derby 10.3 and supports it as a client database.
You can use Derby database instead of the DB2 Everyplace database to synchronize
data. DB2 Everyplace 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 in the DB2 Everyplace documentation.
Synchronization
- Support for synchronization of XML data types
- You can synchronize XML data types between your devices and DB2 Database for Linux, UNIX,
and Windows Version
9.1 or later. Palm OS devices and Symbian devices are not supported for this
feature.
- Mirror database performance tuning utility
- You can improve the synchronization performance with the mirror database
tuning utility. The utility can be set to run once or can be scheduled to
run at a regular interval.
- New parameter for XML scripting tool
- When you apply the XML in the XML script file to the control database
from the command line, you can use the new parameter -d scriptFile -filterAdjustment
to adjust filters.
- Changing trace level without restarting DB2 Everyplace Sync Server
- You can temporarily change the trace level and collect the diagnostic
information without restarting the DB2 Everyplace Sync Server.
- Changes in IBM Type
2 Legacy/CLI JDBC driver
- DB2 Everyplace V9.1.2 does
not support the IBM Type
2 Legacy/CLI JDBC driver any more. During the installation of V9.1.2, the
subscriptions that use the Type 2 Legacy/CLI JDBC driver will be updated automatically
to use the Type 2 Universal JDBC driver. When you uninstall V9.1.2, the JDBC
driver for these subscriptions will be changed automatically back to Type
2 Legacy/CLI JDBC driver.
Database
- Comprehensive data integrity check tool
- Besides checking the general health of your DB2 Everyplace database
by using the DBCHECK command, you can perform checks with the comprehensive
database integrity check tool. The comprehensive check, when used before synchronization,
also helps you to prevent client synchronization errors.
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 either new or have been updated in this release, and are available
in English only.
- DSYS034E: The source data row with primary key value in
table table name exceeds data size limit. Either one BLOB
column, one XML column in replication is bigger than 4 MB, or the row size
is bigger than 4 MB because of the BLOB data or XML data.
-
Explanation: See message text.
User Response: Decrease
the data contained in the BLOB column, XML column, or decrease the data in
other columns.
- DSYS035E: The device cannot synchronize because the subscription contains
XML data. XML data type cannot be synchronized on Palm or Symbian devices.
-
Explanation: See message text.
User Response: Do
not synchronize XML data between Palm or Symbian devices and source databases.
- DSYT041I: Started performance tuning on mirror database mirror
database name.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT042I: Started running REORGCHK command on user
tables in mirror database mirror database name.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT043I: The result of REORGCHK on mirror database mirror
database name is output_of_reorgchk_command.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT044I: Finished REORGCHK on mirror database mirror database
name.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT045I: Reorganizing table table name.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT046I: Finished reorganization of table table name.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT047I: Reorganizing the indexes for table table name.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT048I: Finished reorganization of the indexes for table table
name.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT049I: Started RUNSTATS on table table
name with parameters WITH DISTRIBUTION and DETAILED
INDEXES ALL.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT050I: Finished RUNSTATS on table table
name with parameters WITH DISTRIBUTION and DETAILED
INDEXES ALL.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT051I: Finished performance tuning on mirror database mirror
database name.
-
Explanation: This is a progress message.
User Response: No
action required.
- DSYT052E: Mirror database mirror database name does
not exist.
-
Explanation: See message text.
User Response: Verify
that the specified mirror database exists and try again.
- DSYT053E: Performance tuning on mirror database mirror database
name failed while exception exception description happened.
-
Explanation: See message text.
User Response: Correct
the problem according to the message text and try again.
Fixes contained in this fix pack
The following APARs are fixed in DB2 Everyplace V9.1.2.
APARs
- APAR IC52460: DB2 Everyplace Java(TM) Sync Client cannot send the client
updates in phase I to server if the encoded message size is larger than 5MB.
The failure information is recorded in the trace-isyn file, for example "DSYC000I:
makePostRequest.: p1 Sending message exceeds the max message size limit."
- APAR IC52858: During data synchronization, if the target directory
is in a different Windows drive from the Windows drive where DB2 Everyplace is
installed, for example DB2 Sync is located in D:\DB2e drive
but the target directory is set to C:\target, DB2 Sync will
that synchronization fails with error code -3.
- APAR IC52938: DB2 Everyplace Java Sync Client cannot run on the JVM 1.4
platform because the client uses some JDK1.5 specific APIs. If it is running
on the JVM 1.4 platform , the synchronization will stop and the following
error information is reported by the JVM class loader:
method setConnectTimeout can not be found in the library
method setReadTimeout can not be found in the library
The failure
information is recorded in the trace-isyn file as follows: DSYC000I:
DB2jISyncProvider.openUrlConnection: setConnectTimeout| setReadTimeout doesn't
exist in current JVM.
- APAR IC53100: In DB2 Everyplace Version 9.1, there are a few data type
mappings for Cloudscape(TM) clients
are missing from DB2 Everyplace V9.1 and they are added back after DB2 Everyplace in
9.1.1. for Derby client are missing and they are added back after DB2 Everyplace 9.1.1
- APAR IC54132: If you change "Encrypt on device" from "56-bit data
encryption standard" or "192-bit data encryption standard" (starting from DB2 Everyplace V9.1.1)
to "None" in Mobile Devices Administration Center, in the next synchronization,
Sync Client will report synchronization failure with error "DSYC698E".
- APAR IC54136: DB2 Everyplace Java Sync Client cannot be refreshed after
resetting the file subscription.
- APAR IC54137: While creating table subscriptions with DB2 Type 2 Universal
Driver and DB2 Type
4 Driver, Sync Server fails to connect to AS/400(R) source database with the error
message "DSYM132E: The AS/400 source database 'jdbc:db2:' is not supported
for JDBC table subscriptions."
- APAR IC54134: DB2 Everyplace Java Sync Client cannot accept DDL statement
longer than 8K characters. If there are more than 8K characters in the DDL
statement, DB2 Everyplace Java Sync
Client only processes the first 8K characters and the sync will fail. The
failure information is recorded in the trace-isyn file as follows:
DSYC000I: DB2jISyncProvider.dropAndCreateBaseTables:
DSYC000I: DB2jISyncProvider.: Error: SQL Exception: Syntax error:
DSYC000I: DB2jISyncProvider.syncSubscriptions: ERROR 42X01:
- APAR IC54152: When a BLOB or a record in a subscribed table is
updated from less than 4M to more than 4M, the Sync Client cannot receive
the new data and the obsolete data at client side will not be deleted.
- APAR IC54244: If a data filter of subscription A refers to a lookup
table T that is subscribed by subscription B but not by subscription A, then
XML scripting tool will fail to create subscription A. The tool will report
that table T is an undefined name.
- APAR IC54248: In some cases, when the source database is DB2 for z/OS, subscriptions
with column type VARCHAR(1024) cannot be created. Mobile Devices Administration
Center will indicate that it fails to create the subscription after failing
to create a particular table.
- APAR IC54260: If a user tries to synchronize files larger than
64 KB to Palm V5.4 devices or the SD card through File Subscription, the synchronization
will fail with 401 error.
Installation, configuration and uninstallation
This section points to the installation, configuration and uninstallation
instructions.
To install, configure and uninstall DB2 Everyplace V9.1.2,
see DB2 Everyplace V9.1 Fix Packs Information Center,
or download the Installation and User's Guide from the DB2 Everyplace library.
If you installed only DB2 Everyplace Sync Client for
V9.1, install V9.1.2 manually by using Clients.zip instead
of using the Update Installation wizard.
To uninstall DB2 Everyplace V9.1
after DB2 Everyplace V9.1.2 is
applied, uninstall V9.1.2 first. When you uninstall V9.1, the new directories
and files that were installed by V9.1.2 are not removed, and you must remove
those directories and files manually.
Known considerations and restrictions
This section contains known defects in this release of . It also
provides information about fixes or workarounds that exist for these limitations
and issues.
For installation and configuration
After you complete
the basic configuration of DB2 Everyplace with WebSphere(R) Application Server Version
6 and start the DB2 Everyplace application
server, the SystemOut.log file will contain the exception
message of no permission to write the WebSphere Application Server activity.log file.
This exception occurs because the owner of the DB2 Everyplace application server does
not have the necessary permission to write to the activity.log file
in that directory. This issue will not affect system usage and will be fixed
in the next release.
For the DB2 Everyplace Sync Client
- The IUpgrade application for Symbian mobile devices is available only
in German, English, Spanish, French, and Italian.
For the DB2 Everyplace Sync Server
- Replication of subscriptions that have empty BLOB data
fails for the source database DB2 Database for Linux, UNIX and Windows Version 9.1. The error message
is
com.ibm.db2.jcc.b.SqlException: [ibm][db2][jcc][10152][10176] Invalid position 1 or length 0.
at com.ibm.db2.jcc.b.rc.getBytes(rc.java:116)
Workaround: Do
not insert empty BLOBs to source tables or device tables. When a future fix
pack of DB2 Database
for Linux, UNIX and Windows Version
9.1 solves this issues, apply the fix pack. APAR IZ07562 tracks this problem.
- Replication fails between mirror databases and DB2 for i5/OS(R) V5R3 or
V5R4. The error message is com.ibm.db2.jcc.b.SqlException: FOR UPDATE
clause not valid.
Workaround: To solve this problem on DB2 for i5/OS V5R3,
apply the fix SI27590. To solve this problem on DB2 for i5/OS V5R4, apply the fix
SI27950.
-
Cannot create DataPropagator(TM) subscriptions with the XML
scripting tool.
Workaround:
- Configure DataPropagator by
following the instructions in http://publib.boulder.ibm.com/infocenter/db2e/v9r1f1/index.jsp?topic=/com.ibm.db2e.doc/sag/dbesst0509.htm.
- Create DataPropagator subscriptions
with the XML scripting tool. Set the following items to FALSE:
- "CreateDPropRControlTables" for "AddReplMaster" and "AddReplMirro"
- "SetupDPropRSourceAndMirror" for "AddDproprSubscription
For example,
<AddReplMaster CreateDPropRControlTables="FALSE">
<System>SAD_LPT</System>
<Instance>DB2</Instance>
<Database>VNURSE</Database>
<UserId>db2admin</UserId>
<Password>db2admin</Password>
<DatabaseAlias>VNURSE</DatabaseAlias>
</AddReplMaster>
- The maximum length of BLOB and XML columns is 4 MB. When you update a
BLOB or XML column in a source table from less than 4 MB to more than 4 MB,
the updated data will not be replicated to the mirror database, and the error
message DSYS034E will be reported. The old data will be sent to the device.
Workaround: To
avoid this problem, limit the BLOB and XML size if possible when creating
the source table.
- 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 Users... or ....
Workaround: Refresh
the item again.
For the database
-
Unique user-defined indexes are available in DB2 Everyplace V9.1. Currently, the output
generated by the LIST INDEX command in DB2eCLP does not allow you to distinguish
between unique and non-unique indexes. It is possible only to identify user-generated
indexes from the system-generated indexes for primary key columns.
Workaround: DB2 Everyplace V9.1
fix packs contain the SQLStatistics() CLI API, which applications can use
to determine whether a user-defined index is unique or not. In DB2eCLP, you
can query the contents of the DB2eSYSINDEXES table directly. The NONUNIQUE
column contains the value 0 for unique indexes, and the value 1 for non-unique
indexes.
-
The output of the DB2LOOK command in DB2eCLP does not generate appropriate
DDL for unique user-defined indexes. All CREATE INDEX statements generated
by DB2LOOK will create non-unique indexes.
Workaround: Identify
unique indexes by querying the DB2eSYSINDEXES table. The CREATE INDEX statements
generated by DB2LOOK need to be modified manually for these indexes.
Trademarks
The following terms are trademarks of the International Business Machines
Corporation in the United States, or other countries, or both.
AS/400
Cloudscape
DataPropagator
DB2
Everyplace
i5/OS
IBM
Informix
WebSphere
z/OS
Java and
all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both.
UNIX is
a registered trademark of The Open Group in the United States and other countries.
Linux is
a registered trademark of Linus Torvalds in the United States, other countries,
or both.
Microsoft(R), Windows,
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.