Adding hints without Repository (RPD) change
Adding hints without Repository (RPD) change
Adding hints at the table level or join level is most common however requires a RPD change. This involves server restarts and downtimes.
NB: These hints are always overridden by the repository hints, so in order to make these to work there shouldn’t be any hints in the repository atleast for the same tables.
1. Go to BI answers and start a new request
2. To add a report specific hint in the request, the first column in the request should have a function with the hint as shown here
As shown in the above diagram the evaluate function is used to create the hint in the database sql but with the table alias, to know the table alias – use the Query repository utility in the BI Admin tool
So in this case the alias will be T69092.
It is very easy to understand if you know what evaluate function is actually used for in OBIEE, if not please take a look at one of the John’s article on it, in simple this function is used to execute database functions from Oracle BI.
For the convenience of others who reached this blog just to see how hints are applied in OBIEE Repository, I am giving that information below;
Adding hints at Table level:
A table level hint is actually passed as part of the database sql everytime an answer based report uses the table. For example, to add a table level hint, go to the table properties and enter the hint in the hint text box as shown here
Adding hints at Join level:
Sometimes it may be required to have the hint only during a particular join between the tables and in this case a hint can be added at a join level. For e.g. Go to the join properties and enter the hint text