Fix (APAR): PK29636 Status: Fix Release: 6.0.2.13 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows Supersedes Fixes: PK24014 CMVC Defect: xxxxxx Byte size of APAR: 6923710 Date: 2006-10-02 Abstract: PK24014 is superseeded by this APAR. This apar provides 5.1.60.43 version of the cloudscape driver. Description/symptom of problem: PK29636 resolves the following problem: ERROR DESCRIPTION: During install of PK24014, all stored statements within a Cloudscape SIB datastore database which is being used by a cluster, are erased. This causes the messaging engine to fail to start. The ME reports the following error messages: [26/07/06 10:55:15:844 BST] 0000002d SibMessage E [PhilsBus:xenaNode01.server3-PhilsBus] CWSIS0002E: The messaging engine encountered an exception while starting. Exception: com.ibm.ws.sib.msgstore.PersistenceException: CWSIS1501E: The data source has produced an unexpected exception: com.ibm.db2.jcc.a.SqlException: STATEMENT 'SYSIBM.METADATA' does not exist. LOCAL FIX: This APAR provides a later cloudscape driver which resloves the install problem PROBLEM SUMMARY USERS AFFECTED: Websphere Application Server version 6.0.2 users who use the cloudescape driver or products that make use of cloudscape driver PROBLEM DESCRIPTION: PK24014 is superseeded by this APAR. This apar provides 5.1.60.43 version of the cloudscape driver. RECOMMENDATION: None This APAR was used to superseed PK24014 which tried to provide the 5.1.60.41 version of the cloudscape driver to Application Server version 6.0.2 users. This 5.1.60.41 version was needed to avoid a NullPointerException. However problems were discovered with the 5.1.60.41 version driver offered by PK24014. So this apar offers the 5.1.60.43 which solves the original problem of the NullPointerException and does not have any of the problems related to the 5.1.60.41. PROBLEM CONCLUSION: This APAR updates the cloudescape driver to version 5.1.60.43 and superseeds the version 5.1.60.41 of the driver offered by PK24014. The fix for this APAR is currently targeted for inclusion in fixpack 6.0.2.15. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: