If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Cube Automation failure using .BAT in windows scheduler

Started by sidney786, 05 Jul 2010 04:40:15 AM

Previous topic - Next topic

sidney786

Hi,
I am currently experiencing a problem with windows scheduler, I have scheduled a DTS job that truncates data and then builds a cube off that data via a batch file within the DTS process.

The truncate part works fine, however the PowerPlay Transformer hangs. I have scheduled a batch file to build another works great. I an ensured that no transformer sessions are open at time of build. Extract from the log.

LogFileDirectory=\\xxxxxx\cognos\cubes\logs
ModelSaveDirectory=\\xxxxxx\cognos\cubes\models\
DataSourceDirectory=d:\xxxx\iqds\
CubeSaveDirectory=\\xxxxxx\cognos\cubes\building site\
DataWorkDirectory=\\xxxxxx\cognos\cubes\temporary files\data1\
ModelWorkDirectory=\\xxxxxx\cognos\cubes\temporary files\model\
MaxTransactionNum=25000000
ReadCacheSize=65536
WriteCacheSize=65536
Temporary UDA directory=D:\xxxx\Temporary Files\Impromptu Temp

I have run the content of the batch from the command prompt; runs fine.

I have launched the batch file manually; works fine.

I have ran the DTS job manually; works fine.

Just when I automate it on windows 2000.
I am stomped at this..any suggestions would be great. :'(

Batch File content : "C:\Program Files\Cognos\cer3\bin\trnsfrmr.exe" -n2 -s "\\xxxxx\cognos\Cubes\Models\Cube (xxxxxx).pyi"

ndsharp1

Are you Cognos 8? We have this problem after we converted. IBM said to use Cognos SDK to schedule jobs to run but we haven't been able to figure out how to make that work yet. We found there is also an SDK as part of Transformer but don't know if that has anything to do with it or not. I can't find anything written about it,it is very frustrating. We are trying to schedule and run a .bat file that builds data cubes automatically so we don't have to do it manually.

mikewalker

Have you looked at the permissions on your Win2000 setup?

Do you have write permissions to the build directories?

Which user is the automated batch file running as?

You might need to set the batch file to run automatically using your login (ie on behalf of yourself).