Integrated Security: maintenance

Showing posts with label maintenance. Show all posts

Wednesday, March 21, 2012

Interesting Maintenance Plan Problem

SQL Server 2005 - I created a maintenance plan to backup several
databases. The steps in the maintenance plan are very simple, first -
check database integrity, next reindex or reorganize the indexes, backup
the databases and finally remove backup files.
I set the schedule to begin at 12:05am and tested the process by
manually running (right-click on the job and start at step). The
process ran successfully, all steps.
That night, the process started at 12:05 and failed after the second
step with no indication why the process failed. I ran it manually and
it completed successfully. The following night the process failed after
the first step completed, again with no indication why the process
failed. Again, I ran the process manually and it completed all steps
successfully.
I modified the schedule to run at 12:30am instead - and all steps
completed successfully.
Does anybody have any ideas why the process would fail when scheduled to
run at 12:05, but not fail when scheduled to run at 12:30?
JeffDid something have the database in use?
Jeffrey Williams wrote:
> SQL Server 2005 - I created a maintenance plan to backup several
> databases. The steps in the maintenance plan are very simple, first -
> check database integrity, next reindex or reorganize the indexes, backup
> the databases and finally remove backup files.
> I set the schedule to begin at 12:05am and tested the process by
> manually running (right-click on the job and start at step). The
> process ran successfully, all steps.
> That night, the process started at 12:05 and failed after the second
> step with no indication why the process failed. I ran it manually and
> it completed successfully. The following night the process failed after
> the first step completed, again with no indication why the process
> failed. Again, I ran the process manually and it completed all steps
> successfully.
> I modified the schedule to run at 12:30am instead - and all steps
> completed successfully.
> Does anybody have any ideas why the process would fail when scheduled to
> run at 12:05, but not fail when scheduled to run at 12:30?
> Jeff
--
Brett I. Holcomb
brettholcomb@.R777bellsouth.net
Remove R777 to email|||Jeffrey
Have you looked at ERROR.LOG ? Any entries?
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:OeWJCO$nHHA.208@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005 - I created a maintenance plan to backup several
> databases. The steps in the maintenance plan are very simple, first -
> check database integrity, next reindex or reorganize the indexes, backup
> the databases and finally remove backup files.
> I set the schedule to begin at 12:05am and tested the process by manually
> running (right-click on the job and start at step). The process ran
> successfully, all steps.
> That night, the process started at 12:05 and failed after the second step
> with no indication why the process failed. I ran it manually and it
> completed successfully. The following night the process failed after the
> first step completed, again with no indication why the process failed.
> Again, I ran the process manually and it completed all steps successfully.
> I modified the schedule to run at 12:30am instead - and all steps
> completed successfully.
> Does anybody have any ideas why the process would fail when scheduled to
> run at 12:05, but not fail when scheduled to run at 12:30?
> Jeff|||Uri,
I looked in every log I could find - no errors, just the job stopped,
reporting a failure.
Jeff
Uri Dimant wrote:
> Jeffrey
> Have you looked at ERROR.LOG ? Any entries?
>
>
> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
> news:OeWJCO$nHHA.208@.TK2MSFTNGP05.phx.gbl...
>> SQL Server 2005 - I created a maintenance plan to backup several
>> databases. The steps in the maintenance plan are very simple, first -
>> check database integrity, next reindex or reorganize the indexes, backup
>> the databases and finally remove backup files.
>> I set the schedule to begin at 12:05am and tested the process by manually
>> running (right-click on the job and start at step). The process ran
>> successfully, all steps.
>> That night, the process started at 12:05 and failed after the second step
>> with no indication why the process failed. I ran it manually and it
>> completed successfully. The following night the process failed after the
>> first step completed, again with no indication why the process failed.
>> Again, I ran the process manually and it completed all steps successfully.
>> I modified the schedule to run at 12:30am instead - and all steps
>> completed successfully.
>> Does anybody have any ideas why the process would fail when scheduled to
>> run at 12:05, but not fail when scheduled to run at 12:30?
>> Jeff
>
>|||Brett,
There are no other scheduled jobs at that time, except for the
transaction log files that run every 15 minutes and take less than a
minute to run at that time (no users on the system at midnight).
Jeff
Brett I. Holcomb wrote:
> Did something have the database in use?
>
> Jeffrey Williams wrote:
>> SQL Server 2005 - I created a maintenance plan to backup several
>> databases. The steps in the maintenance plan are very simple, first
>> - check database integrity, next reindex or reorganize the indexes,
>> backup the databases and finally remove backup files.
>> I set the schedule to begin at 12:05am and tested the process by
>> manually running (right-click on the job and start at step). The
>> process ran successfully, all steps.
>> That night, the process started at 12:05 and failed after the second
>> step with no indication why the process failed. I ran it manually
>> and it completed successfully. The following night the process
>> failed after the first step completed, again with no indication why
>> the process failed. Again, I ran the process manually and it
>> completed all steps successfully.
>> I modified the schedule to run at 12:30am instead - and all steps
>> completed successfully.
>> Does anybody have any ideas why the process would fail when scheduled
>> to run at 12:05, but not fail when scheduled to run at 12:30?
>> Jeff
>|||How about the report file for the maint plan? Anything there?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:4659B188.5000608@.verizon.net...
> Uri,
> I looked in every log I could find - no errors, just the job stopped, reporting a failure.
> Jeff
> Uri Dimant wrote:
>> Jeffrey
>> Have you looked at ERROR.LOG ? Any entries?
>>
>>
>> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
>> news:OeWJCO$nHHA.208@.TK2MSFTNGP05.phx.gbl...
>> SQL Server 2005 - I created a maintenance plan to backup several databases. The steps in the
>> maintenance plan are very simple, first - check database integrity, next reindex or reorganize
>> the indexes, backup the databases and finally remove backup files.
>> I set the schedule to begin at 12:05am and tested the process by manually running (right-click
>> on the job and start at step). The process ran successfully, all steps.
>> That night, the process started at 12:05 and failed after the second step with no indication why
>> the process failed. I ran it manually and it completed successfully. The following night the
>> process failed after the first step completed, again with no indication why the process failed.
>> Again, I ran the process manually and it completed all steps successfully.
>> I modified the schedule to run at 12:30am instead - and all steps completed successfully.
>> Does anybody have any ideas why the process would fail when scheduled to run at 12:05, but not
>> fail when scheduled to run at 12:30?
>> Jeff
>>|||Tibor Karaszi wrote:
> How about the report file for the maint plan? Anything there?
>
Nothing there either - the job just stops. I even reviewed the default
trace file and did not find anything there.
I can schedule the process at 12:30am and leave it there, but I was
hoping somebody else had seen something like this. I will keep
researching to see if I can find anything.
Thanks,
Jeffsql

