TM1 - disabling logs doesn’t work

[MarioB]

Hi every one,

I looked for this topic on the forum but didn’t found out anything. Please apologize if you already answered something on this « bug »

We have disabled logs on a particular TI process through the good old instruction cellputs (no, cubeproperties, vcube, logging), but it doesn’t work.
During a test, The tm1 log file added 59 000 kbits after commit.
During this same test, We launched the same TI process after removing the instruction « logging :no , and tm1log file added exactly the same amount of kbits (59000)

How is that possible ?
(We run on planning analytics 2.0.5)

[ascheevel]

You're talking about the tm1s.log file and not the tm1server.log file right? Can you post your actual code for turning transaction logging off and confirm what tab of the TI process you've placed it?

[tomok]

cellputs (no, cubeproperties, vcube, logging)

Is this literally your code? It's not going to work because anything that is not a variable would need to have apostrophes and you have a wrong cube name.

Code: Select all

cellputs ('no', '}cubeproperties', vcube,  'logging');

[MarioB]

Thank you for your reply.

I’m talking about tm1s.log file yes . And my script is the good one (with apostrophe, as mentionned in Tomok’s message) and correct cube name, placed in prolog and epilog.

I just don’t understand why log file still increasing whereas I turned off within the TI process. Did you ever encountered this issue ?

We have a big TI process which transfer data from a cube to another with calculations, and this TI process result to a 60 gbits log file !

Appreciate your help a lot

[ascheevel]

Are you calling a ViewZeroOut in the prolog of your TI? If so, have you made sure that you're setting the logging to no BEFORE you call the zero out?

[tomok]

Any particular reason why you are not using the built-in CubeSetLogChanges function in your TI?

[MarioB]

Are you calling a ViewZeroOut in the prolog of your TI? If so, have you made sure that you're setting the logging to no BEFORE you call the zero out?

Oh thank you , i had a sub process with viewzeroout. Thank you very much !

[Wim Gielis]

Any particular reason why you are not using the built-in CubeSetLogChanges function in your TI?

Yes. Reducing locking, at least that's what I have always assumed the CellPutS does in favour of CubeSetLogChanges.