Hi Mark,
Thanks for your valuable reply.
Dump transaction to file or dump transaction with truncate_only is not working whereas dump tran witth no_log is working to clear the log.
Yes i do have replication secondary truncation point enables on rep server and i can see the entry for it in syslogshold table.
1> dbcc gettrunc
2> go
secondary trunc page secondary trunc state dbrepstat generation id database id database name ltl version
-------------------- --------------------- --------- ------------- ----------- --------------------- -------- -----------
1637791 0 36 0 4 ics 750
I can confirm below things.
1.PDB rep agent is working
2.PDB rep agent is able to connect to rep server.
3.Rep agent is able to pass the transaction to the rep server fine, stable queue is not filled up, minimal rows only.
4.Below is the status of dbcc gettrunc command for RDB database and it shows that Sec. truncation point is configured for the RDB database but it shows states value "0" which means it is disabled currently.
1> select * from syslogshold
2> go
dbid reserved spid page xactid masterxactid starttime name xloid
------ ----------- ------ ----------- -------------- -------------- ------------------------------- ------------------------------------------------------------------- -----------
5 0 0 36790586 0x000000000000 0x000000000000 May 13 2016 8:37PM $replication_truncation_point 0
4 0 0 3448027 0x000000000000 0x000000000000 May 14 2016 1:16AM $replication_truncation_point 0
(2 rows affected)
Kindly review above mentioned details and help me in next course of action.
Thanks and Regards,
Swapnil