V5 SAP BPC SP6 - Error creating Admin cache file - Account

[Former Member]

Dear

I come across following error message when processing dimension account.

Incorrect syntax near 'NOLOCK'.

If this is intended as a part of a table hint, A WITH keyword and parenthesis are now required.

See SQL Server Books Online for proper syntax.

Any ideas?

V5 SAP BPC SP6

thks

[sorin_radulescu · Accepted solution]

Hi Frank,

91 properties ???

This is really something to be avoided.

Any way to answer to your question.

Into dim table is created columns for all properties for every level.

That's means: if you have a dimension with 10 levelels and 91 properties actually your dim table will have: 91*10 = 910 columns.

Into system you have some limitation and it seems you arrive there.

Any way you have to change the design because having a table with 910 columns or even more the performances will be poor.

Maximum the properties shoulb be 30 in my opinion.

everything which is going over this number should be redesign into another way.

In your case I think you can build another dimension instead to create more and more properties.

Kind Regards

Sorin Radulescu

[Former Member · Accepted solution]

Sorin

Ok clear;

The application is a test application, not a live one

However 30 properties seem very strict no?

thks

Frank

[i045436]

Frank,

It is also depending by how many hierarhies and how many hierarchies levels you supposed to have for that dimension. The problem you will have is not on building this dimension, but on performance if you suppose to use it on a production environment with a lot of consurrent users.

As I told you before, in my opinion, the error you received are comming from an internal BPC mistake - some wrong size for an internal variable into a SP procedure that cut the value of a string variable.

There is no limitation in BPC for the number dimension properties(the limitation I found is related to the dimension level - hierarchy level), but you have to limit this to have a system working. As Sorin already said, if you really need all properties, you can split the dimension in two and we will gain for sure the performances.

Kind regards,

Mihaela

[i045436]

Into the BPC help files there are some specification regarding the database limitation.

(http://<servername:port>/osoft/help/admin/helpstart.htm#Client_Admin_Console_vs._Browser_Admin_Tasks.htm)

The levels into the dimension are limited to 64 maxim. The levels you can have in BPC is dependent on the number of properties in the dimension. his can be the source of error.

The error message seems to come from a SP which is building dinamically the code and the number of characters are over the size of a local variable.

Best regards,

Mihaela

[Former Member]

Mihaela

How are the level of the dimension composed? Is this equal to the number of properties?

thks

[sorin_radulescu]

It seems one of store procedure used for processing dimension is incorrect?

Into SP you have a selection like: select * from table NOLOCK and actually NOLOCK has to be between ().

Are you using any custom changes into your application?

Do you have the same problem also into apshell?

If you have the same problem also into apshell then I think the problem is related to upgrade script and you have to report this into OSS.

Regards

Sorin Radulescu

[Former Member]

Hi Sorin

The problem is deminsion specific, since on a different dimension on the same DB it works fine.

Probably the problem is related to the number of properties linked to the dimension.

I had created a large number of new properties which brought the total number of properties to 91. Then processing the dimension fails, while all properties have correctly been created in sql, the error appear on the updating of the cache file.

I have reduced the number of properties to 60 and now the processing runs fine.

Are you aware of a limitation of the number ofo properties that can be attributed to a dim?

V5 SP6

thks!

Frank