Fix (APAR): PM19268 Status: Fix Release: 7.0.0.9,7.0.0.7,7.0.0.5,7.0.0.3,7.0.0.11,7.0.0.1,7.0 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: PM19268 Byte size of APAR: 2984461 Date: 2010-08-24 Abstract: On a DELETE operation from the application to Derby via JDBC, the derby server fails with the ERROR 40XT0 on commit Description/symptom of problem: PM19268 resolves the following problem: ERROR DESCRIPTION: Description: While issuing a DELETE operation from application to Derby via JDBC, the derby server fails with the 4X0T0 error and fails to commit the transaction. . The exception seen in the Derby log is: . 2010-06-30 20:10:08.043 GMT Thread[WorkManager.wpsDefaultWorkManager : 0,5,main] (XID = 391657), (SESSIONID = 7), (DATABASE = C:/IBM/WebSphere/portalServer/derby/wpsdb), (DRDAID = null), Failed Statement is: DELETE FROM SESSION.ICMTT_0e00b2cc_6922_4e5e_b65d_8e389223d3a2 ERROR 42X05: Table/View 'SESSION.ICMTT_0E00B2CC_6922_4E5E_B65D_8E389223D3A2' does not exist. at org.apache.derby.iapi.error.StandardException.newException(Unkno wn Source) at org.apache.derby.impl.sql.compile.FromBaseTable.bindTableDescrip tor(Unknown Source) at org.apache.derby.impl.sql.compile.FromBaseTable.bindNonVTITables (Unknown Source) at org.apache.derby.impl.sql.compile.FromList.bindTables(Unknown Source) at org.apache.derby.impl.sql.compile.SelectNode.bindNonVTITables(Un known Source) at org.apache.derby.impl.sql.compile.DMLStatementNode.bindTables(Un known Source) . WebSphere log shows: Caused by: ERROR 40XT0: An internal error was identified by RawStore module. at org.apache.derby.iapi.error.StandardException.newException(Unkno wnSource) at org.apache.derby.impl.store.raw.xact.Xact.setActiveState(Unknown Source) at org.apache.derby.impl.store.raw.xact.Xact.addContainer(Unknown Source) at org.apache.derby.impl.store.access.heap.Heap.create(Unknown Source) at org.apache.derby.impl.store.access.heap.HeapConglomerateFactory. createConglomerate(Unknown Source) LOCAL FIX: NA PROBLEM SUMMARY USERS AFFECTED: All users of IBM WebSphere Application Server V7.0 PROBLEM DESCRIPTION: On a DELETE operation from the application to Derby via JDBC, the derby server fails with the ERROR 40XT0 on commit RECOMMENDATION: None While issuing a DELETE operation from the application to Derby via JDBC, the derby server fails with the error 4X0T0 and fails to commit or rollback the transaction. The use case that causes this error is : Application creates 3 temporary tables using the the command "DECLARE GLOBAL TEMPORARY TABLE..." and these temp tables are created as part of their delete where data from other tables is deleted using the entries in these tables. The creation of the temp tables and the delete is contained in the same transaction. When the commit is called on the transaction they run into the issue. If an XA two phase commit is performed while an GLOBAL TEMPORARY TABLE is active, embedded derby database server might fail with: XAER_RMERR Exception in thread "main" javax.transaction.xa.XAException: An internal error was identified by RawStore module. at org.apache.derby.jdbc.EmbedXAResource.wrapInXAException(EmbedXAR esource.java:820) at org.apache.derby.jdbc.EmbedXAResource.commit(EmbedXAResource.jav a:143) at ReproXATempTable.tempTableInXA(ReproXATempTable.java:51) at ReproXATempTable.main(ReproXATempTable.java:14) .. .. Caused by: ERROR 40XT0: An internal error was identified by RawStore module. at org.apache.derby.iapi.error.StandardException.newException(Unkno wn Source) at org.apache.derby.impl.store.raw.xact.Xact.setActiveState(Unknown Source) at org.apache.derby.impl.store.raw.xact.Xact.addContainer(Unknown Source) at org.apache.derby.impl.store.access.heap.Heap.create(Unknown Source) at org.apache.derby.impl.store.access.heap.HeapConglomerateFactory. createConglomerate(Unknown Source) PROBLEM CONCLUSION: This problem is fixed in the Embedded Derby Database server. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.13. 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: Fix applies to Editions: Release 7.0 _X_ Application Server (Express or BASE) _X_ Network Deployment (ND) Install Fix to all WebSphere installations unless special instructions are included below. Special Instructions: None NOTE: The user must: * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V7.0.0.0 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. 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 1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into the maintenance directory. 2) Shutdown WebSphere Application Server. Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) For IBM i users, use the update command to install and uninstall the interim fix. The IBM Information Center can provide additional details, if needed, on the use of this command. http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-iseries&topic=rins_update. For non-IBM i users, launch the Update Installer and click the Next button on the Welcome page. 4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button. 5) Select the "Install maintenance package" operation and click the Next button. 6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button. 7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step. The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package. To determine why some maintenance packages have been identified as not applicable, see description in log found in /logs/tmp*/updatelogs.txt 8) For all platforms except Windows. In pre-install summary panel, use the "verify permission" feature to verify the user has permissions to apply updates to files associated with the selected maintenance. Correct any file permissions before clicking next to start the install. 9) Restart WebSphere Application Server. 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 Application Server. 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 Application Server. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere Application Server. Additional Information: