Fix (APAR):  JR28260

Status:  Fix

Release:  6.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  10238

Date: 2008-02-21

Abstract:  During v2v migration on z/OS systems, the commonDBUpgrade script shows a failure to find profileRegistry.xml. Even with this error, the migration continues and finishes.

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

ERROR DESCRIPTION:                                              
WBIProfileUpgrade.ant can't find profileRegistry.xml during a   
6.0.2 to 6.1 migration on z/OS.                                 

LOCAL FIX:                                                      
NONE                                                            

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Process Server v6.1 Users.

PROBLEM DESCRIPTION:
During v2v migration on z/OS systems,
the commonDBUpgrade script shows a
failure to find profileRegistry.xml.
Even with this error, the migration
continues and finishes.

RECOMMENDATION:
None

This is because, on z/OS, the profileRegistry.xml is found
directly in the WAS_HOME directory, whereas on distributed
systems, the profileRegistry.xml is found in the properties
directory and is copied over correctly from the previous
version of the product. The commonDBUpgrade script looks for
the profileRegistry.xml in the properties directory, and when
it can't find it there, the script ends with an error.

PROBLEM CONCLUSION:                                             
The fix for this problem was to explicitly copy the             
profileRegistry from the WAS_HOME directory to the expected     
properties folder in the backup directory when the platform is  
z/OS. Now the commonDBUpgrade script finds the                  
profileRegistry.xml in the correct place and it finishes        
successfully.                                                   


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: