October 18, 2019 at 4:31 pm
In SQL Server 2016 SP2, we had a transaction log that had a truncation wait for OLDEST_PAGE indefinitely, until the disk filled up. We ran a CHECKPOINT manually and it was able to truncate. Some documentation stated this was due to indirect checkpoints, so we changed the Target Recovery Time from 60 to 0 and it no longer waits for OLDEST_PAGE, and we anticipate the issue will be resolved going forward.
This database is in an availability group scenario with two asynchronous replicas (three node cluster).
The question is, does this sound like a SQL Server bug to you related to indirect checkpoints and availability replicas? Or is there something misconfigured on our system?
October 19, 2019 at 5:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply