KB440970: Process crash occurs randomly using Oracle as Statistics database during data load execution with MicroStrategy Enterprise Manager 10.x

SYMPTOM
Process crash occurs randomly using Oracle as Statistics database during data load execution with Strategy Enterprise Manager 10.x. In other scenarios, it is observed that the core dump for the database connection process is generated under the Enterprise Manager directory.; the data load itself may succeed or fail. And when it fails, the trace in MAEntMgr.xml may not be the same.
Althoug, the below record can always be confirmed in DSSErrors log: 

[MultiProcess][Error] Find target process dead while waiting for reply

Sometimes the DSSErrors log show as below:
 

2018-02-21 05:01:03.879+09:00 [HOST:xxxxx][SERVER:][PID:33763][THR:518924032][MultiProcess][Error] Find target process dead while waiting for reply
2018-02-21 05:01:03.906+09:00 [HOST:xxxxx][SERVER:][PID:33763][THR:439039744][Database Classes][Error] Execute Query failed. 
Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [23000:1400: on SQLHANDLE] [Strategy][ODBC Oracle Wire Protocol driver][Oracle]ORA-01400: cannot insert NULL into ("xxxxx"."EM_LOG"."EM_MESSAGE") Connection String: DSN=MSTR_ST;UID=xxxxx;SRVR=sv_msgy;. SQL Statement: insert into EM_LOG(EM_TIME,EM_MESSAGE) values (to_date('2018/02/21 05:01:03','YYYY/MM/DD HH24:MI:SS'),'').

CAUSE
If Oracle database has been used for the Statistics and Enterprise Manager repository, in some specific cases, when the multiple processes spawned by the Enterprise Manager Data Loader Service contend for resources, it is possible to hit a Multiprocess exception.
The Enterprise Manager Data Loader Service has a limitation on the way it handles the Multiprocess exception errors, and so the data load process is interrupted.
 
ACTION
This random crash issue can be prevented by setting the "UseMultiprocess" flag to "false" on the machine running the Enterprise Manager Data Loader Service. Refer to Action in KB289904 on this operation.
The Enterprise Manager Dataloader service should be restarted after this change and there is no need to restart Intelligence Server service. With this change, the execution time to complete a data load is expected to be longer but no more than 3 times of the previous execution time. And if the data load is scheduled at midnight, it is considered as safe to set this flag to False.
KB440970