dbcc opentran is not helping me on "waiting for backend connection"

What else could be causing this?
I keep getting waiting on backend connection on a lot of my log readers
connected to this one publisher. The publisher has no blocking and was
just rebooted last night. Everything on the publisher is working fine.
however. I get "waiting for backend connection" and "waiting for log
backup" a lot on the errors of the log reader.
I have also had to had to put the -readbatchsize level to a (1) on all
of these log readers connected to this publisher. Once i do this, they
at least start going 1 transaction at a time. These are not like huge
transactions.
dbcc opentran shows
Transaction information for database 'pet01'.
Replicated Transaction Information:
Oldest distributed LSN : (25212765:36114:75)
Oldest non-distributed LSN : (25212765:36145:1)
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
Any help would be appreciated.
-comb
Basically this is telling you that the log reader has transactions to write
to the distribution database.
I think your problem is with depleted buffers on SQL Server. You need to
reboot the box. You may be able to get away with merly stopping and starting
SQL Server.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"combfilter" <asdf@.adsf.com> wrote in message
news:MPG.1dd16198660765d99896c2@.news.newsreader.co m...
> What else could be causing this?
> I keep getting waiting on backend connection on a lot of my log readers
> connected to this one publisher. The publisher has no blocking and was
> just rebooted last night. Everything on the publisher is working fine.
> however. I get "waiting for backend connection" and "waiting for log
> backup" a lot on the errors of the log reader.
> I have also had to had to put the -readbatchsize level to a (1) on all
> of these log readers connected to this publisher. Once i do this, they
> at least start going 1 transaction at a time. These are not like huge
> transactions.
> dbcc opentran shows
> Transaction information for database 'pet01'.
> Replicated Transaction Information:
> Oldest distributed LSN : (25212765:36114:75)
> Oldest non-distributed LSN : (25212765:36145:1)
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> Any help would be appreciated.
> -comb
|||In article <ehBTGvw3FHA.1276@.TK2MSFTNGP09.phx.gbl>,
hilary.cotter@.gmail.com says...
> Basically this is telling you that the log reader has transactions to write
> to the distribution database.
> I think your problem is with depleted buffers on SQL Server. You need to
> reboot the box. You may be able to get away with merly stopping and starting
> SQL Server.
>
We rebooted it last night. It's part of a cluster, and we moved the
instance over and rebooted the box. What else should I check Hilary or
Paul?
tia.
-comb

Dbcc Checkdb

Hi,

I don't succeed to do a "dbcc checkdb (BASE)".

I use SQL SERVER 8.00.760 (SP3)

1) Server properties :
NONE default connection option is set

2) Database MASTER and others :
The property "Quoted Identifiers" is NOT set

The result of "dbcc checkdb (BASE)" is always the same :
Error message 1934 "DBCC failed because the following SET options have incorrect settings : 'ANSI_NULLS., QUOTED_IDENTIFIER, ARITHABORT'.

and that, either in Query Analyze or via OSQL command.

Even what is shown in article Q301292 of Microsoft doesn't works correctly ...

Thanks a lot for anyone who could help me to succeed.Can you post your set options - also, does this happen with checkdb ?|||1) OSQL - SET OPTIONS ==> See file "OSQL_DBCC_..."

dbcc checkdb (BASE) is correctly working if I enter previously

set quoted_identifier on
go
set arithabort on
go

2) QUERY ANALYZER - SET OPTIONS :

Set Option Value
----------- --------------
textsize 64512
language Franais
dateformat dmy
datefirst 1
quoted_identifier SET
arithabort SET
ansi_null_dflt_on SET
ansi_defaults SET
ansi_warnings SET
ansi_padding SET
ansi_nulls SET
concat_null_yields_null SET

(12 ligne(s) affecte(s))

dbcc checkdb (BASE) is correctly working WITHOUT any change

So, which is the best way in order "dbcc checkdb" runs OK in either case ?|||So are you saying that it is functioning properly now ? Did you make any modifications using sp_dboption ?