KB268380: In MicroStrategy Enterprise Manager, Lookup tables in the Enterprise Manager warehouse are not populated correctly during the Dataload process: Objects appear as "DELETED" in Enterprise Manager reports

SUMMARY
This technical document covers a known issue with Strategy 10 Enterprise Manager, also affecting version 10.1 and 10.1 Hotfix 1. The Strategy Enterprise Manager Data Load fails to correctly migrate the lookup objects from the Metadata to the Enterprise Manager Warehouse lookup tables, which results in objects showing up as "DELETED" in Enterprise Manager reports. This issue will be addressed in the next Strategy 10 service pack. Also, a fix  has been developed to address this known issue in versions 10,  10.1 and 10.1 HF1
 
SYMPTOM
When running a Strategy Enterprise Manager data load from Operations Manager, the data load process is completed successfully. However, it can be observed from the Enterprise Manager reports that the reports, attributes, documents and other lookup objects are identified as "DELETED".
When directly checking the Fact tables (E.g. IS_REP_FACT, IS_DOC_FACT, etc.) using Strategy DB Query Tool, it can be observed that the the IS_REP_ID column (in the case of IS_REP_FACT) has a negative value for the report ID. When trying to find the matching Lookup Objects (example, the report name in IS_REP table, the document name in IS_DOC, etc.) there will not be any content in the Lookup tables that match the statistics table records i.e., an object which actually exists in the metadata does not show up in the corresponding lookup table.
 
CAUSE
This is a known issue caused by an incorrect order in the Lookup migration scripts, which causes the Staging tables to be truncated before their contents have successfully been moved to the Enterprise Manager warehouse lookup tables.
 
 ACTION
This issue has been fixed in Strategy 10.2. Take advantage of upgrading for a fix. Also, a fix  has been developed to address this known issue in versions 10,  10.1 and 10.1 Hotfix 1. Users needs to download the file attached to the end of this document and implement the following steps: 

1. Stop the Strategy Enterprise Manager Data Loader Service from Strategy Service Manager.
2. Make a backup of the jar file 'MAEMBackend.jar' from the location: "<install_drive>:\Program Files (x86)\MicroStrategy\Enterprise Manager" (Windows) OR "/opt/MicroStrategy/jar" (Linux).
3. Place the file downloaded from this document in the same location.
4. Start the Enterprise Manager Data Loader Service.
5. Run a Custom Time Window data load that covers the affected period.

 
Additional notes:
It is also suggested to review KB268204 to ensure that the contents of the EM_IS_LAST_UPDATE table are correct and there are no failed dataloads on it. Refer to the Woerkaround section in KB268204 for a detailed explanation on how to do so.