Page 1 of 1
TM1.Audit.PostProcessor Error
Posted: Tue Jun 28, 2011 3:43 pm
by mattgoff
Anyone seen errors like this? I'm also opening a ticket with Cognos, but I'm curious to hear if others have seen it as it's a new one to me. I do (obviously) have the audit log turned on with a 60 min writeback timer, but it's been on for a long time and we just started seeing these errors. No changes made to TM1 lately, although I did just have to have IT tune AV settings as there were locking problems on ASCIIOutput writes.
Code: Select all
2011-06-27 15:15:29.581 TM1.Audit.PostProcessor Error copying Scenario.dim
2011-06-27 16:15:29.489 TM1.Audit.PostProcessor Error copying Cost_Center.dim
2011-06-27 18:15:29.304 TM1.Audit.PostProcessor Error copying Scenario.dim
2011-06-28 09:15:29.494 TM1.Audit.PostProcessor Error copying Scenario.dim
I bounced the server too-- it's been a month or so, so good to clean out the cobwebs....
Matt
Re: TM1.Audit.PostProcessor Error
Posted: Wed Jun 29, 2011 4:46 pm
by Mike Cowie
Matt:
Looks like IBM's already posted an explanation?
https://www-304.ibm.com/support/docview ... s=swgimgmt
Apparently you just work at too high a rate of speed... multiple dimension updates in under a minute!
Regards,
Mike
Re: TM1.Audit.PostProcessor Error
Posted: Wed Jun 29, 2011 4:58 pm
by mattgoff
From support:
The reason for the mesages is that you will have had more than one process making a change to the same dimension within one minute.
What is happening is that after the dimension change process finishes an audit process runs to record these changes. This audit process wakes up every minute to process all the auditing for the preceding minute. It sees the first dimension change and writes a file Scenario.dim.<timestamp> it then sees the second change to the same dimension and again tries to write another file Scenario.dim.<timestamp>. If when it tries to write the second file, for the second dimension change, the timestamp is the same as the first it will fail to write it as it already exists. The issue is that the timestamp is only calculated to the second.
The dimension change itself is not affected only the audit trail is affected.
The recommended way to avoid this happening is to try and separate dimension changes that change the same dimension by more than a minute.
Classic.
Matt
Re: TM1.Audit.PostProcessor Error
Posted: Wed Jun 29, 2011 5:06 pm
by mattgoff
Mike Cowie wrote:Apparently you just work at too high a rate of speed... multiple dimension updates in under a minute!
I know! I should really plan all of my TI scripts to work as if they were a human hand-calculating the data to accommodate logging. WTF.
Matt