Which two options are included in Oracle BI Server cache management techniques?
A.
Using NQSConfig.ini to manually edit the parameters
B.
Scheduling Server password
C.
Maximum Number of Rows to Download to Excel
D.
Inspecting the cache reports
E.
Manage access to Subject Areas
Explanation:
A: Much of the configuration of OBI that used to be done in the NQSConfig.ini files
can now be done using this front end console, which in turns updates the NQSConfig.ini file.
Things in the NQSConfig.ini file that are set by EM are noted in the file with ‘# This Configuration
setting is managed by Oracle Business Intelligence Enterprise Manager’. Some things that needs
to be setup manually in the NQSConfig.ini file are:
1. Usage Tracking
2. Dynamic Libraries
3. Query Optimization Flags
4. MDX Member Name Cache Section (SAP BW)
5. More specific General Settings where EM doesn’t contain the level of detail required
D: Cache Management Techniques include
Inspecting the cache reports
Configuring the cache parameters
Setting caching and cache persistence for tables
Using the Cache Manager
Inspecting SQL for cache entries
Modifying the Cache Manager column displayPurging the cache entries manually using the Cache Manager
Purging the cache entries automatically
Using event polling tables
Seeding the cache
http://www.rittmanmead.com/2015/09/obiee-bi-server-cache-management-strategies/
http://obieeinterview.blogspot.ca/2010/04/cache.html
Inspecting the cache reports
Configuring the cache parameters : VIA NQSConfig.ini or EM(like biinstance->capacity management -> cache)
Setting caching and cache persistence for tables: phycial table, set cache exipration time
Using the Cache Manager : administration tool -> manage cache
Inspecting SQL for cache entries : administration tool -> manage cache -> select one cache entry -> right click that entry, inspecting sql
Modifying the Cache Manager column display
Purging the cache entries manually using the Cache Manager : administration tool -> manage cache -> select one cache entry -> right click that entry , purge cache manually
Purging the cache entries automatically
Using event polling tables : set polling table and trigge the inspection on ETL loading
Seeding the cache : priming (preparing) the result set before real query