Cube builds running twice 1

[macrus]

Has anyone else experienced a cube build that when initiated by a DOS batch file, runs through its FULL build process TWICE before completing??

Here is the DOS command that we issue against our server machine.

c:\program files\cognos\cer3\bin\trnsfrmr.exe -n f:\cogdata\models\CLAWpayments.pyi

This command has run perfectly well for the last 2 years but only recently has been taking twice as long to run. After viewing the log it was plain to see that the reason it was taking twice as long was due to each separate step typically performed during a cube build was completed in order once end to end, followed by a second run through.

Just thought I'd ask around to see if anyone has experienced something like this. I suspect it may have nothing to do with Cognos as our setup has been stable for over 12 months now.

thanks folks,
Macrus

 

[spicysudhi]

must be submitting the job twice.
post the full script of ur batch file generating cube and also the log where it says Cube build complete (1st run) and Cube build started (2nd run).

first thing i suggest is to check schedule, sombody must have played with the server!

regards,
sudhi

 

[flex13]

This is a bug that has been logged with Cognos. Stay tuned for a fix.

 

[macrus]

Thanks for both quick replies.

sudhi8645: The command I posted previously is executed on the server by the scheduling tool TNG.

Here an excerpt from the log showing the end of the cube build followed by the immediate start of the 2nd run.

04/26/2004 08:23:02 AM 4 00000000 Updating the PowerCube data.
04/26/2004 08:23:02 AM 4 00000000 Updating the PowerCube data.
04/26/2004 08:23:05 AM 4 00000000 Performing DataBase Commit at record number 125268.
04/26/2004 08:23:05 AM 4 00000261 End Write leaving 80659 categories remaining..
04/26/2004 08:23:05 AM 4 00000000 Timing, CUBE UPDATE,00:00:03
04/26/2004 08:23:05 AM 4 00000000 Committing PowerCube(s).
04/26/2004 08:23:06 AM 4 00000000 Timing, CUBE COMMIT,00:00:01
04/26/2004 08:23:07 AM 4 00000000 End cube update.
04/26/2004 08:23:07 AM 4 00000000 Timing, TOTAL TIME (CREATE CUBE),14:52:02
04/26/2004 08:23:08 AM 4 00000000 Start category generation.
04/26/2004 08:23:17 AM 4 00000000 Initializing categories.
04/26/2004 08:23:17 AM 4 00000000 Timing, INITIALIZING CATEGORIES,00:00:00
04/26/2004 08:23:17 AM 4 00000000 Start processing data source 'f:\cogdata\data sources\datedn.iqd'.

As you can see, after reporting the TOTAL TIME(CREATE CUBE), the next message (1 sec later) is the begining of the 2nd run.

I am VERY interested in what flex13 has mentioned: BUG and if there are any more details on Cognos' response.

There is definitely a STAR on the way to anyone with more details as to what Cognos have to say on this issue.

cheers,
Macrus

 

[macrus]

Extra Information:

We have feverishly been reviewing our archived logs from the past 12-18 months and have found that this problem began occuring when we upgraded to Version 7.1

The log completes 2 passes and subsequently runs each IQD twice (doubling the time taken to build a cube).

1st pass = Timing, TOTAL TIME (CREATE CUBE),00:35:04
2nd pass = Timing, POPULATE,00:34:31

Is there a setting we may need to disable/enable in Transformer that we cause this type of run to occur?

thanks<
macrus

 

[flex13]

As mentioned before (sorry should have elaborated a bit) this is a bug in version 7.1 of Transformer and has been fixed in version 7.1.504.