TM1 Forum

Guys,

One of servers crashed today and we got the following error messages in the day before it went down:

55 ERROR 2009-06-16 08:49:46,015 TM1.Blob StringRead - Read failed: 1

15 WARN 2009-06-15 06:11:28,088 TM1.Server TM1ServerImpl::FileSave could not reacquire lock on object with index 0x40000003
15 WARN 2009-06-15 06:11:28,088 TM1.Server TM1ServerImpl::FileSave could not reacquire lock on object with index 0x40000004
15 WARN 2009-06-15 06:11:28,088 TM1.Server TM1ServerImpl::FileSave could not reacquire lock on object with index 0x40000005
15 WARN 2009-06-15 06:11:28,088 TM1.Server TM1ServerImpl::FileSave could not reacquire lock on object with index 0x40000006
15 WARN 2009-06-15 06:11:28,088 TM1.Server TM1ServerImpl::FileSave could not reacquire lock on object with index 0x40000007
15 WARN 2009-06-15 06:11:28,088 TM1.Server TM1ServerImpl::FileSave could not reacquire lock on object with index 0x40000008
15 ERROR 2009-06-15 06:11:28,094 TM1.Process Process "00 save data": Execution was aborted. Error file: <tm1processerror_20090615061128_00 save data.log>

Any ideas?????

Server: Fujitsu Solaris 10
Software Version 9.1 SP3 U2

It crashed while I was trying to complete a data export,

Jim.

Most messages on Windows are next to useless, but some of the Unix stuff looks almost helpful, like it might be trying to save stuff and couldn't. I assume you have plenty of disk space?

Any chance of a conflict with anti virus software? Perhaps this software was kicking off as you happened to trying to write to the cubes?

Thanks for the replys guys. There was plenty of disk space on the allocated mount. As for virus software I'm not sure. We share our box with a piece of software called debt manager. It may have something to do with that. I will investigate further........

if you do the export again i think it won't crash, right?

I did do the export again but slightly differently:

1) I cleared some historic data out of a cube to make sure that enough memory was available.
2) I mad my dimension selections more compact. (Even though ignore consolidations was ticked I removed them all manually anyway)

Due to both of the above I guess it's diffcult to say that I was not able to replicate. I kind of guess it means I was able to work my way around it,

Jim.

Jim

We get those all the time. What version are you on - 9.1 by any chance? Apparently it is a bug when TM1 is saving data to disk. Cognos say that the save data is still working, but it is producing spurious messages. Personally I am not convinced, as I have had too many cases of things that I could have sworn I had saved, when then don't seem to have changed after the nightly restart of the TM1 service.

This is apparently cured in 9.4.

Regards

Paul

Sounds about right. Cheers Paul,

Jim.