Potentially corrupting a cube
Hi everybody, asking this question on behalf of a parter.
They are removing contracts from a cube in a customers environment and carried out the following steps
- Took backup of cubes
- Took backup of tree for contract (ensuring it was well formed)
- Cleared all contracts
- Reloaded the tree (after removing the contracts not required in notepad++
- Reload cubes.
Now this seemed to work ok so not sure if this caused the corruption as Josef loaded in a few contracts ok but a day or so ago the contracts stopped uplifting every year and eventually we tracked this down to a data flow to ‘Temp Other Cost %’ so we investigated and I noted that the cube was not allowing us to read it in a data view so I tried adjusting the cubes sparsity (which should clear it) but the cube retained its size so we cleared it on clearing the size came down to 0 could see it in a data view even though there was no data and then the process worked correctly.
Just wondering if you have come across a cube corruption like this and if is there anything I can run against the DB to check it. (we did start and stop services a few times during the investigation)
Thanks
Accepted Answers
-
Did you perform an "unload database" after clearing the tree? I usually perform an unload when I clear entities or adjust max item numbers to make sure the changes are saved to disk and not causing any unwanted behaviour.
Kind regards,
Bettina
2 -
Good point @Bettina Clausen.
@Ken Walsh you can give the below as a reference for this type of activities. Here we are describing all the steps to perform:
2
