Strange Logging Error

Post Reply
User avatar
Daniel Lennon
Posts: 6
Joined: Fri May 30, 2008 6:33 am
OLAP Product: TM1
Version: 9.1 SP2 Build 9.1.2.49
Excel Version: 2003 2007
Location: Sydney, Australia

Strange Logging Error

Post by Daniel Lennon »

Hi All,

Just noticed that my tm1server.log file (v9.1.2.49) has been invaded by a large number of the following errors:

11808 ERROR 2008-06-05 00:47:24,923 TM1.Cube Simple cell in thread private data tree with data type missing.Cube: xxxxx

By large I am talking about 80,000 in the last 24 hours.

Has anyone seen this before?

P.S. Thanks for the new home Martin :D
ScottW
Regular Participant
Posts: 152
Joined: Fri May 23, 2008 12:08 am
OLAP Product: TM1 CX
Version: 9.5 9.4.1 9.1.4 9.0 8.4
Excel Version: 2003 2007
Location: Melbourne, Australia
Contact:

Re: Strange Logging Error

Post by ScottW »

I don't know if you can access from the old forum
http://forums.applix.com/forum/tm.asp?m=13622

Quote from Mike Cirillo
This problem occurs because during the feeding process the second time the rule was changed we are changing the cell type from STET to SIMPLE. We record the change in cell type but nothing is noted about the cell data type because there was no change in the cell data; basically the cell data is expected to go back to whatever value it had before the STET rule was added. The same problem occurs if the cell was a rule calculated value and it was fed. The cell in this case would be changing from a FEEDER to SIMPLE. The solution is not trivial in this case if we want to keep the old value in the cell. It involves getting the cell value for a fed cell (which is never deleted from the data tree). Since there are a few things to think about to implement this solution and the only issues caused by this are: 1) The bogus error message that troubles users and 2) In some weird and complicated scenarios (for example a TI process that executes RuleLoadFromFile() and then CellGetN/S(), the cellget won't return the old value in the cell but 0 or an empty string)
Basically this was a bug in 9.1 SP2 that has been fixed in SP3. It is inconsequential except that it clogs up the tm1server.log file.

Cheers,
Scott W
Cheers,
Scott W
Cubewise
www.cubewise.com
Post Reply