Fix (APAR):  JR32743

Status:  Fix

Release:  6.2.0.1,6.2.0

Operating System:  AIX,HP-UX,i5/OS,Linux,Solaris,Windows

Supersedes Fixes:  JR31968

CMVC Defect:  xxxxxx

Byte size of APAR:  75315

Date: 2009-05-20

Abstract:  Event Sequencing users encounter DuplicateKeyException on DB2 for iSeries.

Description/symptom of problem:  
JR32743 resolves the following problem:

ERROR DESCRIPTION:                                              
PersitentLockMgr get DuplicateKey Exception on i5/OS with DB2/I 
JDBC Transaction set to "TRANSACTION_REPEATABLE_READ" (Default) 
abd DB2/I "RS".                                                 
With this isolation level "RS" on DB2/I we get "dirty read"     
This is related to the "phantom row" phenomenon.                

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server v6.2.0.x users.

PROBLEM DESCRIPTION:
Event Sequencing users encounter
DuplicateKeyException on DB2 for
iSeries.

RECOMMENDATION:
None

WebSphere Process Server installations using DB2 on iSeries
and have Event Sequenced messages can sporadically encounter
a DuplicateKeyException that causes the sequencing order to be
lost.
This occurs because the transaction isolation semantics on DB2
for iSeries are slightly different resulting in a specific
timing sequence causing a dirty database read on a transaction
that is pending commit completion.

PROBLEM CONCLUSION:                                             
Applying this interim fix will resolve the issue.               


Directions to apply fix:  
Download and follow Update Installer installation instructions.  The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

Installation
1. Copy the interim fix .pak file to the /maintenance directory in the UpdateInstaller directory.
2. Shut down WebSphere Process Server. Perform a controlled and complete shutdown of the server to ensure that all transactions have completed before installing the interim fix.
3. Run the Update Installer and follow the prompts.
4. Run the following command, depending on your installation:
- For stand-alone servers, run this command from each profile /bin directory: 
wsadmin -conntype none -f $WPS_root/util/EventSequencing/persistentLkMgrAppUpgrade.jacl
- For clusters, run this command from each deployment manager (DMGR) profile /bin directory: 
wsadmin -conntype none -f $WPS_root/util/EventSequencing/persistentLkMgrAppUpgrade.jacl
5. Restart WebSphere Process Server.
Uninstallation
1. Shut down WebSphere Process Server. Perform a controlled and complete shutdown of the server to ensure that all transactions have completed before installing the interim fix.
2. Run the Update Installer and follow the prompts to uninstall the interim fix.
3. Run the following command, depending on your installation:
- For stand-alone servers, run this command from each profile /bin directory: 
wsadmin -conntype none -f $WPS_root/util/EventSequencing/persistentLkMgrAppUpgrade.jacl
- For clusters, run this command from each deployment manager (DMGR) profile /bin directory: 
wsadmin -conntype none -f $WPS_root/util/EventSequencing/persistentLkMgrAppUpgrade.jacl
4. Restart WebSphere Process Server.

Directions to remove fix:  
NOTE:  FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed

1) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix.

3) Restart WebSphere Process Server.

Directions to re-apply fix:  
1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix.

2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

3) Restart WebSphere Process Server.

Additional Information: