Chuck,

Well, the truncation of transaction log is the only option for this situation (which I can think off at that time) because log reader is not reading the these transactions. I did restarted the log reader but it's not replicating the data. No errors were logged in either SQL ErrorLog or Replication Monitor.

I did some post resolution investigation on our test environment by restoring the backups of production but unable to came to conclusion why this happened.

If you know any betterway of resolving this issue then please share 🙂

FYI - I fully understand the consequences of log truncation and that is why I took the full backup of the database prior to following the process.