Invalid Object name after collapse (compress) the cube

[Former Member]

Hi experts,

I'm working with BPC on BW7.5. After compresing one of my cubes, when I try to Display Data I got the following error:

Invalid Object name: /B28/XXXXXXX
SQL Error: 208

Seems the compresion is changen some table name and after that, the cube is not longer usefull.

Any thoughts?
Thanks in advance.

[Former Member]

Number of requests you do not want to collapse = 0

For clarifing,

1. First, I found out the Lite and Full optimizations were doing nothing to my models. I know this after checking the data on the cube as well as checking the requests, which were not green flaged.

2. I use BW trying to collapse the cube: Inforprovider > manage > collape tap. Eventhought it works (I can see the requests all flaged green I'm not able to access to the cube data and I got the error.

2. Back in BPC, I did the modificaciones on the process chain base on the link i attached before. The I try to access the model from BPC or the cube from BW I got the error again and the cube/model become unavailable. When I solved the error by "shaking the model" (creating a new property on a dimension) I can see the optimization has been done.

Basically the problem it is not with the optmization itself, but because of the optimization, something it the model/cube is not-adjusted.

[former_member186338]

"First, I found out the Lite and Full optimizations were doing nothing to my models. I know this after checking the data on the cube as well as checking the requests, which were not green flaged." - by default "Number of requests you do not want to collapse" is 2!

"I use BW trying to collapse the cube:" - don't do it!

[former_member186338]

Incorrect reason to close answer! No accepted answer!

[former_member186338]

BPC embedded?

[Former Member]

No. Classic or Standard.

[former_member186338]

"After compresing one of my cubes" - how you performed it?

[Former Member]

Lite and Full optimization didn't work so I tryied from BW backend.

Infocube > Manage > Collapse tab > Collapse with 0 compresion

[former_member186338]

Sorry but main rule in BPC - don't use BW instruments with bpc cubes!

What do you mean by light optimization didn't work?

[Former Member]

I meant that I run them and, nor compresion neither "zero removal" were happened. But today I did some modificaciones on the process chain for the Lite optimization package base on some advices i found in this foro, and now it works but I got the same error when I try to access de cube.

Basically, after including the "zero removal" option on the process chain, when I run Lite optimization, the package status is Abort, and when I run a report, I got the same error as when I tried to access the cube throught BW.

-------------------------------

code: UJO_READ_EXCEPTION_000 severity: error description: MDX statement error:"SQL Error: 208" log id: 051MibWC7jU2WQvgcnb0nW DATAVALUE:SQL Error: 208

-------------------------------

I found out how to get the model funtional again (adding or removing a property on one of the model dimensions) and I can see the optimizations worked now.

Thanks for your help.

[former_member186338]

In future don't use bw tools on BPC cubes! Unpredictable results...

"But today I did some modificaciones on the process chain for the Lite optimization package base on some advices i found in this foro, and now it works" - can you describe the changes you have done?

[Former Member]

Sure, I followed the steps described here:

https://blogs.sap.com/2010/06/10/optimization-with-zero-elimination/

[former_member186338]

You only implemented zero elimination setting for compress?

Then I do not understand what do you mean by: "nor compresion"?

[former_member186338]

P.S. And before your changes what was the value of "Number of requests you do not want to collapse"?