Cogtr.exe - Retry cube generation if cube is locked

[Bark]

Hi,

I am trying to automate the generation of a cube but I am getting the following error:

(TR0787) The locking of cube cubeName failed. It is probably in use by another application. Select Yes to retry, No to create the cube using a temporary name or Cancel. [->Cancel]

I know it is locked as I am using it with Cognos BI but what I want is for the command to hit Yes (to retry) instead of cancel. Is this possible? How?

Thanks and regards,

Bark

[bdbits]

If you are using a batch file to build the cube, have you set options on the cube property deployment tab and used option "-g" in your command line? For example, something like this: cogtr.exe -n2 -i -r4 -c -g your.pyj

You can also run into this if you are trying to build the cube in the same location as the published cube.

The logon being used to run the batch file must have read/write permissions to the published cube folder.

Hope something in the above helps.

[Bark]

I am a bit confused. I know why the cube is locked, what I want is for the batch to try until it goes through. This is basically hitting "Retry" when the error comes until it works.

I don't really have the issue any more as the cube automation process of my company does not allow me to change the command line but I'm still interested in the answer for the future.

Thanks and regards,

Bark

[cognostechie]

Cognos 10.1 has a feature to hande this. It has the ability to build a cube by the side of the existing cube and then point the connection to the new cube. Once you create a script to build the cube, you can use the script instead of building it manually. For details and command line, pl. see the Transformer guide.

[RobsWalker68]

Hi,

I'm not aware of a command line option that will retry until it completes, but I think from Transformer 8.3 onwards this issue was made moot by the use of the build/deployment option.

The cube is created in a build location and then on completion it will automatically deploy to the configured deployment location.  The reporting tool will instead look at this stub and this removes the issue with locking.

If you deploy using this method you can keep your script file as is.

Regards

Rob