ExtractBalanceData:Error::Cannot perform cube view operation. Essbase Error(1200766), Extract Balance Data Error: Cannot perform cube view operation. Essbase Error 1200766: Query result cells exceed the limit QUERYRESULTLIMIT

Handling Issues Related to Large Data Export from ASO Cubes

This section explains how to troubleshoot issues if you get Oracle Essbase query limit error when exporting a large number of data cells from ASO cubes.

Applies to

Oracle Hyperion Planning, Planning Modules, FreeForm, Financial Consolidation and Close, Tax Reporting, Enterprise Profitability and Cost Management, Oracle Hyperion Profitability and Cost Management, Sales Planning, and Strategic Workforce Planning.

Using EPM Automate Script

Because of the limits imposed by Essbase QUERYRESULTLIMIT, it is not possible to export a large quantity of data from Oracle Enterprise Performance Management Cloud user interface. To resolve this issue, Oracle has published a Windows PowerShell script which exports a large number of cells from an ASO cube using EPM Automate. See Automate the Export of a Large Number of Cells from an Aggregate Storage Cube in Oracle Enterprise Performance Management Cloud Working with EPM Automate for Oracle Enterprise Performance Management Cloud for detailed information.

Note:

You must use the 64 bit version of PowerShell to run this script.

Getting Help

If the execution of the EPM Automate script fails to export data or you face an issue when running the script, contact Oracle for help.

Create a Provide Feedback submission. Optionally, allow Oracle to access the maintenance snapshot of the environment by consenting to application snapshot submission. See Creating a Provide Feedback Submission.
Create a technical service request that identifies the Provide Feedback reference number. See Submitting a Technical Service Request. The service request must contain the following additional information:
- The name of the ASO cube from which you are trying to export data.
- The script file that you executed.
- Error messages that were displayed when you ran the script.
- The command, exactly as you used, to run the script.
- Did this issue start after the latest monthly update?
- If the data export was working previously, the date, time, and time zone when it stopped working.
- Snapshot of the environment, if available, from the last time when data export worked as expected.
- Application changes that you made since the last time data export was working as expected.
- Whether this is a critical outage.