TM1 cube published in Cognos. Delay in updating?

[ChrisF79]

Greetings:

We have a TM1 cube published in Cognos 10 and it's working great right now. I created an alias for each dimension called "CognosFormat" to simplify creating user-friendly names for our items, customers, etc. That all works well for us. I can go in and change numbers and run a simple TI process:

Code: Select all

RefreshMDXHierarchy('');

That pushes any new data out to the Cognos cube. However, if I change the name of an alias, it eventually changes in the cube but I have to wait a couple of hours. What is Cognos doing on the back-end (we're not rebuilding or republishing cubes) and is there a way to run this automatically or change the interval that it runs?

[Christopher Kernahan]

This is something I've seen some problems with, and I don't have all the answers on how it is working.

I believe officially the position is that any change to the cube structure (attributes included) requires a package republish.

Here is a hierarchy of other steps that I follow if I need to see the attribute asap.

Refresh the Package in Report Studio
Manually pick the package in Report Studio
Republish the entire package in Framework Manager
Clear the cache in the Query Service in Cognos Administration
Restart the Query Service
Restart all the Services
Restart Cognos
Restart the Server
Go home and wait until tomorrow

[PlanningDev]

I believe there is a metadata refresh interval setting in BI as well as a caching setting that may have an affect here. Ill have to see if I can look up the setting but you might look in the administrative tasks part of the BI portal.

[macsir]

If I were you, I will close the current IE and restart IE to check if it has been refreshed or not.