backups off distributed database

  • I have two SQL servers which are in merge replication mode. I made a Maintence plan,for making backup files etc. But these don't run. They give these errors

    Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.382

    Copyright (C) Microsoft Corporation, 1995 - 1998

    Logged on to SQL Server 'OLNSQL03' as 'sa' (non-trusted)

    Starting maintenance plan 'DB Maintenance SQL03' on 2002-10-17 08:52:25

    [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 'APPL_WTP'

    [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement failed.

    [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.

    [1] Database APPL_WTP: 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.

    ** Execution Time: 0 hrs, 0 mins, 1 secs **

    [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5058: [Microsoft][ODBC SQL Server Driver][SQL Server]Option 'SINGLE_USER' cannot be set in database 'MASTER'.

    [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.

    [2] Database master: 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.

    ** Execution Time: 0 hrs, 0 mins, 1 secs **

    [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 'WWALMDB'

    [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement failed.

    [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.

    [3] Database WWALMDB: 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.

    ** Execution Time: 0 hrs, 0 mins, 1 secs **

    [4] Database APPL_WTP: Database Backup...

    The backup was not performed since data verification errors were found.

    [5] Database master: Database Backup... The backup was not performed since data verification errors were found.

    [6] Database WWALMDB: Database Backup...

    The backup was not performed since data verification errors were found.

    Deleting old text reports... 0 file(s) deleted.

    End of maintenance plan 'DB Maintenance SQL03' on 2002-10-17 08:52:26

    SQLMAINT.EXE Process Exit Code: 1 (Failed)

  • Hello Andy,

    No we are running SQL 2000 SP2 with the hotfix.

    quote:


    SQL7?

    Andy

    http://www.sqlservercentral.com/columnists/awarren/


  • I think that makes sense - if you check the repair errors option the db has to go into single user mode. To get into single user mode you have to kill all connections, so you'd have to stop all your log reader and distribution agents first since the maintenance plan won't do it for you. The alternative is to not have it repair errors but just notify you, then you can manually handle killing the connections and running the repair, either using DBCC directly or by modifying the plan and re-running.

    Andy

    http://www.sqlservercentral.com/columnists/awarren/

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply