The ASO export, and the limit that shapes it

ASO cubes report fast and export badly: the routes run over MDX, numbers only, under a five-million-cell limit Oracle does not raise. The design answer is to keep level 0 where DATAEXPORT can reach it, and this page covers both the routes and the design.

Note: Some Planning cubes store data in ASO, a format built for reporting speed, not for exporting. In Planning, Oracle's module where budgets and forecasts are built, that difference decides your export route. This page is the three routes and their limits.

The whole module is mapped on the Planning index.

RuleChunk MDX extracts under the limit by design, prefer the BSO side wherever level 0 lives there, and treat the limit as an input, not an incident.

Neversize an ASO extract without doing the arithmetic. The limit is documented behavior surfacing as a failed job, and the fix is arithmetic done before the schedule, not after.

◆ The three routes, with the limit, MDX and its ceiling, the Calc Manager route, and the design escape.

Route out of ASO	The limit that governs it
MDX, directly or through Data Management	Per a documented trace, BSO sources extract by DATAEXPORT and ASO sources extract by MDX, numbers only. MDX-based extracts are governed by QUERYRESULTLIMIT, set at 5,000,000 cells, and per field experience Oracle declines to raise it. The workaround is chunking: one request per month or per entity branch, sized under the limit by design.
Calculation Manager level-0 export	Added for ASO cubes in a 2018 update, per the practitioner note that celebrated it, and still the pragmatic route for whole-cube level-0 pulls.
Move it to BSO first	Where hybrid holds the plan and ASO only reports it, export from the BSO side and skip the problem. The aggregation page explains when data genuinely lives only in ASO.

The hybrid caveat completes the picture: hybrid cubes export like BSO at level 0, which is one more argument for the balanced hybrid design. If the only complete copy of the data sits in an ASO reporting cube, every export inherits the MDX limit; if level 0 lives in the hybrid cube, the tuned DATAEXPORT applies and the limit never enters the conversation.

THE USE CASE, SIMPLIFIED

The problem: The reporting cube is ASO, the export keeps hitting the five-million-cell wall, and nobody documented why.

What we build: The right route per cube: DATAEXPORT for BSO, chunked MDX for ASO, sized under the documented limit.

What you get: Every cube exports nightly without failures, and the limit is a design input, not a surprise.

ASO extracts failing at month end?

We size the chunks against the documented limit, wire the schedule, and the reporting cube exports as reliably as the planning cube.

Talk to us

Terms on this page

QUERYRESULTLIMIT: 5,000,000 cells per MDX query. Not negotiable, per the field record.
chunking: One request per month or branch, sized under the limit.
numbers only: MDX extracts carry no text. The next page handles the words.
the design escape: Keep level 0 in the hybrid cube, and DATAEXPORT applies.