Problem with Integrity Check

I have a db on one server that publishes to a subscriber on another server
(which acts as distributor as well). Both are running SQLS2K. I have
maintenance plans in place on both dbs and each does an integrity check. The
check on the publisher runs fine. The check on the subscriber fails and the
log file states:
Starting maintenance plan 'Loc 052 S2 DB Maintenance Plan' on 5/10/2005
9:25:43 AM
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070: [Microsoft][ODBC SQL
Server Driver][SQL Server]Database state cannot be changed while other users
are using the database 'Unifirst052'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
[1] Database Unifirst052: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC SQL
Server Driver][SQL Server]Repair statement not processed. Database needs to
be in single user mode.
The following errors were found:
[Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
processed. Database needs to be in single user mode.
************
I looked at the properties of both dbs and don't see anything different. I
have this same setup on other pairs of servers in different locations and I
don't have a problem with integrity checks on either the publisher or
subscriber. There are anywhere from 3 to 7 users on each of those systems.
What am I missing on the subscriber of this current system?
Remove the "repair minor problems" from the maint plan. Repairing is *not* something you want to be
done silently and automatically in unlikely case of a corruption. You want to do root cause analysis
etc.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Roger Denison" <RogerDenison@.discussions.microsoft.com> wrote in message
news:A7EFDE92-ECB4-4E27-AF90-41BF541D2DE8@.microsoft.com...
>I have a db on one server that publishes to a subscriber on another server
> (which acts as distributor as well). Both are running SQLS2K. I have
> maintenance plans in place on both dbs and each does an integrity check. The
> check on the publisher runs fine. The check on the subscriber fails and the
> log file states:
> Starting maintenance plan 'Loc 052 S2 DB Maintenance Plan' on 5/10/2005
> 9:25:43 AM
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Database state cannot be changed while other users
> are using the database 'Unifirst052'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
> failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
> [1] Database Unifirst052: Check Data and Index Linkage...
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Repair statement not processed. Database needs to
> be in single user mode.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statement not
> processed. Database needs to be in single user mode.
> ************
> I looked at the properties of both dbs and don't see anything different. I
> have this same setup on other pairs of servers in different locations and I
> don't have a problem with integrity checks on either the publisher or
> subscriber. There are anywhere from 3 to 7 users on each of those systems.
> What am I missing on the subscriber of this current system?
|||That was it, thanks. Don't know how that got checked but I cleared it and
everything is good.
"Tibor Karaszi" wrote:

> Remove the "repair minor problems" from the maint plan. Repairing is *not* something you want to be
> done silently and automatically in unlikely case of a corruption. You want to do root cause analysis
> etc.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Roger Denison" <RogerDenison@.discussions.microsoft.com> wrote in message
> news:A7EFDE92-ECB4-4E27-AF90-41BF541D2DE8@.microsoft.com...
>
>