Friday, March 9, 2012

Integrity job error

Hi folks,

I created a job to check the integrity of my databases every week using SQL Server Maintenance Plan Wizard.
The job is failing every time...
For tb_basico database it works fine, but with the other one (tb_cep) it doesn't work...

Does someone have an idea to solve this problem?

The message is:

[1] Database tb_basico: Check Data and Index Linkage...

** Execution Time: 0 hrs, 0 mins, 11 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 'tb_cep'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
[2] Database tb_cep: 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 **The problem is that other users are in the database while you are attempting to run the job created by the wizard. The wizard created job needs exclusive use of the database to complete the tasks you've asked it to do.

If you want to continue to run the wizard task, then I'd do an ALTER DATABASE mydb SET RESTRICTED_USER WITH ROLLBACK IMMEDIATE (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_aa-az_4e5h.asp), then run the job created by the wizard. After the job completes, you can ALTER DATABASE mydb SET MULTI_USER to allow the users back into the database.

-PatP

Integrity checks job failed

Hello, I had a DB Maintenance plan, the schedule is every day, but today I found teh 'Integrity checks job is failed". What is that mean? How to check this. Thanks.You need to run DBCC CHECKDB and see if one of your databases fail the check. Maintenance plans are useful, unless you want to troubleshoot of course.|||I found one database failed, I found one user didn't exit the database last night, is that will affect the database backup and integrity check? Another thing, what is integrity check means? How to trouble shoot? Thank you very much! I am a new in sql server.|||Oh my...you have a lot to learn. :) What was the error on the database that failed?|||I know i need to learn, can you tell me which book is good for me to learn? I need to learn quickly, I found the error for the job history, that :

Executed as user: DOM\ServerAdmin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Is that help you to figure out?|||http://www.dbforums.com/t812439.html

Gotta love microsoft. Looks like you have a classic generic error message. Could mean "disk is full", or "login failed" or almost anything. Kind of like the engine light in your car. I would start with running

DBCC Checkdb with no_infomsgs

on all of your databases to see if any of them have suddenly become corrupt. It is unlikely, but it is something you want to know about immediately. The user in the database could be the cause, but I can not say that for certain. Good luck.|||http://www.dbforums.com/t812439.html

Gotta love microsoft. Looks like you have a classic generic error message. Could mean "disk is full", or "login failed" or almost anything. Kind of like the engine light in your car. I would start with running

DBCC Checkdb with no_infomsgs

on all of your databases to see if any of them have suddenly become corrupt. It is unlikely, but it is something you want to know about immediately. The user in the database could be the cause, but I can not say that for certain. Good luck.

Hey, Listen...I'm alway one to give M$ a shot...

They all do it...

You can NEVER believe an Error Message

You always have to look outside the box...

DAMN, did I just say that?|||I didn't mean the error that the stupid maintenance plan gave you:

Executed as user: DOM\ServerAdmin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.

This is AS USUAL for MS Maintenance Plans absolutely useless. Run the DBCC CHECKDB for the database that failed. Don't do it with a maintenance plan. Run it in good old Query Analyzer. Let us know what the error is you get from that, which will hopefully, and usually is, be more informative then gee, you seem to have a problem.

:) That's like one of our developers who came up to me today and said "Derrick, there's a problem with one of my programs." and then just stood there. "Yeah...SO....GO AWAY!!!!!"|||Listen...you CRACK ME UP...

ok, Now you want storeis?

Had an Ireland near shore ask me if it was a good idea to do a join or a 12 level nested cursor...

PLEASE!

I'll trade with you in a heart beat....|||12 level? WOW. You should have told him it was a great idea. It probably would have been a good contract after he got fired. :) Hey....FREEEEEE Trip.|||Can you nest 12 cursors? And more importantly, can you run anything else on the box when it kicks off?|||Hi, guys, i was away yesterday, i check today, everything is fine, No any problem, i think the database should be in single user mode. Thank you all.
But i have another question, why one user use sql server database, they have two process ID with same user and database?|||Open up two Query Analyzer connections. You'll see the same thing for you. :)|||But they are database user (Client), Why they also have two Process ID, also, i found the two host are different, one is their own host, another is not, why that happen? Thanks.

58 0 DOM\ssapienza Notary sleeping 0 AWAITING COMMAND Microsoft Office XP 0 not waiting 953 0 0 7/27/2004 11:02 7/27/2004 11:53 S27567 Named Pipes 00105A6D68CD 0 0
59 0 DOM\ssapienza Notary sleeping 0 AWAITING COMMAND Microsoft Office XP 0 not waiting 1048 6 91 7/27/2004 11:02 7/27/2004 11:53 D27450 Named Pipes 00105A6D68CD 0 0|||Use Profiler and trace SP:Completed and RPC:Completed with a filter on this user. Find out what they're doing. Does this user use Access to do things in the SQL Server database by any chance?|||Thanks, I will try. First i need to learn how to use profile, Is that use the memory? My server memory space is limit.

Integrity Checks Failed?

