Mark Cann - Rittman Mead

OAC: Essbase – Incremental Loads / Automation

I recently detailed data load possibilities with the tools provided with Essbase under OAC here [https://www.rittmanmead.com/blog/2017/06/oac-essbase-loading-data/]. Whilst all very usable, my thoughts turned to systems that I have worked on and how the loads currently work, which led to how you might perform

Cloud

OAC: Essbase – Loading Data

After my initial quick pass through Essbase under OAC here [https://www.rittmanmead.com/blog/2017/06/oac-essbase-and-dvcs/], this post looks at the data loading options available in more detail. I used the provided sample database ASOSamp.Basic, which first had to be created, as a working example. Creating ASOSamp

Cloud

OAC: Essbase and DVCS

Finally managed to get around to having a proper look at Essbase within Oracle Analytics Cloud Service (OAC) after a busy couple of months. This post focusses mainly on initial impressions on the ‘out of the box’ the Essbase side of this - which we will explore in more detail

Technical

ASO Slice Clears - How Many Members?

Essbase developers have had the ability to (comparatively) easily clear portions of our ASO cubes since version 11.1.1, getting away from fiddly methods involving manually contra-ing existing data via reports and rules files, making incremental loads substantially easier. Along with the official documentation in the TechRef and DBAG,

Oracle BI Suite EE

OBIEE 11.1.1.7 + Essbase : Essbase Filters within Fusion Middleware 11g Security

Data and metadata filters are used with Essbase to limit access to data in a cube. When you use data filters to restrict access to a certain set of dimension members in the cube, the end-user can see that the member exists, but can't see any data associated with it.