This document describes the new features in Oracle Essbase Studio Release 220.127.116.11. For more information about these features, see the Oracle Essbase Studio User's Guide, available when you access the online help in the Essbase Studio Console, or in PDF and HTML help format on the Oracle Technology Network.
Each time you deploy an Oracle Essbase model, deployment history data is stored in the Essbase Studio catalog. When you migrate the catalog to a new release in a new environment, or export and import the catalog, the deployment history, which is contained in the catalog, is also migrated. If there are many rejected records, the history can grow too large, causing the migration to fail.
In previous releases, there was no option to clear deployment history from Essbase Studio Console. In Release 18.104.22.168, you can clear deployment history from Essbase Studio Console for a single Essbase model. In Metadata Navigator, you right-click the Essbase model and select Deployment History and then Clear Deployment History. Clearing deployment history requires Oracle Essbase Studio administrator privileges.
In previous releases, there was only the option to clear deployment history for a single Essbase model using the cleanModelHistory command line utility. In 22.214.171.124, there are two new command line utilities you can use to clear deployment history for all cubes and all models in the catalog:
The globalCleanModelHistoryAndLeaveLastSucc utility clears deployment history for all cubes and all models in the catalog and leaves the latest successful record for each deployed Essbase model.
The globalCleanModelHistory utility clears all deployment history for all cubes and all models in the catalog, including successful records.
With drill-through reports, you create spreadsheet reports that display data retrieved directly from external relational data sources.
In Release 126.96.36.199, when creating a drill-through report, you can connect to an alternate data source. An alternate data source is a data source other than the one that was used to create the Oracle Essbase cube. If you have a data source with a similar data schema, you can define the drill-through report to access it instead.
You can require users to enter a user name and password to access the database when performing drill-through. When you select Require user name and password on the Report Contents tab of the drill-through report editor, Oracle Smart View for Office users must enter a user name and password to access the database during drill-through.
Use the Cumulative Feature Overview tool to create reports of new features added in prior releases. This tool enables you to identify your current products, your current release version, and your target implementation release version. With a single click, the tool quickly produces a customized set of high-level descriptions of the product features developed between your current and target releases. This tool is available here: