Overlapping DB.lg file messages

Posted by Paul Koufalis on 22-May-2018 08:14

OE 11.5.1 on Windows.

Anyone ever see this kind of thing in a db.lg file? It looks like one process wrote an entry in the middle of another. Note that this is all one line:

[2018/05/01@19:15:46.934-0400] P-6692       T-10928 I SRV     3: (453)   Logout by sqluser on [2018[2018/05/01@19:15:46.934-0400] P-6812       T-248   I SQLSRV2 2: (-----) Logout by user 108.

Here is the line broken up so that you can more easily see the problem:

[2018/05/01@19:15:46.934-0400] P-6692       T-10928 I SRV     3: (453)   Logout by sqluser on
[2018
[2018/05/01@19:15:46.934-0400] P-6812       T-248   I SQLSRV2 2: (-----) Logout by user 108.

Another example below. Note the extra 2018 at the beginning.

[2018[2018/05/06@00:15:51.526-0400] P-6812 T-7448 I SQLSRV2 2: (-----) Logout by user 110.

 

All Replies

Posted by George Potemkin on 22-May-2018 08:19

Yes. With 10.2B on AIX, for example. It's a rare event but sometimes it's still happened.

Posted by Paul Koufalis on 22-May-2018 08:45

I have 25 occurrences from May 1 - 20  but none for the 2 months before that or the week since. Nothing happened on that day. No new process was spawned or anything.

Bizarre.

Posted by George Potemkin on 22-May-2018 08:54

In the case of our customers the message overlapping took place mostly during shutdowns when a lot of the messages /per sec/ were writing to a database log. Your examples look similar.

Posted by gus bjorklund on 22-May-2018 12:08

this are caused by bugs in the code that writes to the database log file. If you write messages with a single write() system call, then the messages won’t overlap.

Posted by ChUIMonster on 23-May-2018 08:57

I've seen similar issues in the past where the *application* was inserting stuff into the .lg file via 4gl PUT statements (pre log-manager).

Paul's issue seems to be a case where Progress executables are overwriting each other?

This thread is closed