Unexpected Essbase error 1007083 - Essbase
In Essbase calculation scripts, when an IF statement is performed, it will perform the first element of the IF statement first, check if the combination being calculated meets that criteria and calculate it if it does or pass to the next element, i.e the next ELSEIF. IFERROR MaxL - Surprises in Essbase Part V ~ Oracle GlennS calls them as issues Cameron Lackpour calls them as stupid tricks and I chose surprises. 🙂 I had to experiment on this because I had to prove that I was not wrong 🙂 and also to explain why it behaves this way. People who are not aware of IFERROR (I don’t think you are one among them) According […] Oracle BI Solutions: Hyperion FAQ'S
Oracle BI Solutions: Hyperion Essbase Interview Questions
• Improved cube build time by investigating and toggling the Essbase cache and buffer settings, I/O settings, Dimension re-ordering as well as the dense/sparse Dimension tags Data Cache Size Recommendation – Why? | Cube Coder
32-bit Essbase: 4 GB. 64-bit Essbase: 256 TB. Buffered I/O: 1 MB (1,048,576 bytes) Direct I/O: 10 MB. Combined size of all ess n.ind files, if possible; otherwise, as large as possible. Do not set this cache size higher than the total index size, because no performance improvement results. To determine the total index size, see Index Files.
Bart Stone - Owner - BStone Consulting Ltd. | LinkedIn • Improved cube build time by investigating and toggling the Essbase cache and buffer settings, I/O settings, Dimension re-ordering as well as the dense/sparse Dimension tags Data Cache Size Recommendation – Why? | Cube Coder The Essbase Database Administrator’s Guide tells us that the recommended size of the Data Cache is 1/8 the size of the Data File Cache. Even granted the usual caveats on these recommendations, I think this one is really odd. The first headscratcher here is that if you use Buffered I/O (as almost everyone does) there is no Data File Cache.