TM1 Forum

Hello,

after moving to a knew windows server (Win 2016) i have a problem with one of the tm1 instances
If a run a a data load or dimension process, the service for this db stops:
"TM1.Transaction TM1TransactionLog::BasicInitialize: The transaction log was found and write-locked. Recovery possible after server load."
I never saw this message before - does anybody has an idea what's my problem is or should i call ibm?

I'm working with Planning Analytics 11.4.00000.21

Best regards,
orlando

Not entirely sure, but sounds like this *could be* related:

https://www-01.ibm.com/support/docview. ... wg21654717

bgregs wrote: ↑Mon Dec 10, 2018 12:21 pm Not entirely sure, but sounds like this *could be* related:

https://www-01.ibm.com/support/docview. ... wg21654717

thanks for your reply.

i saw that before. even shut down server, delete logfiles, start service does not help

Do you have a backup that was taken before the server migration you could test? This line:

The TM1 service may not have been shut down completely prior to copying the model

really sounds like it could be the cause. If you don't have a backup to test with, then calling IBM may be your best bet (unless somebody else on here has another idea).

I don't recall seeing that message before but we have had a few situations where instances that were running just fine on 10.2.2.x refused to load in 11.x and some others where the server did load but then crashed on each SaveDataAll. In these cases we found that the cause was "incomplete" file structure in the data directory which resulted in objects not registering on the server. Particularly
- }ElementAttributes cubes and dimensions where the root dimension .dim file didn't exist or was corrupted
- }vues folders for cubes no longer existing

After cleaning up the data directory the server was able to load and/or in the other case no more crash on save.

Might be worth trying before giving up hope.

Hi all,

i found the "problem".
It was a DimensionDestroy in one of my meta processes.

A metaprocess runs
Process 1: build a temp dimension
Process 2: Copy a part of the structure to another dimension
Process 3: Load the attributes

After the third process the metaprocess runs DimensionDestroy for the temp. dimension
Server Crashs.

Without the DimensionDestroy it rund fine.

It looks like that Win 2016 locks the Dim-File longer than Win 2012.
So in the future i do the housekeeping later.

Thanks for your help!

Best regards,

orlando