Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Oct 19, 2021

WASPreUpgrade + WASPostUpgrade take days to run when processing large files

WASPreUpgrade and WASPostUpgrade allows a migration between two WAS versions, e.g. 8.0 to 9.0 or 8.5 to 9.0. The WASPreUpgrade process effectively exports the data from the original profile. The WASPostUpgrade effectively imports the data from the profile. In some situations, the WASPostUpgrade task will modify some of the data imported. In other situations, it makes no modifications to the data.

If a profile contains a large file, both WASPreUpgrade and WASPostUpgrade processes will continue to run, however, they may take days to complete successfully. The WASPostUpgrade process in particular appears to be the slower of the two processes. This can be reproduced by leaving large files - e.g. a core dump, trace files, sizable .ear applications - etc. in a profile during the WASPostUpgrade process.

A local fix for this issue is documented in an IBM APAR that was closed "SUG", or suggestion, not implemented in the code:

"Local fix

Remove any large files that should not be present in the

WebSphere file system


Further commentary - this is not an issue related to the underlying hardware speed. Adding more disk IOPS will not help here, this is purely an issue with the code in use. Manually copying the large file on the filesystem outside of the WASPostUpgrade code takes one minute at most, versus days within the WASPostUpgrade code.

Idea priority Low
  • Guest
    Dec 8, 2021

    Hi Cindy - I can manually create a core dump in the WAS admin console in WAS 855x, which will produce a multiple GB sized file in the WAS profile, migrate to WAS 905x, and this will reproduce the issue. Therefore this is not a HCL Portal only issue. Request to further reconsider. Thank You.

  • Guest
    Dec 7, 2021

    This issue seems to be particularly troublesome to Portal based on where Portal creates large data related to core dump, trace, etc. Based on only 1 vote and the amount of rework needed to ignore these files, this request will not be implemented, and we are changing the status to Not under consideration. We recommend that Portal continues its pre-processing to remove large files that are not needed.