Archive for March, 2008
OBIEE managing the cache: Seeding / Filling the cache
Now why should you want to do that? OBIEE is not a database, so why would this be an advantage?
No commentsOBIEE managing the cache: Emptying/Purging the cache
One of the most powerful features of OBIEE is the way it uses it’s cache. Good cache management can really boost your performance. From the system management point of view there are a couple of tips and tricks to influence the cache performance.
4 commentsOBIEE Continues Date Time Line
Because OBIEE graph types are not “Date/Time” aware you often face the problem of broken Date/Time Lines. If you don’t want to wait for OBIEE 11G you might want to try this alternative. Our table with fuel consumption entry’s doesn’t have an entry for each day after filtering:
OBIEE Optimizing NQQuery.log for debugging
When building and debugging OBIEE repository’s and reports you will often go back to the NQQuery.log. Depending on the security setting of the user the actual query send to the database will be logged here.Because the log can grow very quickly over time it often means having to scroll to the end of the log to find the information needed.
By default the maximum size for the NQQuery.log is 10MB. This setting is found in the NQSConfig.ini under USER_LOG_FILE_SIZE:
