Testers needed for Data Retention issue in 10.2.1 FP1

[sir_jeroen]

Hi all,

I need your help on this.
In my case I have a situation where my data is "cached" too long and over several sessions.

Could you give the following a try if you have time this.

1. Create a table in your Database
2. Add 10 records
3. Create a FM model and publish it.
4. Create and Save a report on this table (turn Allow Local Cache off)
5. Run the report in Cognos Connection
6. After running the report delete 5 records from the table
7. Run the report again (In my case I still get 10 records returned)
8. Log off/ Logon
9. Run the report again (In my case I still get 10 records returned)
10. Log off/ Logon as DIFFERENT user
11. Run the report again (In my case I still get 10 records returned)
12. Open the table in FM (You'll see 5 records).

Could you share your results of this test?

I have this issue in the following Configuration:
----------------------------------------
Cognos Components:

• BI Server x64
• Powerplay Server x64
• Mobile x64
• Samples x64
• DQA x64
• Language Pack (Dutch) x64
• FP1 x64

OS:                Windows 2008 R2 Standard x64
Contenstore: Oracle 11.2.0.1 x64
Reporting Database: Oracle 11.2.0.1 x64

Database client used: Oracle 11.2.0.1 x86
----------------------------------------
Please share your results.


I know that this issue doesn't occur when Using SQL Server 2008 x64 Express Edition.

Thank you!

[MFGF]

Hi RA,

Are you using CQM or DQM for your database access? With DQM I'd expect caching to be shared between users and sessions.

MF.

[sir_jeroen]

Hi MF,

I only use CQM.
I hope you have time (and of course if you want to... ) to test this, because then I have extra information to add to my PMR at IBM Cognos Support.

Ciao,

RA

[cognostechie]

Hi RNA -

I noticed the same issue when I was trying to find a solution to switch databases for a report. You are right, FM reads the latest records but the reports do not. The only time it read new data is when I published the package again. Publishing the package clears the cache. I found the reason to be that, by default, Cognos does caching. That setting is enabled by default when you install Cognos.

I resolved it by disabling the cache. After that, I deleted the records from the DB, ran the report and it did come up with the latest data. Now every time I run the report, it does go to the DB.

Here is how to disable the caching.

Copy the c10_location/configuration/CQEConfig.xml.sample file to c10_location/bin and rename it CQEConfig.xml.

Open the c10_location/bin/CQEConfig.xml in Notepad.

Locate this line:

<entry name="queryReuse" value="5"/>

Change the value from 5 to 0.

Save the CQEConfig.xml file.

Restart the service from Cognos Configuration.

However this would mean that it will never do caching, no matter what so even the parameter values will be retrieved each time.

[sir_jeroen]

@Cognostechie:
I tried that option too, but it didn't work....
But there's progress: It's now registered as a defect under PM98894

[cognostechie]

That's very strange. It did work for me. Every time I run the report, it does go to the database and I tested it thoroughly and
it is also working in client's production environment.  The database is Oracle though I don't remember which version it is.

[sir_jeroen]

Yep it's strange.. but it's now in the hands of the defect team... So hopefully they get a fix soon...

[beris]

We have the same issue.

We have the following Cognos components installed: BI Server x64, Mobile x64, FP1 x64

OS: Redhat Enterprise Linux 2.6.32-358.18.1.el6.x86_64
Contenstore: Oracle 11.2.0.3.0 x64
Reporting Database: Oracle 11.2.0.3.0 x64
Database client used: Oracle 11.2.0.3.0 x86

[sir_jeroen]

Tnx..

There's a fix available: ask support for Interim Fix 1048.

[javisarmiento]

Hi @ReportNet Adict,
i have the same problem that you mention, please could you specify how to solve it, maybe you could share this fix pack. Thank you for your response.

[bdbits]

Contact IBM/Cognos tech support. We recently applied FP1 and found the same problem for an Oracle 11g database where we had near-realtime updating going on. As was mentioned, there is a hot fix, which you need to get through support.

[javisarmiento]

Thank you @bdbits, i'll keep try contacting IBM support to get this hot fix.