BPMMigrate troubleshooting

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
This command imports the migration snapshot. If you see an exception when you run this command, it might be caused by running out of memory. Otherwise, you can diagnose the problem by changing the log level to FINEST and running the command again.
If the BPMMigrate command runs out of memory, increase the Java™ heap size.
  • For Linux operating systemFor UNIX operating systemEdit install_root/bin/wsadmin.sh. Find PERF_JVM_OPTIONS and increase the value of -Xmx256m to -Xmx512m.
  • For Windows operating system Edit install_root\bin\wsadmin.bat. Find PERFJAVAOPTION and increase the value of -Xmx256m to -Xmx512m.
You can increase the heap size to more than 512 if you have more memory on your system.

To diagnose other problems, change the log level to FINEST as described in "Troubleshooting migration." After you run the command again, check the log file named BPMMigrate_timestamp.log. The file is found in snapshot_folder/logs/. If you cannot find the cause of the problem, you can provide the log to IBM® support.

For the scheduler migration, the BPMMigrate command runs the AdminTask that is registered during server startup and uses the scheduler service to re-create each scheduler task. The trace for the AdminTask is saved in snapshot_folder/logs/. The log for the scheduler migration is saved on one of the active nodes, in install_root_26.0.0.0/profiles/custom_profile/logs. Collect both the trace file and the log file for analysis if an exception occurs.

Make sure that the messaging engine is started before you run BPMMigrate. Otherwise, the command fails when it tries to migrate the service integration bus messages.

For Linux operating systemFor UNIX operating system

Applications fail to import or deploy after migration on Linux or AIX

 Linux:  AIX:  If applications fail to import or deploy after you run BPMMigrate, and the log does not contain a clear error message, check whether the snapshot name contains a period (.) character. The intermediate storage platform can silently strip the period from the snapshot name during transfer between environments. Because the BPMMigrate command does not warn about this condition, the failure occurs only during import or deployment.

To resolve this issue, rename the snapshot to remove any period characters, then run BPMMigrate again.