Fix (APAR):  JR31430

Status:  Fix

Release:  6.2,6.1.2,6.1.0.2,6.0.2.5,6.0.2.4

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  618642

Date: 2009-06-22

Abstract:  Scheduler defined at both the cluster scope and at the server scope in the golden topology. Multiple AppSchedulers cause conflict.

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

ERROR DESCRIPTION:                                              
[8/14/08 13:10:18:713 CDT]                                      
0000000e LeaseAlarm    E   SCHD0125E:                           
Unexpected exception while processing the acquireLease          
operation: com                                                  
ibm.ws.leasemanager.LeaseException: SCHD0300E: Error during     
Database                                                        
operation, localized message is ORA-00001: unique constraint    
(WPRC                                                           
SDB.SYS_C003194) violated, Vendor Error Code is 1, ANSI-92      
SQLState i                                                      
23000, cause: ORA-00001: unique constraint (WPRCSDB.SYS_C003194)
violated                                                        

LOCAL FIX:                                                      
Create only one AppScheduler in cluster scope rather than       
multiple AppSchedulers                                          

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server v6.0.2.x
WebSphere Process Server v6.1.0.x
WebSphere Process Server v6.1.2.x
WebSphere Process Server v6.2.0.x
users using the AppScheduler

PROBLEM DESCRIPTION:
Scheduler defined at both the cluster
scope and at the server scope in the
golden topology. Multiple
AppSchedulers cause conflict.

RECOMMENDATION:
None

Configuration of Scheduler of type AppScheduler at both cell
and cluster level is incorrect. Scheduler and the Scheduler's
workManager need to be created at the cell level only.

PROBLEM CONCLUSION:                                             
Applying this interim fix before creating any profiles will     
resolve the issue. The fix for this APAR is targeted for        
inclusion in a future v6.0.2.x, v6.1.0.x, v6.1.2.x, and         
v6.2.0.x fixpack.                                               


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

1) Copy the pak file to the directory maintenance in the UpdateInstaller directory

2) 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.

3) Run the UpdateInstaller and follow the prompts.

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: