Fix (APAR):                PK50967



Status:                    Fix



Product:                   WAS



Release:                   6.1.0.5,6.1.0.13



Operating System:          All operating systems



Supersedes Fixes:          



Pre-requisite Fixes:       



Exclusive-requisite Fixes: 



CMVC Defect:               PK50967



Byte size of APAR:         107923



Date:                      2007-12-14



Abstract:                  During log rollover, if renaming the file fails, WebSphere Application Server will attempt to copy the file.



Description/symptom of problem:

During log rollover, if renaming the file fails, WAS will attempt to copy the file.



Directions to apply fix:



  Fix applies to Editions:

    Release:

    6.0   6.1

    ___   X__ Application Server (Express or Base)

    ___   X__ Network Deployment  (ND)

    ___   ___ WebSphere Business Integration Server Foundation (WBISF)

    ___   ___ Edge Components

    ___   ___ Developer

    ___   ___ Extended Deployment (XD)



  Install Fix To:

    Method:

    X_ Application Server Nodes

    __ Deployment Manager Nodes

    __ Both



  NOTE:

    The user must:

       * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environment.

       * Be Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

       * Be at V6.1.0.0 or later of the Update Installer. This can be checked by reviewing the level

         of the Update Installer in file <was_root>/updateInstaller/version.txt



  The update Installer can be downloaded from the following link:

       http://www.ibm.com/support/docview.wss?rs=180&uid=swg24012718



  For detailed instructions on how to extract the Update Installer see the following Technote:

       http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg27006162



  1) Copy 6.1.0-WS-WAS-IFPK50967.pak file directly to the maintenance directory.



  2) Shutdown Application Server. 

     Manually execute setupCmdLine.bat in Windows or ../setupCmdLine.sh in UNIX from the 

     IBM WebSphere Application Server instance that maintenance is being applied to.

     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) Launch the Update Installer.



  4) Enter the installation location of the Application Server 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.0-WS-WAS-IFPK50967.pak file which was copied into 

     the maintenance directory).



  7) Install the maintenance package.



  8) Restart Application Server.





Directions to remove fix:



  NOTE:

    * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environment.

    * 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 Application Server. 

     Manually execute setupCmdLine.bat in Windows or ../setupCmdLine.sh in UNIX from the WebSphere

     instance that uninstall is being run against.

     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) Launch the Update Installer.



  3) Enter the installation location of the Application Server product you want to remove the fix.



  4) Select the "Uninstall maintenance package" operation.



  5) Enter the file name of the maintenance package to uninstall (6.1.0-WS-WAS-IFPK50967.pak).



  6) Uninstall the maintenance package.



  7) Restart Application Server.





Directions to re-apply fix:



  1) Shutdown Application 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 instructions to apply the fix.



  3) Restart Application Server.





Additional Information: