SYMPTOM:
In Strategy Enterprise Manager 9.x, multiple report executions by different users report the same execution timestamps, as shown below. The report job and execution times show the same information for both executions. Only the RP First Job Request Timestamp metric shows unique data for each execution.
CAUSE:
When a report execution from Strategy Desktop hits cache, no new jobID gets created and the statistics logged for this report execution are pulled from the report execution that originally created the cache. This means the execution times and report job ids are the same as the original report execution which created the cache. This cache hit information is logged in the Statistics table IS_CACHE_HIT_STATS (and not in IS_REPORT_STATS as the original report execution). When a data load is performed, information about all the jobs i.e., cache hits and non-cache hits gets moved into the IS_REP_FACT fact table.
ACTION:
No action is required as this is the expected behavior in Strategy Enterprise Manager 9.x. If it is desired to determine each unique report execution run, add the 'RP First Job Request Timestamp' metric to the report template and also users should make a note of the 'Cache Hit Indicator' attribute data.
