eFix (APAR): PQ60552
Status:      efix

Release: WebSphere 4.0.2

Supersedes eFixes: n/a

CMVC defect:  PQ60552

Byte size of APAR:   1,081,139 bytes

Date: 04/26/2002

Title: Make remove clone and create app server occur in a single transaction.

Abstract: The two operations above have write updates in multiple DB transactions. This
can result in result in DB inconsistencies in some failure scenarios. This testfix
consolidates the DB updates into a single DB transaction.

Description/symptom of problem:
There are two operations, an ApplicationServer create outside the Admin console and
a clone delete, which have database writes occuring in two different transactions.
If a failur occurs and one of those transactions commits the other one rolls back 
the repository will have inconsistent data. This fix causes each of scenarios to 
write to the repository in a single transaction, thereby eliminating the 
possibility of repository inconsistency.

Directions to apply efix:

1) Create temporary "efix" directory to store the jar file:
             AIX: /tmp/WebSphere/efix
   Solaris/Linux: /tmp/WebSphere/efix
         Windows: c:\temp\WebSphere\efix

2) Copy jar file to the directory

3) Shutdown WebSphere

4) Run the jar file with the following command answering questions/prompts as they appear:
   java -jar <jarfile name>

5) Restart WebSphere

6) The temp directory may be removed but the jar file should be saved.  Do not remove 
   any files created and stored in the <WASHOME>/WebSphere/AppServer/efix/<efix> directories.
   These files are required if an efix is to be removed.



Directions to remove an efix:

NOTE:  EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED.  DO NOT REMOVE AN EFIX UNLESS
       ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED.  YOU MAY REAPPLY ANY REMOVED EFIX.

Example:  If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be
          removed, efix3 must be removed first, efix2 removed, and efix3 re-applied.


1) Change directory to the efix location (<WASHOME>/WebSphere/AppServer/efix/<efix#>).

2) Shutdown WebSphere

3) Run the backup jar file with the following command:
   java -jar <backup_efix#>

4) Restart WebSphere



Directions to re-apply an efix:

Follow the instructions for applying an efix.  If the backup files still exist (from the 
previous efix application), you will be prompted to overwrite.  Answer "yes" at the overwrite 
prompts.



Additional Information:
------------------------------------------------------------------

This is not a cumulative efix. It only fixes the problem described above.