This content has been marked as final. Show 4 replies
Reasons Why a Query is Not Added to the Cache:
* Non-cacheable SQL element. If a SQL request contains Current_Timestamp, Current_Time, Rand, Populate, or a parameter marker then it is not added to the cache.
* Non-cacheable table. Physical tables in the Oracle BI Server repository can be marked 'non cacheable'. If a query references any non-cacheable table then the query results will not be added to the cache.
Cache hit. In general, if the query gets a cache hit on a previously cached query, then the results of the current query are not added to the cache. The exception is query hits that are aggregate roll-up hits.
* Result set is too big.
* Query is cancelled. This can happen by explicit cancellation from Oracle BI Presentation Services or the Administration Tool, or implicitly through timeout.
* Oracle BI Server is clustered. Queries that fall into the ‘cache seeding’ family are propagated throughout the cluster. Other queries continue to be stored locally. Therefore, even though a query may be put into the cache on Oracle BI Server node 1, it may not be on Oracle BI Server node 2.
But if I run the same report independently, it gets cached. So, guess the issue lies somewhere else.
Did u check the cache seeding checkbox while configuring the iBot??
Yes Deepak, I did.
I am also not able to see the query (for the report that am running thru iBot) in the nqsquery.log file.