WMB/IIB MustGather: problems with Migration on UNIX and Linux

1. Review the WebSphere Technical Exchange for your version:
   Webcast replay: Migrating to IBM Integration Bus V9.0
   Webcast replay: Migrating to WebSphere Message Broker V8
   Webcast replay: Migrating to WebSphere Message Broker V7
   
2. Check for known issues:
   Resolving problems that occur when migrating or importing resources

   IBM Integration Bus and WebSphere Message Broker FAQ for Migration

   
   WebSphere Support Blog (WMB Migration)
   WebSphere Message Broker support site

1. mqsidc

   See: mqsidc usage instructions
   

   • When running the tool, select the option for 'Broker Collector', when prompted.



2. mqsimigratecomponents command
   If you used 'mqsimigratecomponents', please send in the output of the command from the time of the failing migration. You can used the same command, post migration, to check or verify the current components.
   See: mqsimigratecomponents command


3. General Broker information
   If the mqsidc tool was not run, then capture this information manually
   • Record the WebSphere Message Broker version, release, and maintenance level.
     This can be captured using the command 'mqsiservice -v'..
   • Record the operating system version, release, and maintenance level.
   • Record the version, release, and maintenance level of any related products and components for the problematic application.
   • Collect the local error log.
     On UNIX and Linux systems, the local error log is the syslog.
     The location of your syslog is configured in the syslog daemon.
     See: Configuring the syslog daemon
   • Collect the Standard Output/Error logs.
     On UNIX and Linux systems, WMB writes information to both 'stdout' and 'stderr' files.
     These files are located under the Message Broker workpath.
     See: Standard System Logs

ATTENTION: A good problem description is one of the most important tools IBM needs to analyze your data!
When sending data to IBM, be sure to update your PMR or send a note with the following information:

• Tell us what errors you saw, where you saw them, and what time they happened
• Let us know if you made any changes to WebSphere Message Broker or the system before the problem
• Share any other observations which you think will help us to better understand the problem

• Use IBM Service Request to open or view a problem record with IBM.
• Send your data to IBM for further analysis.