The latest version of the Oracle BI Applications, 7.9.6 and 7.9.6.1 have not been out for that long. That goes as well for the newest version of the DAC clearly. And, perhaps it is that this release is so new and there are just enough changes that several bugs still got out in this release. Although these bugs are subtle and minor, they will pop-up on you in the damnedest of places, just when you thought you were sailing along swimmingly.
Now, if you read the systems requirements documentation word-for-word upon each and every OBI Apps release, no matter how minor the release, you may not need this information. But, if you are human, you may have missed the tiny section on page 12 of the related release document, http://download.oracle.com/docs/cd/E14847_01/bia.796/e14221.pdf. This page briefly highlights the fact that a DAC patch, 8760212, is required for this release of OBI Apps. It’s a DAC patch.
Read the full story
Working in OBI Answers you will probably run into this code every now and again. I typically bump into this error when I do a “Save As..” of an existing Answers view/report to create a new report built on only a few of the metrics which the original report was built. The full error is: Cube Definition is invalid (Measure out of bounds) Error Codes: GOA4AK7Z.
Cause:
This error is displayed because the pivot table or view that was previously referenced no longer contains the metric selection that previously was chosen. More to the point, the view no longer contains any reference to a metric. This error mainly arises when using the pivot table view as the other views have default references that bind successfully when parsed.
Solution:
Quite simple actually. Just select the Criteria tab in the Answers window. Click the view drop-down and choose the pivot table view in question (Edit the Pivot Table). When the pivot table edit page opens you will see that the Measures box within the pivoting criteria window is empty. Move a metric from the ‘Excluded’ criteria box to the ‘Measures’ box and you should be good to go.
Here is the problem as shown when the pivot table is referenced after getting this error and then choosing to edit pivot table.
In lieu of this solution one could also just scrap the answers report and recreate it. However, it is best to identify and understand why the problem occurring, thus fixing it and preventing it from happening.
