The following configuration setting of NQSConfig.INI file, is managed by Oracle Business Intelligence Enterprise Manager.
[Cache]
ENABLE = YES
If you change this entry directly in NQSConfig.INI file then it will revert to the original value whenever you restart the BI server.[Cache]
ENABLE = YES
You need to login to Oracle EM 11g Fusion Middleware Control and navigate to
Farm_bifoundation_domain
->Business Intelligence
-> coreapplication
Click on 'Capacity Management' tab and 'Performance' subtab.
Then click on 'Lock and Edit Configuration' ,
under 'Enable BI Server Cache'
uncheck the checkbox
'Cache Enabled'
Click on 'Apply' to apply the changes, then 'Activate Changes' and restart BI Server.
This would automatically change the Cache entry in NQSConfig.INI file.
Farm_bifoundation_domain
->Business Intelligence
-> coreapplication
Click on 'Capacity Management' tab and 'Performance' subtab.
Then click on 'Lock and Edit Configuration' ,
under 'Enable BI Server Cache'
uncheck the checkbox
'Cache Enabled'
Click on 'Apply' to apply the changes, then 'Activate Changes' and restart BI Server.
This would automatically change the Cache entry in NQSConfig.INI file.
See the direct link to the OBIEE Administration guide:
http://docs.oracle.com/cd/E28280_01/bi.1111/e10541/querycaching.htm#i1005378
Update
You change the settings in the instanceconfig.xml file to force the OBIEE server to never use cache.
<ServerInstance>
———
<Cursors>
<ForceRefresh>false</ForceRefresh>
</Cursors>
——–
</ServerInstance>
Now restart the OBIEE Presentation server service and test the results.
Note: Keep in mind that this parameter will cause the Presentation Server to always bypass its cache.
You would probably only ever want to use this setting if you were doing some kind of performance testing where having no cache is the requirement, but also potentially in some development environments with fast changing data streams.
Update
You change the settings in the instanceconfig.xml file to force the OBIEE server to never use cache.
<ServerInstance>
———
<Cursors>
<ForceRefresh>false</ForceRefresh>
</Cursors>
——–
</ServerInstance>
Now restart the OBIEE Presentation server service and test the results.
Note: Keep in mind that this parameter will cause the Presentation Server to always bypass its cache.
You would probably only ever want to use this setting if you were doing some kind of performance testing where having no cache is the requirement, but also potentially in some development environments with fast changing data streams.
