Fix (APAR):  PM21071

Status:  Fix

Release:  6.1.1.2,6.1.1

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  104991

Date: 2010-10-17

Abstract:  The on demand router (ODR) fails to start when certain trace is enabled.

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

ERROR DESCRIPTION:                                              
If the binary trace facility encountered errors during the      
start up of a server, then the server would fail to start       
properly, even though it is only the tracing facility that      
has hit errors.                                                 

LOCAL FIX:                                                      

PROBLEM SUMMARY

USERS AFFECTED:
 All users of WebSphere Virtual Enterprise
Version 6.1.1.0 and Version 6.1.1.2

PROBLEM DESCRIPTION:
The on demand router (ODR) fails to
start when certain trace is enabled.

RECOMMENDATION:
None

Under certain trace conditions, the binary trace facility fails
to initialize, causing the entire ODR to not start.

PROBLEM CONCLUSION:                                             
                                                                
                                                                
This fix will be included in the next available fix pack for    
WebSphere Virtual Enterprise.                                   


Directions to apply fix:  
Install Fix to:
NOTE: Developers -  Place and X next to the proper installation method and remove this note
__ Application Server Nodes
__ Deployment Manager Nodes
_X_ Both

NOTE:
The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. Also, you should be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

DOWNLOAD THE UPDATE INSTALLER TOOL IN ORDER TO INSTALL A FIX.
The Fix Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory. It uses fixpacks and fixes as the location of the unpacked files.

Customers must be at V6.1.0.17 or newer of the Update Installer.?This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

1) Copy 6.1.1.0-WS-WXD-IFPM21071.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (6.1.1.0-WS-WXD-IFPM21071.pak file which was copied in the maintenance directory).  The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes directory.

7) Install the maintenance package.

8) Restart WebSphere

Directions to remove fix:  
NOTE:  The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.

NOTE:  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
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) Select the file name of the maintenance package to uninstall 6.1.1.0-WS-WXD-IFPM21071.pak

6) UnInstall maintenance package.

7) Restart WebSphere

Directions to re-apply fix:  
1) Shutdown WebSphere

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere

Additional Information: