February 28, 2020 at 11:11 am
We're playing with a new server as part of a proof of concept and Its a High availability group.. but we are getting a lot of junk in the event log
they look like this
UpdateHadronTruncationLsn(15) (force=0): Primary: 0:0:0 Secondary: 878:49274:1 Partial Quorum : 0:0:0 Aggregation: 878:49274:1 Persistent: 878:49274:1
Does anyone know how to turn this off? it really makes it hard to find any other issues when there are thousands of these messages (that give us no practical value)
MVDBA
February 28, 2020 at 3:02 pm
When you find out, let me know too.
Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
March 16, 2020 at 1:10 pm
I got the same spamming msgs. UpdateHadronTruncationLsn would be a problem?
Microsoft SQL Server 2019 (RTM-CU1) (KB4527376) - 15.0.4003.23 (X64) Dec 6 2019 14:53:33 Copyright (C) 2019 Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: ) (Hypervisor)
April 15, 2020 at 9:41 am
I get the message "UpdateHadronTruncationLsn(8) (force=0): Primary: 0:0:0 Secondary: 37:336:1 Partial Quorum : 0:0:0 Aggregation: 37:336:1 Persistent: 37:336:1" exactly each 30 minutes.
I do have some other AON installations which work fine and do not have this spam. One of the differences is that the have no DTC per database. I want to investigate, if this might make the difference
April 16, 2020 at 2:51 pm
I did a fresh installation of SQL 2016 SP2 with 2 Cluster Nodes and 12 databases in the AG. It all worked fine without any "UpdateHadronTruncationLsn" message until I did the upgrade to SQL Server 2019 CU4.
I don't know if it causes/Shows any problems
May 15, 2020 at 8:03 am
Hi
I'm getting the same messages in my logfile, .
Date 15/05/2020 08:58:26
Log SQL Server (Current - 15/05/2020 08:39:00)
Source spid290s
Message
UpdateHadronTruncationLsn(14) (force=0): Primary: 0:0:0 Secondary: 13707:432:1 Partial Quorum : 0:0:0 Aggregation: 13707:432:1 Persistent: 13707:64:1
May 19, 2020 at 3:43 pm
Hi
Has anyone found a cause or fix for this, or even is it something to worry about.
I just upgrade and 2014 AlwaysOn to 2019 CU4 and get this message logged periodically through the day.
June 2, 2020 at 5:58 pm
In my case, 2019 CU1 has the same behavior as well. No idea what SQL Server is trying to tell me by spitting this information out to error log.
June 2, 2020 at 9:26 pm
We logged call with MS but nothing confirmed. Just told it’s just part of hardening process. If not causing any issues then ignore. We’ve asked for case to be escalated.
June 3, 2020 at 11:47 am
I have a case ongoing and MS said:
....
Thank you for your patience, we have an update on this case. Our Product team is going to release a hotfix in near future which will produce a fix such that only if TF3605 is enabled, this message will show up in the errorlog.
.....
I got this information on 30th of may.
Ignoring is a nice hint, but makes it hard to read the error log.
June 18, 2020 at 12:23 pm
MS support told me, the fix will be released in SQL Server 2019 CU6, only if you enable a support flag, you'll get the log messages
January 24, 2021 at 9:16 am
I setup a new installation. Never set any support flags and the message is there. Microsoft, is the one that set those support flags. Also, which support flag # is it onlt TF3605?
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply