Troubleshooting: Extract infocube

Document created by ggallo Employee on Jul 13, 2017
Version 1Show Document
  • View in full screen mode

Extracting an Infocube (using a procedure command) produces a .txt file as well as a .cfg file which contains its structure.


During database tuning activities and/or during the normal maintenance activities, the file track and field orders might change, and consequently a data-reader initially based on the former structure/field order needs to be updated.


Consider the following example:

In this database there are 3 entities, which are all part of an infocube.


This Infocube would be therefore structured by "Time", Entity "A", Entity "B", Entity "C" (let's ignore sparsity)

When extracting it, the output file track would be:









if you change the Entity "C" max item number up to 2000 and extract again the same Infocube the file track would be different:

(note the Entity C positioning)








The output file track depends on the Entities Max Item Number:  they will be sorted in from the entity with the highest Max Item number to the entity with the lowest.



  • The time entity is the last column before values
  • If two entities have the same Max Item Number, the entity earlier created precedes the other (regardless of the entity row number)
  • The number of loaded items does not affect the file track
  • The entity included into a Sparse structure are always put before the dense ones ; within the Sparsity the order is given by the Max item Number as above
5 people found this helpful