Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1410
  • Last Modified:

Error in Satabase Maintenance plan

The maintenance plan for daily back up failed.
I have SQL 2000 on Windows Server 2003.
This is the report:

Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server 'M2MERP' as 'lmc\sqladmin' (trusted)
Starting maintenance plan 'DAILY_MASTER_INTEGRITY' on 4/30/2004 4:00:00 AM
[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.
[1] 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 **

[2] Database model: Check Data and Index Linkage...

    ** 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 'msdb'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
[3] Database msdb: 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 **

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

End of maintenance plan 'DAILY_MASTER_INTEGRITY' on 4/30/2004 4:00:01 AM
SQLMAINT.EXE Process Exit Code: 1 (Failed)

How do I correct this error?

Thank you,

0
cosio
Asked:
cosio
  • 3
  • 3
  • 2
1 Solution
 
Anthony PerkinsCommented:
Do not check the box that reads "Attempt to repair any minor problems"
0
 
cosioAuthor Commented:
What are the consequences of checking the box? I mean other that cousing this error to happen, why does the plan fails? Can anyone give me a brief explanation?
I appreciate
0
 
Anthony PerkinsCommented:
The consequences of checking the box is that the database needs to go into Single User mode.  If this is a multiuser database (and 99% are) that will mean it will fail if any user is currently active.  Worse still, even if there are not (and that is a risk in itself) there is a chance that it will remain in Single User mode.  See here:
FIX: Database Remains in Single User Mode with the Database Maintenance Plan Option "Repair Any Minor Problems"
http://support.microsoft.com/default.aspx?scid=kb;en-us;259551

Again, not a good thing.
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
arbertCommented:
agree with acperkins totally.....Personally, I think it's a bad idea to let SQL Server attempt any repairs anyway until you have a report and know what the damage is.  Sometimes the repair makes things worse....
0
 
cosioAuthor Commented:
A MSSQL "expert" told me that I need to check "Attempt to repair any minor problems" when doing backups.
0
 
arbertCommented:
So why the question here if you already have an "expert"?
0
 
cosioAuthor Commented:
What I have been told is to check "attempt to repai any minor problems in the productions databases maintenance plan.
The person who installed SQL in this place suppose to be an "expert."

Obviouly I like to heart other people with experience in SQL. So far what you guy are telling me makes a lot more sense that what I  have been told.

For the record, it is not my "expert", this person is a consultant that this place hired before me. I am new here taking care of the company databases. I post the question because I have some doubts about the way the consultant "expert" implements some things around here.

thank you
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now