If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Missing MUN on the saved cube reports after every cube refresh

Started by bpsanoj, 12 Jan 2010 08:13:38 AM

Previous topic - Next topic

bpsanoj

Hi All,

  we have cognos 8.3 ServicePack4 installed in the machine.
While opening a previously saved cube report in analysis studio, a window appears with the message "<you must update the analysis 'ABC' because it refers to items that are either no longer present in the model or inaccessible because of security restrictions.For best results, we recommend that the analysis author perform this action>".

We have tried keeping the source unique within all the levels of the dimension but still the issue persists. We are using calendar dimensions with Month level, week level and at day level(lowest) in our cube.
The cube is refreshed on daily basis.(Not an incremental load, fully loaded cube build we are using)

Thanks all for your valuable comments!!

MFGF

Hi,

How is your Transformer model defined? (mdl or pyj)  Are the generated categories stored in the model?  If so, they should not change each time the cube is built unless you are doing a "clean house" in Transformer.

MF.
Meep!

bpsanoj

Hi,

Thanks for looking into this.

It's mdl.
No categories are generated/saved in the model.
We are building the mdl cube in LINUX server machine. 

Please advise.

Thanks

MFGF

Yes - that's the issue.  It sounds like you have non-unique IDs within your dimensions, and Transformer is forcing their uniqueness by appending ~<number> to the non-unique category codes.  The number is randomly generated, so the category codes (used in the MUN) are changing.

You either need to eliminate the non-unique IDs as the data is being read from the source, perhaps using data source calculations, or use a Windows version of Transformer where pyj models are viable so that the categories can be generated once and saved as part of the model.

MF.
Meep!

bpsanoj

HI,

Earlier the source of all items were used as caption values, which is non-unique for few levels within  dimension. Eg: A(Country)->B(State)->B(region)->C(city)

Hence I tried changing the source values of the items used in all the levels within the dimension to businesskeys , so that the source values stays unique.
And I gave the label as the captions(non-unique) in the cube model since the caption in the AS needs to be as such.

After cube builds the same issue persists again.

Also need to confirm when the relative time category (Eg: week numbers changes) changes gradually, whether the corresponding MUNs also changes after day by day cube refresh(builds)??

Thanks

MFGF

Hi,

When I mentioned uniqueness, I was referring to uniqueness of the categories within each dimension (not just each level).

For example, if you have a products dimension with Product Line, Product Type and Product levels, the category codes for each would need to be unique within the dimension (ie having a Product Line with a category code of 1 and a Product with a category code of 1 would result in a non-unique ID, which would then trigger the tilde (~) behaviour to enforce uniqueness in Transformer.

MF.
Meep!