powerplay dataserver could not find a record

[Filip.Cuppens]

All,

I know this issue has been posted before, but it seems like noone had the answer at that time. Perhaps in the meanwhile someone has found the reason and solution for this issue ?!

We get the above error (powerplay dataserver could not find a record) when we try to run a report using Cognos Anlysis Studio 8.4. If we access the cube from PowerPlay Client we do not get any errors.

Anyone any idea ?

Regards

[MFGF]

Hmmm - I've not seen this problem before.  Do you get this error when first opening the cube in Analysis Studio?  Is this with a blank initial report or a default initial report?  If you find the package for the cube in Cognos Connection and click on 'More', then 'Modify the package configuration', does the cube package have a default analysis assigned to it?  What happens if you try to use the cube package in Query Studio and/or Report Studio?

MF.

[Filip.Cuppens]

That's a lot of questions ...

We get the error when we try to open both the blank report or open an existing Analysis. We even get the error when the package information is loaded in Report Studio. So it seems it's not a particular studio that's generating the error, but really the Powerplay Dataserver. I found some messages on the internet about this error, but they all seem to be related with Transformer. I checked the Transformer log file and there we do not have this issue.

Even more strange, when we build the cube using the .MDL file we do not get the error. When we save the .MDL file as .PYJ file we do get the error. Not sure yet if this is the case each time we build the cube from the PYJ file. So I'm a bit puzzled. My guess is this has to do with memory or lack of space, but so far we have not been able to find any system logs to confirm this.

So any suggestion which might point us in the correct direction is welcome

Regards

[MFGF]

Could it be a corrupt pyj file?  Does the problem still occur if you open the mdl version and save it as a new pyj then build the cube from that?

[Filip.Cuppens]

Unfortunately, yes it does, we tested that already

[MFGF]

How big is the physical cube file?  Could it be exceeding the 2Gb max?

[Filip.Cuppens]

No, not yet. It's pretty large, around 1.8 Gb, but it's not exceeding 2Gb. And if I'm not mistaken the cube will fail loading if it exceeds 2 Gb ?

Regards

[MFGF]

Hi Filip,

When you build the cube from the mdl version of the model, is the cube filesize any different from when it's built from the pyj version?  I'm slightly baffled why it should work from mdl but not pyj - just wondering if the pyj version introduces anything extra which is causing cube access errors, perhaps based on it being a physically larger file?

You could also try playing with the MultiFileCubeThreshold setting in cogtr.xml to see if splitting the cube into two or more physical files helps matters.  0 means it is disabled, so you could try setting it to (say) 10,000,000 to see if it makes a difference.

MF.