SAP BI Cube Zero Record Timing problem

This post is all about another problem that I faced in our production system. I had to do significant analysis/simulation to understand the problem.

When you have a configuration as below

1. Datastage job to post into BW (3.x datasource)
2. Infopackage triggered is of type – Update PSA and data target in parallel, typically a write optimized DSO
3. You use an external scheduling tool to trigger the datastage job
4. Have another BW chain to extract data from a DSO and post into a cube which is also triggered by an external scheduler

There is a possibility that your DTP load from the DSO to the cube could post empty data.

The reason why this happens is that, BW takes a lot of time to actually update the data in the WO DSO. BW responds back to datastage as soon as it recieves all the data and does not really wait for the data to get saved in the DSO.

If your BI system is slow for any reason, the external scheduler would trigger your DTP for the cube much before the data is actually saved in the DSO. This eventually results in zero records being transferred to the cube.

A solution to this problem is to only post to the PSA by datastage and have a process chain to push data to the DSO and DSO to the Cube.

 

Advertisement