KB319822: Enterprise Manager data load hangs at ~98% in MicroStrategy Secure Enterprise 10.0 - 10.6

SYMPTOM
The Enterprise Manager data load reaches approximately 98% completion but never finishes.  Checking the status of the data load with Command Manager will indicate that the data load is still running.  Entries similar to the following will be found at the end of the Enterprise Manager log file (MAEntMgr.xml):
 

<log4j:event logger="MAEntMgr" timestamp="1486454636170" level="INFO" thread="pool-1-thread-3">
<log4j:message type ="DEFAULT"><![CDATA[Finished Fact Migration]]></log4j:message>
</log4j:event>

<log4j:event logger="MAEntMgr" timestamp="1486454636189" level="DEBUG" thread="pool-1-thread-2">
<log4j:message type ="DEFAULT"><![CDATA[Executing: Warehouse and Fact Update]]></log4j:message>
</log4j:event>

<log4j:event logger="MAEntMgr" timestamp="1486454636190" level="INFO" thread="pool-1-thread-2">
<log4j:message type ="DEFAULT"><![CDATA[Finish Updating Warehouse and Fact Migration]]></log4j:message>
</log4j:event>

<log4j:event logger="MAEntMgr" timestamp="1486454636190" level="DEBUG" thread="pool-1-thread-2">
<log4j:message type ="DEFAULT"><![CDATA[Finished Executing: Warehouse and Fact Update]]></log4j:message>
</log4j:event>

<log4j:event logger="MAEntMgr" timestamp="1486454636190" level="DEBUG" thread="pool-1-thread-3">
<log4j:message type ="DEFAULT"><![CDATA[Command moved to execution: Warehouse and Fact Update]]></log4j:message>
</log4j:event>

<log4j:event logger="MAEntMgr" timestamp="1486454639398" level="DEBUG" thread="pool-1-thread-3">
<log4j:message type ="DEFAULT"><![CDATA[Finished executing: Fact Migration]]></log4j:message>
</log4j:event>

 
The key indicator is that the task "Warehouse and Fact Update" is marked as "Finished Executing" on one thread (thread 2 above) and then is marked as "Command moved to execution" on a different thread afterward (thread 3 above).
 
This is a known issue in Strategy versions 10.0 through 10.6.
 
ACTION
This issue is addressed starting in Strategy 10.4 Hotfix 3 and Strategy 10.7.
 
WORKAROUND
A workaround for this issue is to force the data loader process to only utilize a single thread during the data load. This can be set by running the following SQL query in DB Query Tool against the Enterprise Manager Warehouse:

UPDATE EM_PROPS SET EM_PROP_VALUE = '1' WHERE EM_PROP_NAME='THREAD COUNT';

 
After making this change, the Enterprise Manager Data Loader service must be restarted in order for the change to take effect.
The internal case reference number for this issue is DE38308.