TM1 Forum

Hi all

a quick one really i bet someone out there has already got the answer,

I recently read an article in the Help hints and tips section about Dimensions that do not have any linked cubes to them which worked perfectly
http://www.tm1forum.com/viewtopic.php?f=21&t=4901

i added a dimensiondestroy section and instant removal of errant dims. i was wondering if anyone was able to point me to a place i can find one for all the errant files like Cube files that do not work Rux files that arent linked to a cubes, Processes that do not work (normally they have an exclamation mark next to them)

anything that finds all the above would be great,

thanks guys

"Cube files that do not work"

Why would a cub file not work?
Do you have a cub file with dimensions that are not part of the TM1 model?
In that case, the TM1 server will not load the cub file.
This will be a manual task to go throught the cub files in the data directory.

"Rux files that arent linked to a cubes"

Again, a manual task, look for rux files without a cub file with the same filename. Like BalanceSheet.cub that exists, but not for instance BS.rux (if a renaming took place).

"Processes that do not work (normally they have an exclamation mark next to them)"

They will be in the data directory, so you should be able to locate them and delete manually.

All tasks could be coded and automated, but I do not think that you will gain a lot of time.
So manual work will be the solution to you.

Cub files when certain dimensions have been removed still try and get loaded but fail on restart..


and all i see is the word "manual" im not a fan of Manual thats why i got into IT

As said above, there is not much scope in automation for these tasks.

Only point 2 could be done with a little bit of VBA code (Dir function) or TI (WildCardFileSearch).

The 2 other points will be much more work to code, compared to the gain you book.

Darkhorse wrote:Cub files when certain dimensions have been removed still try and get loaded but fail on restart..

The only place you'll see an error when this has occurred is in the message log. So again you're looking at a manual trawl through the log.

These are all one-off tasks though. At most they'd take you an hour for the whole cleanup. Trying to automate the task would take days. Sometimes manual is faster.