We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status: Faile
d
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?Have you looked at the report that is generated from your maintenance plan?
Possibly this report will help you determine what is wrong. If you are not
generating the report, then review your options under the "Reporting" tab
while editing your maintenance plan.
----
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
> We have 3 maintenance plans, each running against a different subset of
> databases on the same server. Each maintenance plan runs integrity checks
> once a week. According to "Job History", one of the three jobs fails
every
> week. Looking at the sql logs every DBCC check shows "found 0 errors and
> repaired 0 errors." In the server's Application Event Log we see this
vague
> error message:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 1/2/2005
> Time: 12:00:27 AM
> User: N/A
> Computer: FBENSQLP1
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
> - Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
> invoked by Schedule 19 (Schedule 1). The last step to run was step 1
(Step
> 1).
> Is it possible that this is some sort of a false alert? The other two
> weekly integrity checks always show successful completions.
> What might cause this job to "Fail" every week?
>|||No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?|||You need to uncheck the checkbox in the MP wizard that states to "Fix Minor
Repairs". Then it won't attempt to put the db into single user mode and it
will operate properly. If there is a problem the job will fail and then you
can handle the issue the correct way as is best suited for your environment
.
--
Andrew J. Kelly SQL MVP
"Anna Emegard" <Anna.Emegard@.harryda.se> wrote in message news:ufX7Xb$HFHA.1
172@.TK2MSFTNGP12.phx.gbl...
Hi!
We have the exact same error. We run the integrity check once a week on this
one database and it has run smoothly until three weeks ago. In the log file
it says "Database state cannot be changed while other users are using the d
atabase". There are other jobs running before and after this job and there a
re no problems with them. I can't figure out why this particular job won't r
un.
Sincerely,
Anna
[vbcol=seagreen]
No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
--
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?

Integrity Checks Failed?

