Caching in OBIEE/OBISE1

Question

Here is list of my research that corresponds to the Caching issue in OBISE1 well its similar to OBIEE atleast in this aspect,this list pretty much covers caching that can occur different levels.I would suggest to start one by one and see how caching is corresponding in the Dashboard and please do contact me if you need further help
A.Cache Management
For this release of the OBIEE, if you run an initial or incremental load without first
clearing the query cache, it is possible that reports that you run after the load process will reuse the cache that existed prior to the load process. This can result in inconsistencies between reports. There are several alternatives to mitigate this situation,
such as:
• Configure the query cache to expire daily.
• Clear the cache tables manually as needed; for example, after you complete a load process.
• Schedule the system to clear the cache tables at the same frequency as the
incremental load process.
To clear cached queries:
1. Open the Oracle BI Administration Tool in online mode.
2. Click Manage, Cache to access the Cache Manager page and select all cache entries.
3. Click Action, Refresh.
To disable the cache:
1. Locate this configuration file: <root
directory>\OracleBI\server\Config\NQSConfig.INI.
2. In the Query Result Cache Section, change the [ CACHE ] setting from ENABLE =YES; to ENABLE = NO;.
3. Save the NQSConfig.INI configuration file and restart the Oracle BI Server service.
See: Oracle Business Intelligence Server Administration Guide, "Query Caching in the OracleBI Server" chapter for more information on query caching in OBIEE.,
B. After running an Answers report, check the SQL NQQUERY.log (on Windows, usually located in, :\OracleBI\Server\log\)
TIP:
Turn off caching in the NSQConfig.ini (and restart the server service) or at the physical table level in the .rpd, to ensure you get the un-cached results, and can therefore see the SQL being generated each run, or drill down in Answers.
C.Found this in documentation(if using OBISE1,for OBIEE refer to OBIEE documentation on CACHING)
http://download-west.oracle.com/docs/cd/B40078_02/doc/bi.1013/b31770.pdf
all about caching in OBISE1
But important thing to note is that Caching occurs at different levels
Server (NQSConfig file ,look for ENABLE parameter)
Administration(if you click on the TOOL in the MENU bar ,there you would some options related to OBJECT in the physical layer )
OBIEE Dashboard Query level (in answers when making the ad-hoc query ,there is a check box which can checked or unchecked depending on whats desired in terms of caching).
This is to the best of my Knowledge but please free to add some more details if you feel If I missed something.
Four logs to check are as follows
NQServer.log
NQQuery.log
NQSAdminTool.log
NQScheduler.log
I hope this covers some ground as to Caching in OBISE1/OBIEE
Thank you,
Mohammad Alam

Answer 1

Hi Mohammed,
Thank you for the VERY thorough and useful digest of OBIEE Caching!
We've found that caching to be less-than-satisfactory. We've enabled caching at the NQSConfig level, and set the max time out to 5 minutes, but for some reason our users are not seeing data refreshed.
For example, we have a report that shows Sales Order shipments. The order status can go from "Booked" to "Picked" to "Shipped" all within 1 day. However, the report will show "Booked" when the transaction actually has been "Picked".
I've tried unchecking By pass server cache in the report's Advanced tab, but to no avail.
Any suggestions or comments? Our current workaround is NO caching at all.
irene