Change Tracking auto cleanup error 22123
Just upgraded to 2016 SP2 (13.0.5026.0) and receiving frequent error messages logged from change tracking auto cleanup: Error 22123, severity 16, state 1 Change Tracking autocleanup is blocked on side table of "<>". If the failure persists, check if the table "<>" is blocked by any process . Routinely for different tables, not repeatedly from the same table.
I suspect this was added as part of the changes to auto cleanup released in SP2, and is raised when a table is blocked and marked for retry. Can anyone please confirm this?
Additionally, this seems to me like more of an informational status than a user correctable error, doesn't it? I would not think this would be an issue requiring intervention unless it was happening repeatedly and often on the same table.
Finally, according to sys.messages 22123 is NOT set to be event_logged... but it IS logging to the even log each time.
Enabling trace flag 8293 doesn't eliminate the message, using SQL 2016 SP2
Fux Molder commented
Same issue on "Microsoft SQL Server 2016 (SP2-GDR) (KB4293802) - 13.0.5081.1 (X64) Jul 20 2018 22:12:40 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor) "
Same problem with 2014 SP3 also!!
Sebastian Habeker commented
It has been fixed in SQL 2016 SP2 CU3 as well: https://support.microsoft.com/en-us/help/4456883
Surprised it has been a problem since May 2018 and not been addressed by Microsoft :(
Upgraded one of our production servers to SQL 2016 SP2 + KB 4458621 (13.0.5201.2), and the error log is flooded with this. Can this be resolved ASAP please?
Same problem with 2014 SP3, no CU yet?
Alex Bransky commented
This is happening with 2014 SP3 and is quite annoying.
Confirmed fixed in 2017 CU10.
It has not been fixed in 2016 yet.
Does anyone know if Microsoft has addressed this issue yet - my log files are flooded.
Seems to be fixed in SQL Server 2017 CU10.
Danielle Paquette-Harvey commented
I've got this error everywhere in my log in SQL 2016 SP2 CU2. Very annoying and I cannot see any real error because my log is so full of these errors.
Shudley Adams commented
Upgraded one of our production servers to SQL 2016 SP2 On Friday, and the error log is riddled with this "error". Our other production servers are on SQL 2016 SP1 CU7 and we do not have this "issue". Can this be attended to ASAP. It is quite annoying having to troll through the logs for actual errors when the logs are being flooded with this "error"
Lars Utterstrom commented
An no change after also upgrading to CU2 from previous SP2 + CU1 on SQL Server 2016. Still the SQL Errorlog is flooded with this error message.
Murat YALLIKURT commented
After install SP2 + CU1 on SQL Server 2016, I have same issue. Please release a new update to fix that problem.
I am experiencing this in SQL Server 2017 CU7. I sometimes have as many as 100,000+ entries in the errrolog per hour.
Messages are often 10 milliseconds apart.
It is 100% recoverable and ignorable.
At least give us a trace flag to disable logging, or configure the timeout. I suspect the timeout is pretty short due to 10 ms between log entries and my monitoring often not reporting blocking beyond 30 seconds.
I have this with SQL 2016 SP2 CU1 as well. Is it indeed informational?
Jules Ebben commented
I've got the same error message logged in the eventviewer also with different tables after the update to SQL Server 2016 SP2.