We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status: Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?Have you looked at the report that is generated from your maintenance plan?
Possibly this report will help you determine what is wrong. If you are not
generating the report, then review your options under the "Reporting" tab
while editing your maintenance plan.
--
----
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
> We have 3 maintenance plans, each running against a different subset of
> databases on the same server. Each maintenance plan runs integrity checks
> once a week. According to "Job History", one of the three jobs fails
every
> week. Looking at the sql logs every DBCC check shows "found 0 errors and
> repaired 0 errors." In the server's Application Event Log we see this
vague
> error message:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 1/2/2005
> Time: 12:00:27 AM
> User: N/A
> Computer: FBENSQLP1
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
> - Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
> invoked by Schedule 19 (Schedule 1). The last step to run was step 1
(Step
> 1).
> Is it possible that this is some sort of a false alert? The other two
> weekly integrity checks always show successful completions.
> What might cause this job to "Fail" every week?
>|||No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?|||--____XAVHMWYRSQSWQDYPECYE____
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hi!
We have the exact same error. We run the integrity check once a week on =this one database and it has run smoothly until three weeks ago. In the =log file it says "Database state cannot be changed while other users are =using the database". There are other jobs running before and after this =job and there are no problems with them. I can't figure out why this =particular job won't run.
Sincerely,
Anna
>> AnthonyThomas<Anthony.Thomas@.CommerceBank.com> 2005-01-03 17:11:38 >>
No, something indeed happened; the problem is finding out more details as =to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info =on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If =there
were database connectivity issues, then this information will be missing =and
the text log files your created above will be the only source of informatio=n
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
--
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails =every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this =vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 =(Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?
--____XAVHMWYRSQSWQDYPECYE____
Content-Type: multipart/related; boundary="____JVBAVOGAYIGGGPIKBBLQ____"
--____JVBAVOGAYIGGGPIKBBLQ____
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
&

Hi!
We have the exact same error. We run the integrity check once a =week on this one database and it has run smoothly until three weeks ago. =In the log file it says "Database state cannot be changed while other =users are using the database". There are other jobs running before and =after this job and there are no problems with them. I can't figure =out why this particular job won't run.
Sincerely,
Anna> AnthonyThomas 2005-01-03 17:11:38 >>
No, something indeed happened; the problem =is finding out more details as towhy. There are several logging =options available to you.1. In the maintenance plan, Reporting =Tab, choose to retain informationwithin the MSDB database but also =create Job Run report to a text file.Oftentimes, this information= will provide you with the necessary detail.2. On the job, make =sure it is configured to output additional step info onthe advanced =tab of the step settings.3. You've already discovered the SQL =Server error logs and the WindowsApplication event logs, also take a =look at the SQL Agent error logs.To view the maintenance history, =in SQL EM, right-click one of themaintenance plans and choose to view =the history. This log will tell youeach activity, and each =database, whether successfull or failure. If therewere database =connectivity issues, then this information will be missing andthe text =log files your created above will be the only source of informationouts=ide of the error logs you have already discovered.Hope this =helps.Sincerely,Anthony Thomas-- "A=nthonyMunoz" wrote in =messagenews:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...We= have 3 maintenance plans, each running against a different subset =ofdatabases on the same server. Each maintenance plan runs =integrity checksonce a week. According to "Job History", one of =the three jobs fails everyweek. Looking at the sql logs every =DBCC check shows "found 0 errors andrepaired 0 errors." In the =server's Application Event Log we see this vagueerror message:E=vent Type: WarningEvent Source: SQLSERVERAGENTEvent Category: Job =EngineEvent ID: 208Date: 1/2/2005Time: 12:00:27 AMUser: =N/AComputer: FBENSQLP1Description:SQL Server Scheduled Job ='Integrity Checks Job for DB Maintenance Plan'Internal Maintenance'' =(0x860A641AB3C0FD4CA22C0369E63523E4) - Status:Failed- Invoked on: =2005-01-02 00:00:00 - Message: The job failed. The Job wasinvoked= by Schedule 19 (Schedule 1). The last step to run was step 1 =(Step1).Is it possible that this is some sort of a false =alert? The other twoweekly integrity checks always show =successful completions.What might cause this job to "Fail" every =week?

--____JVBAVOGAYIGGGPIKBBLQ____--
--____XAVHMWYRSQSWQDYPECYE____--|||This is a multi-part message in MIME format.
--=_NextPart_000_0070_01C51FCF.9D6B6680
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
You need to uncheck the checkbox in the MP wizard that states to "Fix =Minor Repairs". Then it won't attempt to put the db into single user =mode and it will operate properly. If there is a problem the job will =fail and then you can handle the issue the correct way as is best suited =for your environment.
-- Andrew J. Kelly SQL MVP

"Anna Emegard" <Anna.Emegard@.harryda.se> wrote in message =news:ufX7Xb$HFHA.1172@.TK2MSFTNGP12.phx.gbl...
Hi!
We have the exact same error. We run the integrity check once a week =on this one database and it has run smoothly until three weeks ago. In =the log file it says "Database state cannot be changed while other users =are using the database". There are other jobs running before and after =this job and there are no problems with them. I can't figure out why =this particular job won't run.
Sincerely,
Anna
>> AnthonyThomas<Anthony.Thomas@.CommerceBank.com> 2005-01-03 17:11:38 =
No, something indeed happened; the problem is finding out more details =as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain =information
within the MSDB database but also create Job Run report to a text =file.
Oftentimes, this information will provide you with the necessary =detail.
2. On the job, make sure it is configured to output additional step =info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell =you
each activity, and each database, whether successfull or failure. If =there
were database connectivity issues, then this information will be =missing and
the text log files your created above will be the only source of =information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas
--
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in =message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset =of
databases on the same server. Each maintenance plan runs integrity =checks
once a week. According to "Job History", one of the three jobs fails =every
week. Looking at the sql logs every DBCC check shows "found 0 errors =and
repaired 0 errors." In the server's Application Event Log we see this =vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job =was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 =(Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?
--=_NextPart_000_0070_01C51FCF.9D6B6680
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

You need to uncheck the checkbox in the MP =wizard that states to "Fix Minor Repairs". Then it won't attempt to put the db =into single user mode and it will operate properly. If there is a =problem the job will fail and then you can handle the issue the correct way as is =best suited for your environment.
-- Andrew J. Kelly SQL MVP
"Anna Emegard" =wrote in message news:ufX7Xb$HFHA.1172=@.TK2MSFTNGP12.phx.gbl...
Hi!

We have the exact same error. We run the integrity check =once a week on this one database and it has run smoothly until three weeks ago. In =the log file it says "Database state cannot be changed while other users are =using the database". There are other jobs running before and after this job =and there are no problems with them. I can't figure out why this =particular job won't run.

Sincerely,
Anna> AnthonyThomas 2005-01-03 =17:11:38 >>
No, something indeed happened; the =problem is finding out more details as towhy. There are several logging =options available to you.1. In the maintenance plan, Reporting Tab, =choose to retain informationwithin the MSDB database but also create =Job Run report to a text file.Oftentimes, this information will provide =you with the necessary detail.2. On the job, make sure it is configured =to output additional step info onthe advanced tab of the step settings.3. You've already discovered the SQL Server error =logs and the WindowsApplication event logs, also take a look at the SQL =Agent error logs.To view the maintenance history, in SQL EM, right-click =one of themaintenance plans and choose to view the history. This =log will tell youeach activity, and each database, whether successfull or failure. If therewere database connectivity issues, then =this information will be missing andthe text log files your created =above will be the only source of informationoutside of the error logs you =have already discovered.Hope this helps.Sincerely,Anthony Thomas-- "AnthonyMunoz" =wrote in =messagenews:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...=We have 3 maintenance plans, each running against a different subset ofdatabases on the same server. Each maintenance plan runs =integrity checksonce a week. According to "Job History", one of the =three jobs fails everyweek. Looking at the sql logs every DBCC check =shows "found 0 errors andrepaired 0 errors." In the server's =Application Event Log we see this vagueerror message:Event Type: WarningEvent Source: SQLSERVERAGENTEvent Category: Job =EngineEvent ID: 208Date: 1/2/2005Time: 12:00:27 AMUser: =N/AComputer: FBENSQLP1Description:SQL Server Scheduled Job 'Integrity =Checks Job for DB Maintenance Plan'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:Failed- Invoked =on: 2005-01-02 00:00:00 - Message: The job failed. The Job =wasinvoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step1).Is it possible that this is some sort of a false alert? The other twoweekly integrity checks always show =successful completions.What might cause this job to "Fail" every week?

--=_NextPart_000_0070_01C51FCF.9D6B6680--

Integrity Checks Failed?

We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type:Warning
Event Source:SQLSERVERAGENT
Event Category:Job Engine
Event ID:208
Date:1/2/2005
Time:12:00:27 AM
User:N/A
Computer:FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status: Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?
Have you looked at the report that is generated from your maintenance plan?
Possibly this report will help you determine what is wrong. If you are not
generating the report, then review your options under the "Reporting" tab
while editing your maintenance plan.
----
-
Need SQL Server Examples check out my website
http://www.geocities.com/sqlserverexamples
"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
> We have 3 maintenance plans, each running against a different subset of
> databases on the same server. Each maintenance plan runs integrity checks
> once a week. According to "Job History", one of the three jobs fails
every
> week. Looking at the sql logs every DBCC check shows "found 0 errors and
> repaired 0 errors." In the server's Application Event Log we see this
vague
> error message:
> Event Type: Warning
> Event Source: SQLSERVERAGENT
> Event Category: Job Engine
> Event ID: 208
> Date: 1/2/2005
> Time: 12:00:27 AM
> User: N/A
> Computer: FBENSQLP1
> Description:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
> 'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
> - Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
> invoked by Schedule 19 (Schedule 1). The last step to run was step 1
(Step
> 1).
> Is it possible that this is some sort of a false alert? The other two
> weekly integrity checks always show successful completions.
> What might cause this job to "Fail" every week?
>
|||No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas

