May 23, 2019 at 4:54 pm
Hello all,
I have an issue with my growing transaction log. When I query the log_reuse_wait_desc we found that it is pending for "replication".
I have both transactional replication and CDC enabled at the same time. It means that it is actually sharing the same log reader agent.
We are not sure which exactly the root cause (transaction replication / CDC) is preventing the Transaction Log from being reused.
When I did an DBCC Opentran(). It showed me the output like below.
May i know the name:ChangeTable below is referring to the CDC feature which is holding the Transaction Log?
Your input is much appreciated.
DBCC Opentran() Output as below:
SPID (server process ID): 91
UID (user ID) : -1
Name : changeTable
LSN : (2376409:3030764:1)
Start time : May 23 2019 11:56:18:587AM
SID : 0x01
Replicated Transaction Information:
Oldest distributed LSN : (2375825:1525424:187)
Oldest non-distributed LSN : (2375242:1587399:59)
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
May 23, 2019 at 8:54 pm
Check the replication, the easiest way will be adding tracer token if it will replicate to subscriber then replication is working, check also log reader agent for any errors.
CDC errors you can find in sys.dm_cdc_errors table.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply