Enabling Language Translation
If you are thinking about enabling language translation on your Oracle Business Intelligence web site, remember only the text that OBIEE provides out of the box will be automatically translated into the selected language. You will have to customize all data, dashboard titles, reports titles, logical columns, etc to the appropriate language(s).
Differentiating Your Environments
Have you ever made a change to a report within one environment but meant to do it in another? Try modifying the style sheet whereby changing the section or heading color to differentiate your environments. Migrating the repository or web catalog will not carry forward any style sheet modifications.
Debugging issues with Logical SQL
Have you ever encountered errors when trying to develop and test a logical SQL statement issued directly to the Oracle BI Server? One common root cause is the use of SQL constructs not supported by the OBI Server; sub-queries are particularly sensitive. According to the Oracle documentation, only the following sub-query predicates are supported (in addition to UNION and UNION ALL):
IN, NOT IN
Any, >=Any, =Any, <Any, <=Any, <>Any
All, >=All, =All, <All,<=All, <>All
EXISTS, NOT EXISTS
For example, try using <Any instead of <. If this does not fix your problem, see if a physical SQL statement is being generated when you run the logical SQL statement. If so, try running the physical SQL directly against a database, and the database error description may provide the information you need for debugging.
Avoiding the CAST Function
To improve query response time, try pushing columns that are calculated with the CAST function down to the database level. You should see a significant performance improvement, especially if the DBA can add an index to the database column.