Hi
Am I correct in understanding that you have two processes running at the same time, both doing a SaveDataAll to write data to disk? If so, then as far as I am aware the standard IBM advice is not to do this. It is best to have SaveDataAll in a Chore that runs periodically where the process that runs the SaveDataAll is the only process in that Chore.
We have had huge problems with SaveDataAll. We do not run it during the day during busy month end periods, as in the past it has caused crashes. Your situation may be different but we typically have 100+ users all entering data and running processes..
Not flushing data to disk has its risks if the server crashes, but if running a SaveDataAll causes a crash then you are possibly even worse off.
Regards
Paul SImon
------------------------------
Paul Simon
------------------------------
Original Message:
Sent: Tue March 17, 2020 09:59 PM
From: mvp morgan
Subject: Massive No lock messages when saving data happens concurrently
I know it is warning but there are massive "No lock" info in the sever log when two saving processes running at the same time. Is there a way to suppress this?
13428 [1f43] WARN 2020-03-18 11:09:33.160 TM1.Lock Attempt to release lock on 0x00000191F23D1A68(0x00000191F23B9A10). No lock held by module c:\jenkins\j12\workspace\build-tm1_main-tm1server-win64-production\src\tm1server\prod\tm1_r7s\tm1serverimpl.cpp at Line 16703
13428 [1f43] WARN 2020-03-18 11:09:33.162 TM1.Lock Attempt to release lock on 0x00000191F23D1A68(0x00000191F23B9A10). No lock held by module c:\jenkins\j12\workspace\build-tm1_main-tm1server-win64-production\src\tm1server\prod\tm1_r7s\tm1serverimpl.cpp at Line 16703
1
------------------------------
mvp morgan
------------------------------
#PlanningAnalyticswithWatson