Direct edit dimension collection has not been cleared before commit

Post Reply
lotsaram
MVP
Posts: 2987
Joined: Fri Mar 13, 2009 11:14 am
OLAP Product: TM1, CX
Version: TM1 10.2.2 PA 2.0x
Excel Version: 2010 2013 365
Location: Switzerland

Direct edit dimension collection has not been cleared before commit

Post by lotsaram » Thu Jun 22, 2017 2:23 pm

Has anyone ever seen the following ERROR status log message in the tm1server.log and know what it means?

ERROR TM1.Commit Direct edit dimension collection has not been cleared before commit.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.

User avatar
qml
MVP
Posts: 1036
Joined: Mon Feb 01, 2010 1:01 pm
OLAP Product: TM1
Version: 10.2.2
Excel Version: 2007 - 2016
Location: London, UK, Europe

Re: Direct edit dimension collection has not been cleared before commit

Post by qml » Tue Jul 04, 2017 2:28 pm

What version did you see it in?

I have started seeing this message after upgrading our on-premise 10.2.2 from build 10.2.20300.98 to build 10.2.20700.43. It happens at the end of any process that makes use of the Direct metadata functions, but seems to have no impact on the completion status of the process or its outcomes. However, I have seen it coincide with a rollback/restart of a process on one occasion - but I don't have enough evidence to conclude that it was caused by this error.

In any case this looks like a defect to me.
Kamil Arendt

lotsaram
MVP
Posts: 2987
Joined: Fri Mar 13, 2009 11:14 am
OLAP Product: TM1, CX
Version: TM1 10.2.2 PA 2.0x
Excel Version: 2010 2013 365
Location: Switzerland

Re: Direct edit dimension collection has not been cleared before commit

Post by lotsaram » Tue Jul 04, 2017 5:26 pm

Thanks for the response. This is on 10.2.2 FP7 and we didn't see it on FP5 which was the previous version on this site.

Got a somewhat dubious response from support which didn't clarify at all whether this is an actual error or overenthusiastic logging.

Although there is is odd (very rare) use of DimensionElementInsertDirect in the system with the error the odder thing is that this error crops up at random after commits of dimensions and not always necessarily the ones where TI is using the direct update functions.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.

Gabor
MVP
Posts: 169
Joined: Fri Dec 10, 2010 4:07 pm
OLAP Product: TM1
Version: [2.x ...] 10.2.2
Excel Version: Excel 2010-2013
Location: Germany

Re: Direct edit dimension collection has not been cleared before commit

Post by Gabor » Wed Jul 12, 2017 11:38 am

I've seen that error after moving to 10.2.2 FP7, but could get rid of the message by adding "DimensionUpdateDirect(DimName)" at the end of the Epilog of each process handling with direct dim updates.

User avatar
qml
MVP
Posts: 1036
Joined: Mon Feb 01, 2010 1:01 pm
OLAP Product: TM1
Version: 10.2.2
Excel Version: 2007 - 2016
Location: London, UK, Europe

Re: Direct edit dimension collection has not been cleared before commit

Post by qml » Thu Jul 13, 2017 9:37 am

Gabor wrote:I've seen that error after moving to 10.2.2 FP7, but could get rid of the message by adding "DimensionUpdateDirect(DimName)" at the end of the Epilog of each process handling with direct dim updates.
Weird. I always do the DImensionUpdateDirect in Epilog after any Direct inserts, mostly because without that rules don't get attached to elements added in that way (one to look out for). Despite that I still see the same error as Lotsa.
Kamil Arendt

lotsaram
MVP
Posts: 2987
Joined: Fri Mar 13, 2009 11:14 am
OLAP Product: TM1, CX
Version: TM1 10.2.2 PA 2.0x
Excel Version: 2010 2013 365
Location: Switzerland

Re: Direct edit dimension collection has not been cleared before commit

Post by lotsaram » Thu Jul 13, 2017 2:22 pm

From own testing and confirmed from IBM support adding DimensionUpdateDirect to the Epilog does not make this error message go away.

What I still don't know is whether the error actually is an "error" or just something g that should be ignored.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.

Post Reply