Fix (APAR):  JR31352

Status:  Fix

Release:  6.2.0

Operating System:  AIX,HP-UX,Linux,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  9938

Date: 2008-12-12

Abstract:  When creating Relationship database schema objects, Relationship Service check if any of them already exist to prevent from attempting creating the duplicates. The check for stored

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

ERROR DESCRIPTION:?                                             
relationshipservice.exceptions.RelationshipServiceException:    
Fail to create runtime schemas for relationship                 

LOCAL FIX:?                                                     

PROBLEM SUMMARY:?

USERS AFFECTED:
WebSphere Process Server V6.2.0 users.

PROBLEM DESCRIPTION:
When creating Relationship database
schema objects, Relationship Service
check if any of them already exist to
prevent from attempting creating the
duplicates. The check for stored
procedure existance fails on
db2zos v9. Because of this
Relationship Service attempts to
create the stored procedure again and
it fails. This causes the relationship

to not initialize properly.

RECOMMENDATION:
None

There was a change in db2zos between v8 and v9. In DB2 V8, the
value stored in column CREATEDBY is the Auth ID of the user
who created the routine. In DB2 V9, the value stored in column
CREATEDBY is the Primary Auth ID of the user who created the
routine. The query to check for stored procedure existance
used the CREATEDBY clause. With this syntax it fails to find
the procedure when the Auth ID and the Primary Auth ID do not
match. As a result Relationship Service fails to detect that
the procedure already exists and attempts to recreate it
causing the exception.

PROBLEM CONCLUSION:?                                            
The query syntax is changed to use the SCHEMA keyword instead   
of the CREATEDBY keyword when checking for stored procedure     
existance.                                                      
                                                                
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

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: