Any seen my cube?!

[mweldon]

Hi
We're running Tm1 9.1.4, noticed one of the views stopped working - "cube 'Billing Category' not found"! Had a look in architect and the cube had indeed totally vanished! This is a permenent cube, fairly small and uncomplicated. Initially I could not even find 'Billing category.cub', however I noticed that there is a Billing Category.cub$ file.

In the tm1 log I found this:

5532 ERROR 2011-01-07 19:01:32,234 TM1.System.File sf_Rename: Failed to rename (d:\tm1data\abax\Billing Category.cub$) to (d:\tm1data\abax\Billing Category.cub). Errno: 13
5532 ERROR 2011-01-07 19:01:32,234 TM1.Commit CommitActionLog::SaveFiles() - Failed to rename file Billing Category.cub$ to Billing Category.cub

As you can see the cube rename failed a few days ago. The obvious solution seems to be remove the $ from the filename, and hopefully the cube will re-appear after the overnight restart.I was also reading http://forums.olapforums.com/viewtopic.php?f=3&p=5791 so I guess my questions are:

Has anyone experienced this before?
What are the possible causes and where could I find out what Errno: 13 is?

Thanks

[garry cook]

The dollar sign signifies a temp file - when the savedataall runs, if it doesn't complete for whatever reason, it will create a .cub$ file (same as any other file - eg .dim$). Shouldn't overwrite your initial .cub file though - that should still exist as the whole point of the dollar file is that it's trying and failing to over-write the initial file with the same name (ie the .cub).

Can be caused by running out of hard disk, RAM, virus checker locking the file, security access to the file changing, etc. All pretty damn unlikely but not impossible.

Do you have access to a backup of the .cub file prior to this happening? Safest to use this if possible.

If not, you can remove the $ sign but it's a bit risky - if the full save data had taken place but it simply couldn't replace the original file, it'll work if you rename. If it was half way through the save, it'll give you a garbled cube. By the sound of it, it's a small cube so you should be ok to rename as a .cub as it's likely to have fully prepared the .cub$ to overwrite.

I'd also have a look through the rest of your files in the data drive for any $ files. You may find you have a few of them if the access to the folder or somesuch has changed.

[mweldon]

thanks garry

I did indeed rename the .cub$ file and by the sounds of it I have been very lucky in that after the restart it came back absolutely fine!

I also followed your good suggestion of looking for other $ files but there were none. Seems to me like it was a one off oddity, lets hope it doesn't happen again!

Cheers

-Marc

[mweldon]

Unfortunately I've just had the same problem occur, with exactly the same cube. As before it worked when I renamed the cube file and restarted the server, but its quite worrying!
Will post if I am able to determine what caused the problem.

[Alan Kirk]

Unfortunately I've just had the same problem occur, with exactly the same cube. As before it worked when I renamed the cube file and restarted the server, but its quite worrying!
Will post if I am able to determine what caused the problem.

Garry mentioned it, but your virus checker would be the first thing that I'd be looking at. We ensure that our data directory is excluded from the scan. The last thing you want in the middle of a data save is your AV program blundering in and grabbing the file while TM1 is trying to rename it.