Cannot Truncate Transaction Log!

My Transaction Log on a production database has grown to 5 GB. And
all but 118 MB is used in that log. DBCC Opentran shows the
following:
Replicated Transaction Information:
Oldest distributed LSN : (10576:2240:4)
Oldest non-distributed LSN : (0:0:0)
Replication is not set up on that server! There are no agents running
on it, there is no Distribution database. But it looks like something
is flagged for replication. I know a very large DTS was executed on
the database and maybe something got mixed up, and now the database
thinks it has to replicate this giant transaction.
I am shipping the logs of this database from MI to VA, and I really
don't want to break log shipping by fixing this problem. I may have
to anyway. How can I get this transaction to get cleaned out' I
can't execute sp_repldone, because no replication agents are running.
Help!!!!!!Try these links :-
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
HTH
Ryan Waight, MCDBA, MCSE
"Laura Jones" <jonesl@.ofllc.com> wrote in message
news:978604d4.0403040636.446e8010@.posting.google.com...
> My Transaction Log on a production database has grown to 5 GB. And
> all but 118 MB is used in that log. DBCC Opentran shows the
> following:
> Replicated Transaction Information:
> Oldest distributed LSN : (10576:2240:4)
> Oldest non-distributed LSN : (0:0:0)
>
> Replication is not set up on that server! There are no agents running
> on it, there is no Distribution database. But it looks like something
> is flagged for replication. I know a very large DTS was executed on
> the database and maybe something got mixed up, and now the database
> thinks it has to replicate this giant transaction.
> I am shipping the logs of this database from MI to VA, and I really
> don't want to break log shipping by fixing this problem. I may have
> to anyway. How can I get this transaction to get cleaned out' I
> can't execute sp_repldone, because no replication agents are running.
> Help!!!!!!