"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?
|||You need to uncheck the checkbox in the MP wizard that states to "Fix Minor Repairs". Then it won't attempt to put the db into single user mode and it will operate properly. If there is a problem the job will fail and then you can handle the issue the correct way as is best suited for your environment.
Andrew J. Kelly SQL MVP
"Anna Emegard" <Anna.Emegard@.harryda.se> wrote in message news:ufX7Xb$HFHA.1172@.TK2MSFTNGP12.phx.gbl...
Hi!
We have the exact same error. We run the integrity check once a week on this one database and it has run smoothly until three weeks ago. In the log file it says "Database state cannot be changed while other users are using the database". There are other jobs running before and after this job and there are no problems with them. I can't figure out why this particular job won't run.
Sincerely,
Anna
[vbcol=seagreen]
No, something indeed happened; the problem is finding out more details as to
why. There are several logging options available to you.
1. In the maintenance plan, Reporting Tab, choose to retain information
within the MSDB database but also create Job Run report to a text file.
Oftentimes, this information will provide you with the necessary detail.
2. On the job, make sure it is configured to output additional step info on
the advanced tab of the step settings.
3. You've already discovered the SQL Server error logs and the Windows
Application event logs, also take a look at the SQL Agent error logs.
To view the maintenance history, in SQL EM, right-click one of the
maintenance plans and choose to view the history. This log will tell you
each activity, and each database, whether successfull or failure. If there
were database connectivity issues, then this information will be missing and
the text log files your created above will be the only source of information
outside of the error logs you have already discovered.
Hope this helps.
Sincerely,
Anthony Thomas

"AnthonyMunoz" <AnthonyMunoz@.discussions.microsoft.com> wrote in message
news:6D182012-CFDD-4A1F-86FD-19297F036C6F@.microsoft.com...
We have 3 maintenance plans, each running against a different subset of
databases on the same server. Each maintenance plan runs integrity checks
once a week. According to "Job History", one of the three jobs fails every
week. Looking at the sql logs every DBCC check shows "found 0 errors and
repaired 0 errors." In the server's Application Event Log we see this vague
error message:
Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 1/2/2005
Time: 12:00:27 AM
User: N/A
Computer: FBENSQLP1
Description:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'Internal Maintenance'' (0x860A641AB3C0FD4CA22C0369E63523E4) - Status:
Failed
- Invoked on: 2005-01-02 00:00:00 - Message: The job failed. The Job was
invoked by Schedule 19 (Schedule 1). The last step to run was step 1 (Step
1).
Is it possible that this is some sort of a false alert? The other two
weekly integrity checks always show successful completions.
What might cause this job to "Fail" every week?

Wednesday, March 7, 2012

Integrity Checks Fail

I'm not sure what my response to this error should be.
JOB RUN: 'Integrity Checks Job for DB Maintenance Plan 'DB Maintenance
Plan2'' was run on 11/26/2006 at 00:00:03
DURATION: 0 hours, 1 minutes, 14 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 190 (Schedule 1).
The last step to run was step 1 (Step 1).
CheckDB reported
CHECKDB found 0 allocation errors and 0 consistency errors in database
'ATOMS'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
However CheckCatalog reports:
Server: Msg 2513, Level 16, State 2, Line 1
Table error: Object ID 231723928 (object '231723928') does not match between
'SYSCOLUMNS' and 'SYSOBJECTS'.
(many more)
And
Table error: Object ID 423724612 (object '423724612') does not match between
'SYSINDEXES' and 'SYSOBJECTS'.
Server: Msg 2513, Level 16, State 1, Line 1
Help appreciated.
--
Regards,
JamieYou might want to have a look at these:
http://blogs.msdn.com/sqlserverstorageengine/archive/tags/DBCC/default.aspx
Andrew J. Kelly SQL MVP
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:1162D111-8C87-40B9-99FD-91BF48290290@.microsoft.com...
> I'm not sure what my response to this error should be.
> JOB RUN: 'Integrity Checks Job for DB Maintenance Plan 'DB Maintenance
> Plan2'' was run on 11/26/2006 at 00:00:03
> DURATION: 0 hours, 1 minutes, 14 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 190 (Schedule
> 1).
> The last step to run was step 1 (Step 1).
> CheckDB reported
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'ATOMS'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> However CheckCatalog reports:
> Server: Msg 2513, Level 16, State 2, Line 1
> Table error: Object ID 231723928 (object '231723928') does not match
> between
> 'SYSCOLUMNS' and 'SYSOBJECTS'.
> (many more)
> And
> Table error: Object ID 423724612 (object '423724612') does not match
> between
> 'SYSINDEXES' and 'SYSOBJECTS'.
> Server: Msg 2513, Level 16, State 1, Line 1
> Help appreciated.
> --
> Regards,
> Jamie|||And a very short summary of options and recommendations:
http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OGNhkfkFHHA.1240@.TK2MSFTNGP03.phx.gbl...
> You might want to have a look at these:
> http://blogs.msdn.com/sqlserverstorageengine/archive/tags/DBCC/default.aspx
>
> --
> Andrew J. Kelly SQL MVP
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:1162D111-8C87-40B9-99FD-91BF48290290@.microsoft.com...
>> I'm not sure what my response to this error should be.
>> JOB RUN: 'Integrity Checks Job for DB Maintenance Plan 'DB Maintenance
>> Plan2'' was run on 11/26/2006 at 00:00:03
>> DURATION: 0 hours, 1 minutes, 14 seconds
>> STATUS: Failed
>> MESSAGES: The job failed. The Job was invoked by Schedule 190 (Schedule 1).
>> The last step to run was step 1 (Step 1).
>> CheckDB reported
>> CHECKDB found 0 allocation errors and 0 consistency errors in database
>> 'ATOMS'.
>> DBCC execution completed. If DBCC printed error messages, contact your
>> system administrator.
>> However CheckCatalog reports:
>> Server: Msg 2513, Level 16, State 2, Line 1
>> Table error: Object ID 231723928 (object '231723928') does not match between
>> 'SYSCOLUMNS' and 'SYSOBJECTS'.
>> (many more)
>> And
>> Table error: Object ID 423724612 (object '423724612') does not match between
>> 'SYSINDEXES' and 'SYSOBJECTS'.
>> Server: Msg 2513, Level 16, State 1, Line 1
>> Help appreciated.
>> --
>> Regards,
>> Jamie
>

