Monitoring for Batch Cube build Failure

[adam_mc]

What is the best methodology for monitoring a .bat file script for a cube create failure?

Right now, if the cube build fails, the cube reverts to its previous version and the subsequent reports are then re-created with yesterday's data.
I need to know if the cube build fails so that I can send an alert and also prevent the subsequent reports from executing.

Script for cube build is similar to following:

cd "C:\Program Files (x86)\ibm\cognos\c10\bin"
"C:\Program Files (x86)\ibm\cognos\c10\bin\cogtr.exe" -n2 -r4 -dLogFileName=Cube_batch.log -dLogfileDirectory="D:\BI\Jobs\Logs" -m"D:\BI\Models\Cube.pyj" -g

Is there some sort of suggested way to systemattically "investigate" the log file?
Other options?

Any thoughts would be greatly appreciated.
Thanks in advance,
Adam.

[RKMI]

Hi Adam,

Please see this link, http://mybyeexperience.blogspot.com/2011/10/cognos-transformer-cube-failure-alert.html I think the alert mechanism can be done.

What we current do just have a report sudio drill report, using layout calculation there is a function called "CubeCreatedOn ()". To show our users when it was last updated incase a failure occured.

Thanks,
RK

[bensah]

Hi ,

How those reports are executed ? If it is through scripts then in the cube refreshment batch file you create on trigger file if it fails or success. In report script it will check the trigger file and if it is success as trigger file then it will run the report. Hope it will helpful.