PM72952: MIGRATIONS MAY FAIL FOR VARIOUS REASONS IF THE ULIMIT OPEN FILES SETTING IS TOO LOW

8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15

APAR status

• Closed as program error.

Error description

• Migration is very file intensive and requires that the
  allowable number of open file handles be set at the WebSphere
  Application Server recommended level of 10000 or higher.  Not
  having enough file handes may cause OutOfMemory, hangs,
  incomplete file transfers, and so on.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Migration Tools                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: Hangs, OutOfMemory errors,              *
  *                      FileNotFoundExceptions and other        *
  *                      migration failures may be due to not    *
  *                      having enough File Handles available    *
  *                      for migration to complete the process.  *
  ****************************************************************
  * RECOMMENDATION:  After applying this fix, a message will be  *
  *                  written to the Trace and Log Files          *
  *                  recording the setting of the ulimit -n      *
  *                  value.                                      *
  ****************************************************************
  Often the default ulimit -n setting is way below the
  recommended minimum value of 10,000 as recommended be
  WebSphere Application Server.  This can cause a variety of
  failures at various times during the migration process.  Often
  increasing this value causes the problem to be resolved.  Many
  times you have no idea what this value was set at when the
  migration tools were run.
  

Problem conclusion

• Since this value must be set before running the migration
  tools - the best we can do is to detect the value and record
  it in the Trace and Log files.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 7.0.0.25, 8.0.0.5, and 8.5.0.1.  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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP