This page uses Javascript. Your browser either doesn't support Javascript or you have it turned off. To see this page as it is meant to appear please use a Javascript enabled browser.
Use a lower move.thread.count if this server is in production to lower the CPU impact on Blackboard processes. In this case, we recommend you start by dividing the Xmx setting by 600 (half the number of threads).
On Windows, this must be a file name (not path).
You can re-run the tool multiple times if needed.
If you get intermittent non-fatal java.lang.OutOfMemoryError in the log file, this indicates you have some large files that your JVM’s RAM can’t accommodate.
Possible solutions:
If you get a fatal error saying failed; error='Cannot allocate memory', your -Xmx setting is greater than the available RAM on the box. Either edit movecontent.sh (or movecontent_fg.sh) to decrease the -Xmx setting, or increase the amount of available RAM on the box by stopping other processes or reconfiguring the box.
You can monitor the MoveCourseContent log, located in blackboard/logs/move-course-content/move-course-content-log.txt, to follow progress and for warnings specific to moving content within a course. Search for WARNING to find these errors.
The information contained in the Knowledge Base was written and/or verified by Blackboard Support. It is approved for client use. Nothing in the Knowledge Base shall be deemed to modify your license in any way to any Blackboard product. If you have comments, questions, or concerns, please send an email to kb@blackboard.com. © 2025 Blackboard Inc. All rights reserved