SYMPTOM:
When running reports in Strategy Enterprise Manager 9.x, users may find some users or user groups missing even though these objects exist in the metadata and a data load process has been recently performed, as shown below:
CAUSE:
The manual and scheduled data load process carried out by Enterprise Manager is run for a time window beginning at the last migration and ending at the current time. Objects that exist in a project's metadata, will not be updated in the Enterprise manager Warehouse by the data load process if they have not being modified in this time window period.
Understanding why the objects were not migrated in the time period when they were modified is incident specific and can be investigated provided a MSTRMigration.log file is available for the time period in question. In many environments the cause appears to be a failed migration that has been subsequently recovered (by only performing a fact migration) and the metadata objects modified or created in this time period have never been migrated.
ACTION:
There are two possible means of rectifying this condition. The first one would be to identify the Migration window in which these objects were created or modified and to run the Custom time window data load over this window. This action assumes that the statistics for this time period are also available since the custom time window purges the Enterprise Manager Warehouse for the time window and reloads it from the raw statistics data.
The second option would be to modify the object that has not been moved causing its modification time to be changed. The next time a Strategy Enterprise Manager 9.x data load takes place, its new definition will be updated in the Enterprise Manager Warehouse.
This object modified and migrated by the data load process will now be available for reporting in Strategy Enterprise Manager 9.x.
