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

Cognos BI 10.2.1 - Dynamic Query Mode for TM1 - caching

Started by monbar82, 18 Dec 2014 10:06:12 AM

Previous topic - Next topic

monbar82

Hi All,

Does anyone has some experience with caching data in DQM coming from Tm1 cubes?

I have found below sentence in this source http://www.ibm.com/developerworks/data/library/cognos/infrastructure/cognos_specific/page529.html

"For IBM Cognos TM1, there is no caching on the IBM Cognos 10 side therefore these tasks do not apply to that data source."
It is for version 10.1.1 and I cannot find anything new about it.

I have the following problem. I have TM1 cubes published as packages in Cognos BI 10.2.1 (DQM).
Reading metadata takes about 2 minutes, before query for fact data.
I have to find the way to skip this step as this source will be used to Ad-hoc reporting, dashboard, where user can filter content.

My idea was to clear cache every night, and schedule one report, which will load metadata. But,...
1. I do not really see option to clear cache as I do not have this option to choose TM1 data source.
     New Query Service Administration Task - does not contain TM1, it contains DMR, Oracle Essbase, Cynamic Cube, SAP BW...

2. Framework Manager contains governors for DQM, but are they relevant also for TM1 sources?
    I have published the package with configured governors, so it should not be DB, Connction or signon dependent
    User on BI side have the same privilidges, but thay are not able to share cache.


Any ideas or links to relevant articles, I have already read couple of them, but they didnot help.

Thanks


MFGF

Quote from: monbar82 on 18 Dec 2014 10:06:12 AM
Hi All,

Does anyone has some experience with caching data in DQM coming from Tm1 cubes?

I have found below sentence in this source http://www.ibm.com/developerworks/data/library/cognos/infrastructure/cognos_specific/page529.html

"For IBM Cognos TM1, there is no caching on the IBM Cognos 10 side therefore these tasks do not apply to that data source."
It is for version 10.1.1 and I cannot find anything new about it.

I have the following problem. I have TM1 cubes published as packages in Cognos BI 10.2.1 (DQM).
Reading metadata takes about 2 minutes, before query for fact data.
I have to find the way to skip this step as this source will be used to Ad-hoc reporting, dashboard, where user can filter content.

My idea was to clear cache every night, and schedule one report, which will load metadata. But,...
1. I do not really see option to clear cache as I do not have this option to choose TM1 data source.
     New Query Service Administration Task - does not contain TM1, it contains DMR, Oracle Essbase, Cynamic Cube, SAP BW...

2. Framework Manager contains governors for DQM, but are they relevant also for TM1 sources?
    I have published the package with configured governors, so it should not be DB, Connction or signon dependent
    User on BI side have the same privilidges, but thay are not able to share cache.


Any ideas or links to relevant articles, I have already read couple of them, but they didnot help.

Thanks

It's my understanding that because TM1 is memory-resident, Cognos 10 BI does not cache TM1 data. If TM1 is taking a long time to return metadata, this could be where the members are initially being read into memory by TM1 on initial access to the cube. There's nothing you can do to affect this from the BI side, as far as I'm aware - it's TM1 doing this not Cognos 10 BI.

Why do you need to "clear the cache"? Are the dimensional structures changing regularly? If so, restarting the TM1 server should flush memory, but why do you need to?

MF.
Meep!

bi4u2

I have a client using BI with TM1 and we found the need to run the "clear the cache" option pretty frequently. They found a dimensional structure changing pretty frequently and thus the need to clear the cache or else the entire report would not run. Their particular instance was when employees changed their status from active to inactive or inactive to active and this might show up in the dimension differently after nightly processes were run.