TSV errors and creation of aggregates

Question

Hi experts,
Since few days, I can't run any more a query. It makes different shorts dumps like :
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TABH_POOL_NO_ROLL_MEMORY
TSV_TNEW_OCCURS_NO_ROLL_MEMORY
The query is based on a Infocube which contains 3 584 086 records. Once by week, entire data is deleted and reloaded.
There is'n any aggregatesfor this Infocube.
Do you know if the creation of aggregates in order top optimize performance of the query can resolve this kind of technical problem ?
My second part of my question is about aggregates :
In my query, we want to display the masterdata Article (0MATERIAL) and some of his navigation attributes (_Department_, Sub-department, Family). We want to display the plant and one ratio Stock data.
In this query, we make a restriction on a charactestic XXX by excluding a value.
My idea was to create an aggrgate with Article, Department, Sub-department, Family, Plant, and the characteristic XXX with a value excluded.
But when I create the aggregate, I firstly drag and drop the article. But when I want then to drag and drop his navigation attributes, a warning is generate : "Article cannot be  in aggregate because of characteristic Department".
- We can't put in an aggregate a masterdata with some of his navigation attributes ?
- Is it possible in an aggregate to restrict a characteristic by excluding a value ? Apparently, we can only add a constant...
I can bring some precisions if it's necessary for better understanding.
Thanks for your precious help,
Tempka

Answer 1

Hi Tempka,
  It seems that there are issues with your roll memory where the memory is not enough to execute your query.
TSV_TNEW_PAGE_ALLOC_FAILED and TSV_TNEW_BLOCKS_NO_ROLL_MEMORY
You will need to get the roll memory extended by contacting your Basis team / ERP team.
Just before you go to ERP team, check if the data base indexes for the info cube on which the  query has been developed are fine or not. You can check the DB indexes by following the below steps:
1) Right click the cube, Click on manage.
2) Click on Performance tab,
3) Check DB indexes.
4) If the check shows Red, Then recreate the DB indexes by clicking on "Create DB Index (batch)". Once the indexing is complete  try running the report again & see if the error comes.
Also
Thanks
Pawan