Apache Derby 10.1 updates are not automatically applied

Technote (troubleshooting)


Problem(Abstract)

In IBM WebSphere Application Server Version 6.1.0.17 through 6.1.0.27, updates to Apache Derby 10.1 are not shipped in Fix Packs to WebSphere Application Server V6.1. Apache Derby 10.1 is the Derby version that is bundled with Version 6.1 of Application Server.

If other IBM products replace the Derby version that is bundled with the Application Server with a newer version of the Derby image and you apply any V6.1 Fix Pack the Application Server starting with Fix Pack 17 and going through Fix Pack 27, the Fix Pack replaces the Derby image with a 10.1 version. This replacement might result in compatibility issues.

Diagnosing the problem

Beginning with 6.1.0.17 and continuing through 6.1.0.27, updates to Apache Derby 10.1 are not automatically applied to WebSphere Application Server V6.1. Instead, Derby 10.1 updates are located in a separate directory.

Note: Do not apply the Derby update for these Fix Pack versions unless there is a specific reason to apply it.

You might be directed to apply the Derby update by support documentation for the Application Server or other IBM product documentation. Do not apply the Derby update unless you are certain that you will not revert the current Derby version to a previous version.


Resolving the problem

To avoid this issue, upgrade the Application Server to Fix Pack 29 or later. Otherwise, you can follow the steps below to update Derby outside of the Application Server process.


The Java™ archive (JAR) file for Derby can be found in the WAS_HOME/derby/lib directory. The Derby updates are now installed in the WAS_HOME/derby/fixes/10.1/derby_build_number directory for WebSphere Application Server or in the was_smpe_root/derby/fixes/10.1/derby_build_number directory for WebSphere Application Server for z/OS.

For example:

  • WebSphere Application Server on the AIX, HP-UX, i5/OS, Linux, Solaris, and Microsoft Windows operating systems: WAS_HOME/derby/fixes/10.1/10.1.3.2.639536
  • WebSphere Application Server for z/OS:
    was_smpe_root /derby/fixes/10.1/10.1.3.2.639536

Updates to the Application Server will install the JAR files for Apache Derby in this directory path. In addition, a script is added that you can use to apply the fixes to the derby/lib directory.

The script name is:
  • For WebSphere Application Server on the AIX, HP-UX, Linux, and Solaris operating systems: updateDerby.sh
  • For WebSphere Application Server on the i5/OS operating system: updateDerby
  • For WebSphere Application Server on the Windows operating systems: updateDerby.bat
  • For WebSphere Application Server for z/OS: updateDerby.sh

To run the script, complete the following steps:
  1. Change the working directory to the directory that contains the Derby fix.

    For example, for WebSphere Application Server on the AIX, HP-UX, Linux, Solaris operating systems:
    cd /opt/IBM/WebSphere/AppServer/derby/fixes/10.1/10.1.3.2.639536

    For WebSphere Application Server for z/OS, the fix resides in the read-only SMP/E file system. For example:
    cd /usr/lpp/zWebSphere/V6R1/derby/fixes/10.1/10.1.3.2.639536

    Note: Be aware that the command to change the directory should be on the same command line. Do not insert carriage returns.

  2. Run the script.

    On non-z/OS operating systems, the script copies the necessary JAR files from the current directory to the WAS_HOME/derby/lib directory.

    With WebSphere Application Server for z/OS, the script resides in the read-only SMP/E file system and requires a parameter, which is the location in the writeable configuration file system that is referenced by the WAS_HOME variable.

    For example:
    updateDerby /WebSphere/V6R1/AppServer

    WAS_HOME /derby/lib in the configuration file system is actually a symbolic link to was_smpe_root /derby/lib. The script will convert WAS_HOME /derby/lib to a directory that contains symbolic links to the JAR files and to other contents of the was_smpe_root /derby/lib directory.

    Note: You can use the script with an -undo option, which converts WAS_HOME/derby/lib back to a symbolic link and points to the was_smpe_root/derby/lib directory. Use the -undo option before the WebSphere Application Server V6.1 Fix Pack is removed from the SMP/E.

    For example:
    updateDerby -undo /WebSphere/V6R1/AppServer

This issue is addressed with APAR PK66013.

Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server for z/OS z/OS 6.1

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Application Server
DB Connections/Connection Pooling

Software version:

6.1.0.17

Operating system(s):

AIX, HP-UX, IBM i, Linux, Solaris, Windows

Software edition:

Base, Express, Network Deployment

Reference #:

1305388

Modified date:

2010-02-03

Translate my page

Machine Translation

Content navigation