TM1 Forum

Hi All,

We use PA and looking for transaction log just like we did before in the TM1.

It seems that now the transaction log only reads logs from closed log files and not from the one that is open right now.

I can see transactions logs before today but not from today (only tomorrow I'll see today's log transaction)

How can I read transactions that just were done now?
What was changed in my configurations?

Thanks

Hello,

I'm a little confused by...

It seems that now the transaction log only reads logs from closed log files and not from the one that is open right now.

Transaction log (tm1s) is always locked by the model unless serialized to the disk by either SaveDataAll or CubeSaveData. I'd guess you have a SaveDataAll Chores that runs overnight ?

As far as I know and see in PA, none of this behavior has changed

Thanks

Evgeny

Thanks EvgenyT.

I was able to read transaction log even of the current log in the TM1 10.2.2.

Now on PA it's not possible

Roei

How are you trying to read the transaction log? Viewing the transaction log in architect should be the same in PA2.0.x as 10.2.

I'm using Perspectives in both

In my experience, TM1S is always locked and you cannot read it.
Viewing the transaction log from within TM1 will show transactions but only those written after serialization/save data.
Cannot see how this would be different unless you have a chore saving data periodically.

TM1s file will be locked but right-clicking the server -> View Transaction Log should still query recent transactions. I just confirmed with architect/perspectives that changes I made that were not serialized to disk appeared in the query results. I did have to click "logtime" to switch the sort from ascending to descending as the default sort is ascending.

roei61 wrote: ↑Wed Jan 22, 2020 4:20 pm Thanks EvgenyT.

I was able to read transaction log even of the current log in the TM1 10.2.2.

Now on PA it's not possible

Roei

Please review what I said above, tm1s log is always locked (and it has been like that for the last 10 years that I have been worked with tm1) unless you serialize it to the disk with Save Data functions (tm1s.log will be saved as tm1s | datetimestamp.log). Have you tried that?

Alternatively, as others pointed out, you can query it via View Transaction Log in Architect / Perspectives (although might be a bit slow if there are heaps of records)

I really don't see any issues here

Thanks

Evgeny