Mark Rittman has written a very thorough useful guide on using Subversion for version control in OBIEE. [ad#ad-1] I think this sort of strategy would be very appropriate for a large-scale project with many OBIEE developers. I’m personally using regular abundant backups of my project files, however, it might not be intuitive to someone else. I wonder how much effort does it take to maintain version notes?
David Kwan posted a very nice OBIEE caching article – To Cache or Not to Cache That is The Question. I found it very interesting and worth reading. From myself, I’d like to add that in some situations using cache is necessary – for example – a relatively static Dashboard report (maybe updated monthly) from a very large table. I am positive that it’s not worth it for a BI server or a database to waster resources running it for every user over and over.
I’m getting close to a 100 unique visitors daily. I’d really appreciate if you could take a minute and leave a comment about yourself – how did you find the blog? do you like it? how could I improve? did you find information you were looking for? do you check it daily / weekly? Please leave a comment – and let me know (just add “don’t publish”) if you don’t want your comment to be published.
Thank you in advance.
If your users are missing cache, you might find the service request below helpful.
User1 one and User 2 have the same profile but User 2 is not hitting User 1’s cache even though the physical queries are exactly the same.
Customer had implemented data-level security. This resulted in different SQL for each user.
Cache hits are not based upon the physical queries.
They were using session variables in the connection pool login/password fields. Each different login has a different query, the issuer of the query is different, this results in the cache being specific to a user / session variable.
They modified the connection pool to use a shared login/password and this resulted in a cache hit.
Something else, I’ve found. I suggest always adding 1.00* when working with non-integers, just for sake of convenience.
(Customers.”Total Customers” / sum(Customers.”Total Customers”)) * 100
The problem was caused because that Integer Data Type values are involved in the calculation. If the calculation is performed on Integer values, then the correct answer is ‘0’.
When a Grand Total is specified, then the Data Type is promoted to Double Precision. If the operation is performed on a Double Precision field, then non-zero values will be returned.
The solution to this issue and to ensure that non-zero values can always be returned in an OBI EE Report is by modifying the formula expression as follows: –
e.g. (1.0*Customers.”Total Customers” / sum(Customers.”Total Customers”)) * 100 or 1000*Customers.”Total Customers” / sum(Customers.”Total Customers”)