Report turns to NA 1

[ukflix]

When updating a report with calculations the report suddenly turns all values to NA. Auto Calculation is set on and there is no reason to show NA's. if we add a new row and column, their specific values show OK but only for their row/column intersect. If we do an explain it shows like this below. Has anyone seen this before or have any ideas on what causes it or how to fix it please?

"Calculation: ([, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + ([, , ] = error - [, , ] = error) + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error + [, , ] = error) / 1000

 

[drlex]

I've seen this in PowerPlay (client, not web) when the cube has failed to build correctly, but NA shows for all values, not just intersects. If you're using PowerPlay, can you confirm the report works by opening it as against a back-up cube?

soi la, soi carré

 

[ukflix]

Hi drlex, thanks for the reply.
I forgot to mention that this is with the client version. I know that the cube is OK as when I drag new rows and columns I do get values (but only where a new row and column meet). It's just that the rest of the report has all turned to NA for no reason. There is no calculation containing missing elements which I find usually causes NA's (as well as cube not building as you stated).

 

[drlex]

Well, I understand you can get 'NA' showing in certain circumstances when using 80:20 and when using forecasting. Just to rule out incomplete cube built, did you try opening the report as against a back-up copy of the relevant cube?


soi la, soi carré

 

[ukflix]

Hi drlex. We have no suppression in use neither do we use forecasting. The report is the same against a Backup and a rebuilt version of the cube. I think we are going to have to put this to corruption. What do you think?

 

[drlex]

Sounds plausible, and the best cause of action - hope it wasn't too complex. I've had to re-create transformer models before when I've received the 'contact cognos support' error (the trick of saving as mdl hadn't worked) and it's a right royal, fur-lined, ocean-going P.I.T.A.

soi la, soi carré

 

[vzak]

What I would fo is:

1. Clean House
2. Remove cube(s) from the model
3. Save the model
4. Delete temp files
5. Try to reboot the server/desktop

In 95% cases it helps.

Vlad