Oracle Transactional Business Intelligence
Length function issue
Please use CHAR_LENGTH instead of LENGTH
In OBI, there is an issue with the LENGTH function where it causes the report to take up multiple times the normal memory require to run it, which causes issues with our servers. We are looking into fixing this. As a workaround, please use the CHAR_LENGTH function instead. the only difference is that CHAR_LENGTH will count trailing blanks if any, however, in our database, only free form text fields can have trailing blanks in someone accidentally puts some in the field so there should be no problem.