Solution for Browse View OutOfMemory error

[John Hammond]

Here's my solution to where you get locked out of your view because you have too many row and column elements - you need to convert to titles especially the large dimensions.

Create a new TI process and paste this into the advanced and prolog. (Nothing else is required)

# ViewTitleDimensionSet(CubeName, ViewName, DimName);

ViewTitleDimensionSet('cbsTrialBalance','vTI ClearOut','dimProject');
ViewTitleDimensionSet('cbsTrialBalance','vTI ClearOut','dimFunction');
ViewTitleDimensionSet('cbsTrialBalance','vTI ClearOut','dimChartOfAccounts');

Modify to fit your view using the view properties window in Architect. Once you convert enough dims to titles you will be able to view.

(Now awaiting someone who knows the easy way!)

[David Usherwood]

Select 'Export as Ascii File' then adjust the selections until it's manageable.

[Steve Rowe]

The easy way subject to system limitations.
In your cfg file.

MaximumViewSize
Optional Sets the maximum amount of memory (in MB) to be allocated when a user accesses a view. If you do not set the MaximumViewSize parameter, the default maximum view size is 100MB on a 32-bit system, and 500 MB on a 64-bit system.
To specify a maximum amount of memory allocation for views, add the following line to Tm1s.cfg:
MaximumViewSize=n
where n represents the amount of memory in MB to be allocated.

[John Hammond]

Thanks chaps - will give those a try also.

Steve:

Always thought the OutOfMemory limitation was on the client's memory.

What you are implying with the param being in .cfg (ie server level) is that the server builds the view on behalf of the client in its own address space as a separate entity even though it already has the cube loaded.

Is this right?

[lotsaram]

What you are implying with the param being in .cfg (ie server level) is that the server builds the view on behalf of the client in its own address space as a separate entity even though it already has the cube loaded.

When cubes are loaded into memory what is loaded are leaf level values. Consolidated values and rule calculated values are only calculated on demand when requested by a user in a view. The server then caches the calculated values (not just for the user who requested them but for all users) but only until any of the underlying leaf values change. This is why initial rendering of a view can take a while but subsequent view recalculations are much faster (unless there are data changes to the cube in the interim in which case the view must be rebuilt.)