Integrity Checks Fail

I'm not sure what my response to this error should be.
JOB RUN: 'Integrity Checks Job for DB Maintenance Plan 'DB Maintenance
Plan2'' was run on 11/26/2006 at 00:00:03
DURATION: 0 hours, 1 minutes, 14 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 190 (Schedule 1).
The last step to run was step 1 (Step 1).
CheckDB reported
CHECKDB found 0 allocation errors and 0 consistency errors in database
'ATOMS'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
However CheckCatalog reports:
Server: Msg 2513, Level 16, State 2, Line 1
Table error: Object ID 231723928 (object '231723928') does not match between
'SYSCOLUMNS' and 'SYSOBJECTS'.
(many more)
And
Table error: Object ID 423724612 (object '423724612') does not match between
'SYSINDEXES' and 'SYSOBJECTS'.
Server: Msg 2513, Level 16, State 1, Line 1
Help appreciated.
Regards,
JamieYou might want to have a look at these:
http://blogs.msdn.com/sqlserverstor...CC/default.aspx
Andrew J. Kelly SQL MVP
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:1162D111-8C87-40B9-99FD-91BF48290290@.microsoft.com...
> I'm not sure what my response to this error should be.
> JOB RUN: 'Integrity Checks Job for DB Maintenance Plan 'DB Maintenance
> Plan2'' was run on 11/26/2006 at 00:00:03
> DURATION: 0 hours, 1 minutes, 14 seconds
> STATUS: Failed
> MESSAGES: The job failed. The Job was invoked by Schedule 190 (Schedule
> 1).
> The last step to run was step 1 (Step 1).
> CheckDB reported
> CHECKDB found 0 allocation errors and 0 consistency errors in database
> 'ATOMS'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
> However CheckCatalog reports:
> Server: Msg 2513, Level 16, State 2, Line 1
> Table error: Object ID 231723928 (object '231723928') does not match
> between
> 'SYSCOLUMNS' and 'SYSOBJECTS'.
> (many more)
> And
> Table error: Object ID 423724612 (object '423724612') does not match
> between
> 'SYSINDEXES' and 'SYSOBJECTS'.
> Server: Msg 2513, Level 16, State 1, Line 1
> Help appreciated.
> --
> Regards,
> Jamie|||And a very short summary of options and recommendations:
http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OGNhkfkFHHA.1240@.TK2MSFTNGP03.phx.gbl...
> You might want to have a look at these:
> [url]http://blogs.msdn.com/sqlserverstorageengine/archive/tags/DBCC/default.aspx[/url
]
>
> --
> Andrew J. Kelly SQL MVP
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:1162D111-8C87-40B9-99FD-91BF48290290@.microsoft.com...
>

Integrity Checks continue to fail

