PI92469: CONFIGURATIONS OF NEW TARGET PROFILE TEMPLATE REMAIN UNTOUCHED DURING MIGRATION ALTHOUGH THEY DO NOT EXIST IN OLD PROFILE.

9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• Migration thinks that any configuration data provided by the new
  target profile template is new and remains untouched if not
  found in the old profile.
  When the untouched configurations reside in lower level than
  the configurations on old profile, then the untouched
  configurations will be taken in the migrated profile and may
  cause some issue.
  

Local fix

• Delete the useless configurations after migration.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server migration commands                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: WASPostUpgrade is adding back in the    *
  *                      SERVER_LOG_ROOT variable that was       *
  *                      deleted in the old config.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The SERVER_LOG_ROOT variable was standardized in a higher
  level variables.xml and deleted from the server level
  variables.xml by the customer.  It reappeared at the server
  level after migration completed.  It was added in by the
  profile creation because it is part of the template.
  

Problem conclusion

• Check it the SERVER_LOG_ROOT variable exists in the old
  variables.xml at the server level.  If so deleted it from the
  new target profile during WASPostUpgrade.
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.7 and 8.5.5.14.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP

• R900 PSY

     UP