I have a Maintenance plan schedule on one my dev databases, and I'm
continually getting notices that it is failing. Here is the report that I
get:
Starting maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:00
PM
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 5070: [Microsoft]&#
91;ODBC SQL
Server Driver][SQL Server]Database state cannot be changed while other u
sers
are using the database 'CRMDEV'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE st
atement
failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption comma
nd failed.
[1] Database CRMDEV: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 7919: [Microsoft]&#
91;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 **
End of maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:01 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
How do I put a database in "single-user" mode to run an Integrity check?
Thanks,
SaraSaral6978 wrote:
> I have a Maintenance plan schedule on one my dev databases, and I'm
> continually getting notices that it is failing. Here is the report that I
> get:
> Starting maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:0
0 PM
> [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 'CRMDEV'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE
statement
> failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption com
mand failed.
> [1] Database CRMDEV: 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 nee
ds to
> be in single user mode.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statemen
t not
> processed. Database needs to be in single user mode.
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> End of maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:01
PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> How do I put a database in "single-user" mode to run an Integrity check?
> Thanks,
> Sara
>
The maintenance plan is attempting to put the DB in single user mode
(that's what the failing ALTER DATABASE statement is doing). It's
failing because someone/something has a connection that can't be terminated.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||A database does NOT need to be in the single user mode to perform integrity
checks. But it does need to be in the single user mode to attempt any repair
.
Automated repair is a dangerous business, and I'd suggest that you modify
your maintenance plan to disable it. In addition, it's not rare for a
database to be left in the single user mode after the repair is done, thus
preventing others from using the database until you intervene.
Linchi
"Saral6978" wrote:

> I have a Maintenance plan schedule on one my dev databases, and I'm
> continually getting notices that it is failing. Here is the report that I
> get:
> Starting maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:0
0 PM
> [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 'CRMDEV'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE
statement
> failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption com
mand failed.
> [1] Database CRMDEV: 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 nee
ds to
> be in single user mode.
> The following errors were found:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Repair statemen
t not
> processed. Database needs to be in single user mode.
> ** Execution Time: 0 hrs, 0 mins, 1 secs **
> End of maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:01
PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> How do I put a database in "single-user" mode to run an Integrity check?
> Thanks,
> Sara
>|||Linchi - thank you so much for your suggestion...I will disable the automati
c
repair...thanks!
"Linchi Shea" wrote:
[vbcol=seagreen]
> A database does NOT need to be in the single user mode to perform integrit
y
> checks. But it does need to be in the single user mode to attempt any repa
ir.
> Automated repair is a dangerous business, and I'd suggest that you modify
> your maintenance plan to disable it. In addition, it's not rare for a
> database to be left in the single user mode after the repair is done, thus
> preventing others from using the database until you intervene.
> Linchi
> "Saral6978" wrote:
>|||Okay - I just unchecked the "Attempt to repair" box, ran the Integrity check
,
and it was successful.
Thank you so much!
"Linchi Shea" wrote:
[vbcol=seagreen]
> A database does NOT need to be in the single user mode to perform integrit
y
> checks. But it does need to be in the single user mode to attempt any repa
ir.
> Automated repair is a dangerous business, and I'd suggest that you modify
> your maintenance plan to disable it. In addition, it's not rare for a
> database to be left in the single user mode after the repair is done, thus
> preventing others from using the database until you intervene.
> Linchi
> "Saral6978" wrote:
>

Integrity Checks continue to fail

I have a Maintenance plan schedule on one my dev databases, and I'm
continually getting notices that it is failing. Here is the report that I
get:
Starting maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:00 PM
[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 'CRMDEV'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
[1] Database CRMDEV: 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 **
End of maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:01 PM
SQLMAINT.EXE Process Exit Code: 1 (Failed)
How do I put a database in "single-user" mode to run an Integrity check?
Thanks,
Sara
Saral6978 wrote:
> I have a Maintenance plan schedule on one my dev databases, and I'm
> continually getting notices that it is failing. Here is the report that I
> get:
> Starting maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:00 PM
> [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 'CRMDEV'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
> failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
> [1] Database CRMDEV: 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 **
> End of maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:01 PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> How do I put a database in "single-user" mode to run an Integrity check?
> Thanks,
> Sara
>
The maintenance plan is attempting to put the DB in single user mode
(that's what the failing ALTER DATABASE statement is doing). It's
failing because someone/something has a connection that can't be terminated.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||A database does NOT need to be in the single user mode to perform integrity
checks. But it does need to be in the single user mode to attempt any repair.
Automated repair is a dangerous business, and I'd suggest that you modify
your maintenance plan to disable it. In addition, it's not rare for a
database to be left in the single user mode after the repair is done, thus
preventing others from using the database until you intervene.
Linchi
"Saral6978" wrote:

> I have a Maintenance plan schedule on one my dev databases, and I'm
> continually getting notices that it is failing. Here is the report that I
> get:
> Starting maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:00 PM
> [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 'CRMDEV'
> [Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
> failed.
> [Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
> [1] Database CRMDEV: 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 **
> End of maintenance plan 'CRMDEV DB Maintenance Plan' on 1/11/2007 8:00:01 PM
> SQLMAINT.EXE Process Exit Code: 1 (Failed)
>
> How do I put a database in "single-user" mode to run an Integrity check?
> Thanks,
> Sara
>
|||Linchi - thank you so much for your suggestion...I will disable the automatic
repair...thanks!
"Linchi Shea" wrote:
[vbcol=seagreen]
> A database does NOT need to be in the single user mode to perform integrity
> checks. But it does need to be in the single user mode to attempt any repair.
> Automated repair is a dangerous business, and I'd suggest that you modify
> your maintenance plan to disable it. In addition, it's not rare for a
> database to be left in the single user mode after the repair is done, thus
> preventing others from using the database until you intervene.
> Linchi
> "Saral6978" wrote:
|||Okay - I just unchecked the "Attempt to repair" box, ran the Integrity check,
and it was successful.
Thank you so much!
"Linchi Shea" wrote:
[vbcol=seagreen]
> A database does NOT need to be in the single user mode to perform integrity
> checks. But it does need to be in the single user mode to attempt any repair.
> Automated repair is a dangerous business, and I'd suggest that you modify
> your maintenance plan to disable it. In addition, it's not rare for a
> database to be left in the single user mode after the repair is done, thus
> preventing others from using the database until you intervene.
> Linchi
> "Saral6978" wrote:

Integrity Check/Optimization Check

As part of a Maintenance plan we have an Integrity check scheduled for 12:00
AM every Sunday Morning and an Optimization Check 1:00 AM every Sunday. I'm
noticing errors from one of of our Web Application that connects to a SQL
database. It has a process that runs every night 12:00 AM. This process
requires access to one of the Databses on the SQL server. The error is
basically a SQL error that states cannot open db, login failed. My question
is if the integrity check or optimization check would cause this. Does it
prevent anything from connecting to the database?The activities created from the Maintenance Plan wizard 'should' not keep
any user from connecting to the database. There may be some slowness, but
normal activity should not be impeded.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:D916B0EF-7158-4429-90B6-61CD9CB8B356@.microsoft.com...
> As part of a Maintenance plan we have an Integrity check scheduled for
> 12:00
> AM every Sunday Morning and an Optimization Check 1:00 AM every Sunday.
> I'm
> noticing errors from one of of our Web Application that connects to a SQL
> database. It has a process that runs every night 12:00 AM. This process
> requires access to one of the Databses on the SQL server. The error is
> basically a SQL error that states cannot open db, login failed. My
> question
> is if the integrity check or optimization check would cause this. Does it
> prevent anything from connecting to the database?|||George Schneider wrote:
> As part of a Maintenance plan we have an Integrity check scheduled for 12:00
> AM every Sunday Morning and an Optimization Check 1:00 AM every Sunday. I'm
> noticing errors from one of of our Web Application that connects to a SQL
> database. It has a process that runs every night 12:00 AM. This process
> requires access to one of the Databses on the SQL server. The error is
> basically a SQL error that states cannot open db, login failed. My question
> is if the integrity check or optimization check would cause this. Does it
> prevent anything from connecting to the database?
If you've told the integrity check to attempt to fix any errors that it
finds, it will put the database into single-user/DBO only mode,
preventing other logins from connecting.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Oops, I forgot about that 'checkbox'. (Never use it and hope folks don't.)
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:456C78F0.4040101@.realsqlguy.com...
> George Schneider wrote:
>> As part of a Maintenance plan we have an Integrity check scheduled for
>> 12:00 AM every Sunday Morning and an Optimization Check 1:00 AM every
>> Sunday. I'm noticing errors from one of of our Web Application that
>> connects to a SQL database. It has a process that runs every night 12:00
>> AM. This process requires access to one of the Databses on the SQL
>> server. The error is basically a SQL error that states cannot open db,
>> login failed. My question is if the integrity check or optimization
>> check would cause this. Does it prevent anything from connecting to the
>> database?
> If you've told the integrity check to attempt to fix any errors that it
> finds, it will put the database into single-user/DBO only mode, preventing
> other logins from connecting.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Arnie Rowland wrote:
> Oops, I forgot about that 'checkbox'. (Never use it and hope folks don't.)
>
Ditto...
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||If this is checked is the Databse put nto single user mode/DBO during the
scan or only if it finds an issue? If this is not checked how would I know
if there is an Integrity error? I would have to fix it myself instead of
having SQL automatically do this? How would I go about fixing integrity
issues then?
"Arnie Rowland" wrote:
> Oops, I forgot about that 'checkbox'. (Never use it and hope folks don't.)
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
> news:456C78F0.4040101@.realsqlguy.com...
> > George Schneider wrote:
> >> As part of a Maintenance plan we have an Integrity check scheduled for
> >> 12:00 AM every Sunday Morning and an Optimization Check 1:00 AM every
> >> Sunday. I'm noticing errors from one of of our Web Application that
> >> connects to a SQL database. It has a process that runs every night 12:00
> >> AM. This process requires access to one of the Databses on the SQL
> >> server. The error is basically a SQL error that states cannot open db,
> >> login failed. My question is if the integrity check or optimization
> >> check would cause this. Does it prevent anything from connecting to the
> >> database?
> >
> > If you've told the integrity check to attempt to fix any errors that it
> > finds, it will put the database into single-user/DBO only mode, preventing
> > other logins from connecting.
> >
> >
> > --
> > Tracy McKibben
> > MCDBA
> > http://www.realsqlguy.com
>
>|||George Schneider wrote:
> If this is checked is the Databse put nto single user mode/DBO during the
> scan or only if it finds an issue? If this is not checked how would I know
> if there is an Integrity error? I would have to fix it myself instead of
> having SQL automatically do this? How would I go about fixing integrity
> issues then?
>
You're better off learning the various DBCC commands that are available
to you, as opposed to letting the maintenance plan auto-magically fix
things.
--
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||You need to read up about the DBCC CHECKDB command. This is the very basic starting point. When the
option is checked, the database is put in single user mode and then DBCC CHECKDB command is executed
with the REPAIR_FAST option, and the db is put back in multi user mode.
What we do is to *not* check this option, and have CHECKDB report the error it finds, the job will
fail and you will be notified of the job failure so you can act.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:B5B7C210-DB54-43C0-AAEE-0FDF48CBFF28@.microsoft.com...
> If this is checked is the Databse put nto single user mode/DBO during the
> scan or only if it finds an issue? If this is not checked how would I know
> if there is an Integrity error? I would have to fix it myself instead of
> having SQL automatically do this? How would I go about fixing integrity
> issues then?
> "Arnie Rowland" wrote:
>> Oops, I forgot about that 'checkbox'. (Never use it and hope folks don't.)
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>> You can't help someone get up a hill without getting a little closer to the
>> top yourself.
>> - H. Norman Schwarzkopf
>>
>> "Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
>> news:456C78F0.4040101@.realsqlguy.com...
>> > George Schneider wrote:
>> >> As part of a Maintenance plan we have an Integrity check scheduled for
>> >> 12:00 AM every Sunday Morning and an Optimization Check 1:00 AM every
>> >> Sunday. I'm noticing errors from one of of our Web Application that
>> >> connects to a SQL database. It has a process that runs every night 12:00
>> >> AM. This process requires access to one of the Databses on the SQL
>> >> server. The error is basically a SQL error that states cannot open db,
>> >> login failed. My question is if the integrity check or optimization
>> >> check would cause this. Does it prevent anything from connecting to the
>> >> database?
>> >
>> > If you've told the integrity check to attempt to fix any errors that it
>> > finds, it will put the database into single-user/DBO only mode, preventing
>> > other logins from connecting.
>> >
>> >
>> > --
>> > Tracy McKibben
>> > MCDBA
>> > http://www.realsqlguy.com
>>|||Is that checkbox what is causing the databse to lock and not allow any user
login?
"Tracy McKibben" wrote:
> Arnie Rowland wrote:
> > Oops, I forgot about that 'checkbox'. (Never use it and hope folks don't.)
> >
> Ditto...
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Yes.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"George Schneider" <georgedschneider@.news.postalias> wrote in message
news:FD54EDB5-3346-4B64-AF4F-6602CF87F568@.microsoft.com...
> Is that checkbox what is causing the databse to lock and not allow any user
> login?
> "Tracy McKibben" wrote:
>> Arnie Rowland wrote:
>> > Oops, I forgot about that 'checkbox'. (Never use it and hope folks don't.)
>> >
>> Ditto...
>> --
>> Tracy McKibben
>> MCDBA
>> http://www.realsqlguy.com

Wednesday, March 21, 2012

Interesting Maintenance Plan Problem

Interesting Maintenance Plan Problem

Interesting Maintenance Plan Problem

Friday, March 9, 2012

Integrity job error

Integrity checks job failed

Integrity Checks Failed?

Integrity Checks Failed?

Integrity Checks Failed?

Wednesday, March 7, 2012

Integrity Checks Fail

Integrity Checks Fail

Integrity Checks Fail

Integrity Checks continue to fail

Integrity Checks continue to fail

Integrity Check/Optimization Check

Integrity Check/Optimization Check

Integrity Check/Optimization Check

Integrated Security

Blog Archive

About Me