Win2000sp4. SQL2k sp3
One server I have the option selected to Attempt to repair any minor
problems is checked on the Integrity checks. I know it is trying to repair
something due to the fact it is trying to place in single user mode and
can't due to connections.
My problem is that I have ran dbcc checkdb and no errors were found. So
what is exactly is it detecting and how do I detect the same? Certain trace
flags or option need to be set with dbcc checkdb?
TIA
CDThe DBCC CHECKDB has a parameter about how to repair the
error if it finds any. You can check BOL for details.
>--Original Message--
>Win2000sp4. SQL2k sp3
>One server I have the option selected to Attempt to
repair any minor
>problems is checked on the Integrity checks. I know it
is trying to repair
>something due to the fact it is trying to place in single
user mode and
>can't due to connections.
>My problem is that I have ran dbcc checkdb and no errors
were found. So
>what is exactly is it detecting and how do I detect the
same? Certain trace
>flags or option need to be set with dbcc checkdb?
>TIA
>CD
>
>.
>|||Remove the option to attempt to repair any minor
problems...it just causes problems with maintenance plans
and is not a good idea anyway. If you have errors in a dbcc
checkdb, you want to investigate the errors, find what the
root of the problem is and address the issue or issues
yourself before you would even consider using this option.
-Sue
On Wed, 12 Nov 2003 15:15:54 -0600, "CD"
<mcdye1@.hotmail.nospam.com> wrote:
>Win2000sp4. SQL2k sp3
>One server I have the option selected to Attempt to repair any minor
>problems is checked on the Integrity checks. I know it is trying to repair
>something due to the fact it is trying to place in single user mode and
>can't due to connections.
>My problem is that I have ran dbcc checkdb and no errors were found. So
>what is exactly is it detecting and how do I detect the same? Certain trace
>flags or option need to be set with dbcc checkdb?
>TIA
>CD
>|||Thanks for the replies, but you have missed the point. dbcc checkdb found
no errors.
The following leads me to believe that something was detected. But What?
How to confirm? Add switches to DBCC command? trace flag?
[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 'BaseQuery'
[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
failed.
[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
[1] Database BaseQuery: 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, 7 secs **
> On Wed, 12 Nov 2003 15:15:54 -0600, "CD"
> <mcdye1@.hotmail.nospam.com> wrote:
> >Win2000sp4. SQL2k sp3
> >
> >One server I have the option selected to Attempt to repair any minor
> >problems is checked on the Integrity checks. I know it is trying to
repair
> >something due to the fact it is trying to place in single user mode and
> >can't due to connections.
> >
> >My problem is that I have ran dbcc checkdb and no errors were found. So
> >what is exactly is it detecting and how do I detect the same? Certain
trace
> >flags or option need to be set with dbcc checkdb?
> >
> >TIA
> >CD
> >
>|||Don't believe I missed the point. When you run the integrity
check with that option, the maintenance plan attempts to put
the database in single user mode before it even runs the
integrity check. It doesn't run one version, detects an
error and then runs it again. It just attempts to put the
database in single user mode when using this option.
-Sue
On Thu, 13 Nov 2003 08:12:55 -0600, "CD"
<mcdye1@.hotmail.nospam.com> wrote:
>Thanks for the replies, but you have missed the point. dbcc checkdb found
>no errors.
>The following leads me to believe that something was detected. But What?
>How to confirm? Add switches to DBCC command? trace flag?
>[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 'BaseQuery'
>[Microsoft][ODBC SQL Server Driver][SQL Server]ALTER DATABASE statement
>failed.
>[Microsoft][ODBC SQL Server Driver][SQL Server]sp_dboption command failed.
>[1] Database BaseQuery: 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, 7 secs **
>> On Wed, 12 Nov 2003 15:15:54 -0600, "CD"
>> <mcdye1@.hotmail.nospam.com> wrote:
>> >Win2000sp4. SQL2k sp3
>> >
>> >One server I have the option selected to Attempt to repair any minor
>> >problems is checked on the Integrity checks. I know it is trying to
>repair
>> >something due to the fact it is trying to place in single user mode and
>> >can't due to connections.
>> >
>> >My problem is that I have ran dbcc checkdb and no errors were found. So
>> >what is exactly is it detecting and how do I detect the same? Certain
>trace
>> >flags or option need to be set with dbcc checkdb?
>> >
>> >TIA
>> >CD
>> >
>|||SORRY!
Thank you for the reply....I was tunneled vision due to the next error
message. What excatly 2 hours different.|||No problem...it's not exactly all that intuitive in terms of
the error message and could be seen as having a consistency
problem when there really isn't one.
-Sue
On Thu, 13 Nov 2003 10:57:42 -0600, "CD"
<mcdye1@.hotmail.nospam.com> wrote:
>SORRY!
>Thank you for the reply....I was tunneled vision due to the next error
>message. What excatly 2 hours different.
>
Showing posts with label checks. Show all posts
Showing posts with label checks. Show all posts
Friday, March 9, 2012
Integrity checks keeps failing
Hi All,
I am driving myself crazy trying to debug this one. My Integrity check
keeps failing due to:
Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
And
Test (emptySlotCnt == 0) failed. Values are 1 and 0.
I have been researching this all morning. I ran a simple select on the
offending table and it turned out there where 2 columns that had a date that
went beyond the year 9999. I have nulled out the offending columns since
these dates are meaningless in the table. I can now run a select on this
table and return all rows, but the integrity check still fails for the same
reasons.
Can anyone please tell me how to fix this error? restoring the DB is out of
the question since i dont have a clean one without this issue. I am new to
this company and this job has been failing for long before I got here.
TIA,
Joe
jaylou
It is unclear, please provide DDL+ sample data+ keys to test the problem
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> Hi All,
> I am driving myself crazy trying to debug this one. My Integrity check
> keeps failing due to:
> Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> And
> Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> I have been researching this all morning. I ran a simple select on the
> offending table and it turned out there where 2 columns that had a date
> that
> went beyond the year 9999. I have nulled out the offending columns since
> these dates are meaningless in the table. I can now run a select on this
> table and return all rows, but the integrity check still fails for the
> same
> reasons.
> Can anyone please tell me how to fix this error? restoring the DB is out
> of
> the question since i dont have a clean one without this issue. I am new
> to
> this company and this job has been failing for long before I got here.
> TIA,
> Joe
>
|||Can you tell me how to send you that info?
"Uri Dimant" wrote:
> jaylou
> It is unclear, please provide DDL+ sample data+ keys to test the problem
>
>
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
>
>
|||Post it here
CREATE TABEL tbl....
INSERT INTO tbl VALUES (.....
Desired result :
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:547DA248-751B-48FB-A5FC-B14D399554BC@.microsoft.com...[vbcol=seagreen]
> Can you tell me how to send you that info?
> "Uri Dimant" wrote:
I am driving myself crazy trying to debug this one. My Integrity check
keeps failing due to:
Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
And
Test (emptySlotCnt == 0) failed. Values are 1 and 0.
I have been researching this all morning. I ran a simple select on the
offending table and it turned out there where 2 columns that had a date that
went beyond the year 9999. I have nulled out the offending columns since
these dates are meaningless in the table. I can now run a select on this
table and return all rows, but the integrity check still fails for the same
reasons.
Can anyone please tell me how to fix this error? restoring the DB is out of
the question since i dont have a clean one without this issue. I am new to
this company and this job has been failing for long before I got here.
TIA,
Joe
jaylou
It is unclear, please provide DDL+ sample data+ keys to test the problem
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> Hi All,
> I am driving myself crazy trying to debug this one. My Integrity check
> keeps failing due to:
> Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> And
> Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> I have been researching this all morning. I ran a simple select on the
> offending table and it turned out there where 2 columns that had a date
> that
> went beyond the year 9999. I have nulled out the offending columns since
> these dates are meaningless in the table. I can now run a select on this
> table and return all rows, but the integrity check still fails for the
> same
> reasons.
> Can anyone please tell me how to fix this error? restoring the DB is out
> of
> the question since i dont have a clean one without this issue. I am new
> to
> this company and this job has been failing for long before I got here.
> TIA,
> Joe
>
|||Can you tell me how to send you that info?
"Uri Dimant" wrote:
> jaylou
> It is unclear, please provide DDL+ sample data+ keys to test the problem
>
>
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
>
>
|||Post it here
CREATE TABEL tbl....
INSERT INTO tbl VALUES (.....
Desired result :
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:547DA248-751B-48FB-A5FC-B14D399554BC@.microsoft.com...[vbcol=seagreen]
> Can you tell me how to send you that info?
> "Uri Dimant" wrote:
Integrity checks keeps failing
Hi All,
I am driving myself crazy trying to debug this one. My Integrity check
keeps failing due to:
Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
And
Test (emptySlotCnt == 0) failed. Values are 1 and 0.
I have been researching this all morning. I ran a simple select on the
offending table and it turned out there where 2 columns that had a date that
went beyond the year 9999. I have nulled out the offending columns since
these dates are meaningless in the table. I can now run a select on this
table and return all rows, but the integrity check still fails for the same
reasons.
Can anyone please tell me how to fix this error? restoring the DB is out of
the question since i dont have a clean one without this issue. I am new to
this company and this job has been failing for long before I got here.
TIA,
Joejaylou
It is unclear, please provide DDL+ sample data+ keys to test the problem
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> Hi All,
> I am driving myself crazy trying to debug this one. My Integrity check
> keeps failing due to:
> Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> And
> Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> I have been researching this all morning. I ran a simple select on the
> offending table and it turned out there where 2 columns that had a date
> that
> went beyond the year 9999. I have nulled out the offending columns since
> these dates are meaningless in the table. I can now run a select on this
> table and return all rows, but the integrity check still fails for the
> same
> reasons.
> Can anyone please tell me how to fix this error? restoring the DB is out
> of
> the question since i dont have a clean one without this issue. I am new
> to
> this company and this job has been failing for long before I got here.
> TIA,
> Joe
>|||Can you tell me how to send you that info?
"Uri Dimant" wrote:
> jaylou
> It is unclear, please provide DDL+ sample data+ keys to test the problem
>
>
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
>
>|||Post it here
CREATE TABEL tbl....
INSERT INTO tbl VALUES (.....
Desired result :
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:547DA248-751B-48FB-A5FC-B14D399554BC@.microsoft.com...[vbcol=seagreen]
> Can you tell me how to send you that info?
> "Uri Dimant" wrote:
>
I am driving myself crazy trying to debug this one. My Integrity check
keeps failing due to:
Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
And
Test (emptySlotCnt == 0) failed. Values are 1 and 0.
I have been researching this all morning. I ran a simple select on the
offending table and it turned out there where 2 columns that had a date that
went beyond the year 9999. I have nulled out the offending columns since
these dates are meaningless in the table. I can now run a select on this
table and return all rows, but the integrity check still fails for the same
reasons.
Can anyone please tell me how to fix this error? restoring the DB is out of
the question since i dont have a clean one without this issue. I am new to
this company and this job has been failing for long before I got here.
TIA,
Joejaylou
It is unclear, please provide DDL+ sample data+ keys to test the problem
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> Hi All,
> I am driving myself crazy trying to debug this one. My Integrity check
> keeps failing due to:
> Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> And
> Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> I have been researching this all morning. I ran a simple select on the
> offending table and it turned out there where 2 columns that had a date
> that
> went beyond the year 9999. I have nulled out the offending columns since
> these dates are meaningless in the table. I can now run a select on this
> table and return all rows, but the integrity check still fails for the
> same
> reasons.
> Can anyone please tell me how to fix this error? restoring the DB is out
> of
> the question since i dont have a clean one without this issue. I am new
> to
> this company and this job has been failing for long before I got here.
> TIA,
> Joe
>|||Can you tell me how to send you that info?
"Uri Dimant" wrote:
> jaylou
> It is unclear, please provide DDL+ sample data+ keys to test the problem
>
>
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
>
>|||Post it here
CREATE TABEL tbl....
INSERT INTO tbl VALUES (.....
Desired result :
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:547DA248-751B-48FB-A5FC-B14D399554BC@.microsoft.com...[vbcol=seagreen]
> Can you tell me how to send you that info?
> "Uri Dimant" wrote:
>
Integrity checks keeps failing
Hi All,
I am driving myself crazy trying to debug this one. My Integrity check
keeps failing due to:
Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
And
Test (emptySlotCnt == 0) failed. Values are 1 and 0.
I have been researching this all morning. I ran a simple select on the
offending table and it turned out there where 2 columns that had a date that
went beyond the year 9999. I have nulled out the offending columns since
these dates are meaningless in the table. I can now run a select on this
table and return all rows, but the integrity check still fails for the same
reasons.
Can anyone please tell me how to fix this error? restoring the DB is out of
the question since i dont have a clean one without this issue. I am new to
this company and this job has been failing for long before I got here.
TIA,
Joejaylou
It is unclear, please provide DDL+ sample data+ keys to test the problem
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> Hi All,
> I am driving myself crazy trying to debug this one. My Integrity check
> keeps failing due to:
> Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> And
> Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> I have been researching this all morning. I ran a simple select on the
> offending table and it turned out there where 2 columns that had a date
> that
> went beyond the year 9999. I have nulled out the offending columns since
> these dates are meaningless in the table. I can now run a select on this
> table and return all rows, but the integrity check still fails for the
> same
> reasons.
> Can anyone please tell me how to fix this error? restoring the DB is out
> of
> the question since i dont have a clean one without this issue. I am new
> to
> this company and this job has been failing for long before I got here.
> TIA,
> Joe
>|||Can you tell me how to send you that info?
"Uri Dimant" wrote:
> jaylou
> It is unclear, please provide DDL+ sample data+ keys to test the problem
>
>
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> > Hi All,
> > I am driving myself crazy trying to debug this one. My Integrity check
> > keeps failing due to:
> > Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> > And
> > Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> >
> > I have been researching this all morning. I ran a simple select on the
> > offending table and it turned out there where 2 columns that had a date
> > that
> > went beyond the year 9999. I have nulled out the offending columns since
> > these dates are meaningless in the table. I can now run a select on this
> > table and return all rows, but the integrity check still fails for the
> > same
> > reasons.
> >
> > Can anyone please tell me how to fix this error? restoring the DB is out
> > of
> > the question since i dont have a clean one without this issue. I am new
> > to
> > this company and this job has been failing for long before I got here.
> >
> > TIA,
> > Joe
> >
>
>|||Post it here
CREATE TABEL tbl....
INSERT INTO tbl VALUES (.....
Desired result :
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:547DA248-751B-48FB-A5FC-B14D399554BC@.microsoft.com...
> Can you tell me how to send you that info?
> "Uri Dimant" wrote:
>> jaylou
>> It is unclear, please provide DDL+ sample data+ keys to test the problem
>>
>>
>>
>>
>> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
>> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
>> > Hi All,
>> > I am driving myself crazy trying to debug this one. My Integrity check
>> > keeps failing due to:
>> > Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
>> > And
>> > Test (emptySlotCnt == 0) failed. Values are 1 and 0.
>> >
>> > I have been researching this all morning. I ran a simple select on the
>> > offending table and it turned out there where 2 columns that had a date
>> > that
>> > went beyond the year 9999. I have nulled out the offending columns
>> > since
>> > these dates are meaningless in the table. I can now run a select on
>> > this
>> > table and return all rows, but the integrity check still fails for the
>> > same
>> > reasons.
>> >
>> > Can anyone please tell me how to fix this error? restoring the DB is
>> > out
>> > of
>> > the question since i dont have a clean one without this issue. I am
>> > new
>> > to
>> > this company and this job has been failing for long before I got here.
>> >
>> > TIA,
>> > Joe
>> >
>>
I am driving myself crazy trying to debug this one. My Integrity check
keeps failing due to:
Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
And
Test (emptySlotCnt == 0) failed. Values are 1 and 0.
I have been researching this all morning. I ran a simple select on the
offending table and it turned out there where 2 columns that had a date that
went beyond the year 9999. I have nulled out the offending columns since
these dates are meaningless in the table. I can now run a select on this
table and return all rows, but the integrity check still fails for the same
reasons.
Can anyone please tell me how to fix this error? restoring the DB is out of
the question since i dont have a clean one without this issue. I am new to
this company and this job has been failing for long before I got here.
TIA,
Joejaylou
It is unclear, please provide DDL+ sample data+ keys to test the problem
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> Hi All,
> I am driving myself crazy trying to debug this one. My Integrity check
> keeps failing due to:
> Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> And
> Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> I have been researching this all morning. I ran a simple select on the
> offending table and it turned out there where 2 columns that had a date
> that
> went beyond the year 9999. I have nulled out the offending columns since
> these dates are meaningless in the table. I can now run a select on this
> table and return all rows, but the integrity check still fails for the
> same
> reasons.
> Can anyone please tell me how to fix this error? restoring the DB is out
> of
> the question since i dont have a clean one without this issue. I am new
> to
> this company and this job has been failing for long before I got here.
> TIA,
> Joe
>|||Can you tell me how to send you that info?
"Uri Dimant" wrote:
> jaylou
> It is unclear, please provide DDL+ sample data+ keys to test the problem
>
>
>
>
> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
> > Hi All,
> > I am driving myself crazy trying to debug this one. My Integrity check
> > keeps failing due to:
> > Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
> > And
> > Test (emptySlotCnt == 0) failed. Values are 1 and 0.
> >
> > I have been researching this all morning. I ran a simple select on the
> > offending table and it turned out there where 2 columns that had a date
> > that
> > went beyond the year 9999. I have nulled out the offending columns since
> > these dates are meaningless in the table. I can now run a select on this
> > table and return all rows, but the integrity check still fails for the
> > same
> > reasons.
> >
> > Can anyone please tell me how to fix this error? restoring the DB is out
> > of
> > the question since i dont have a clean one without this issue. I am new
> > to
> > this company and this job has been failing for long before I got here.
> >
> > TIA,
> > Joe
> >
>
>|||Post it here
CREATE TABEL tbl....
INSERT INTO tbl VALUES (.....
Desired result :
"jaylou" <jaylou@.discussions.microsoft.com> wrote in message
news:547DA248-751B-48FB-A5FC-B14D399554BC@.microsoft.com...
> Can you tell me how to send you that info?
> "Uri Dimant" wrote:
>> jaylou
>> It is unclear, please provide DDL+ sample data+ keys to test the problem
>>
>>
>>
>>
>> "jaylou" <jaylou@.discussions.microsoft.com> wrote in message
>> news:F5825753-E60C-4062-9361-859BBFA5E9C0@.microsoft.com...
>> > Hi All,
>> > I am driving myself crazy trying to debug this one. My Integrity check
>> > keeps failing due to:
>> > Test (m_freeCnt == freeCnt) failed. Values are 7798 and 8094.
>> > And
>> > Test (emptySlotCnt == 0) failed. Values are 1 and 0.
>> >
>> > I have been researching this all morning. I ran a simple select on the
>> > offending table and it turned out there where 2 columns that had a date
>> > that
>> > went beyond the year 9999. I have nulled out the offending columns
>> > since
>> > these dates are meaningless in the table. I can now run a select on
>> > this
>> > table and return all rows, but the integrity check still fails for the
>> > same
>> > reasons.
>> >
>> > Can anyone please tell me how to fix this error? restoring the DB is
>> > out
>> > of
>> > the question since i dont have a clean one without this issue. I am
>> > new
>> > to
>> > this company and this job has been failing for long before I got here.
>> >
>> > TIA,
>> > Joe
>> >
>>
Integrity Checks job failing
Hi,
SQl Server 7
I have Daily User DB Integrity Checks job running daily
From past 2 days i am getting below error.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 35 consistency errors in table 'Prod_Hist' (object ID 2098106515).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 99 consistency errors in database 'Ucatalog'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Ucatalog repair_fast).
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Please suggest..
Thanks in Advance
AdilHi,
SQl Server 7
I have Daily User DB Integrity Checks job running daily
From past 2 days i am getting below error.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 35 consistency errors in table 'Prod_Hist' (object ID 2098106515).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 99 consistency errors in database 'Ucatalog'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Ucatalog repair_fast).
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Please suggest..
Thanks in Advance
Adil
1. Contact your DBA with the stated information and ask for his help or
2. Fix the table and database corruption ... either by running checkdb with the repair option stated or restore from a previous backup. Checkdb is telling you that you will probably lose data by allowing it to repair the corruption ... be prepared.
SQl Server 7
I have Daily User DB Integrity Checks job running daily
From past 2 days i am getting below error.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 35 consistency errors in table 'Prod_Hist' (object ID 2098106515).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 99 consistency errors in database 'Ucatalog'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Ucatalog repair_fast).
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Please suggest..
Thanks in Advance
AdilHi,
SQl Server 7
I have Daily User DB Integrity Checks job running daily
From past 2 days i am getting below error.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 35 consistency errors in table 'Prod_Hist' (object ID 2098106515).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 99 consistency errors in database 'Ucatalog'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Ucatalog repair_fast).
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator.
Please suggest..
Thanks in Advance
Adil
1. Contact your DBA with the stated information and ask for his help or
2. Fix the table and database corruption ... either by running checkdb with the repair option stated or restore from a previous backup. Checkdb is telling you that you will probably lose data by allowing it to repair the corruption ... be prepared.
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.
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 job causing SQL 7 database to enter single-user mode
Hi,
I've encountered with very strange problem on this issue on one of my my SQL 7 Servers.
The integrity checks job on the database failed, and caused the database to enter the single user mode, thus preventing applications to access the database. I had to manually switch the database to normal mode to repair the problem.
Right now, every time i try to run the integrity checks job, it fails and causes the database to enter the single user mode again.
Any ideas how to solve the problem?
Thanks in advance,
BarakThis looks like a known issue. Have you seen this?
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B259551
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"Barak Turovsky" <barak.turovsky@.comverse.com> wrote in message
news:7DA294DF-065F-431A-91D6-AA23B4AA50CE@.microsoft.com...
Hi,
I've encountered with very strange problem on this issue on one of my my SQL
7 Servers.
The integrity checks job on the database failed, and caused the database to
enter the single user mode, thus preventing applications to access the
database. I had to manually switch the database to normal mode to repair the
problem.
Right now, every time i try to run the integrity checks job, it fails and
causes the database to enter the single user mode again.
Any ideas how to solve the problem?
Thanks in advance,
Barak
I've encountered with very strange problem on this issue on one of my my SQL 7 Servers.
The integrity checks job on the database failed, and caused the database to enter the single user mode, thus preventing applications to access the database. I had to manually switch the database to normal mode to repair the problem.
Right now, every time i try to run the integrity checks job, it fails and causes the database to enter the single user mode again.
Any ideas how to solve the problem?
Thanks in advance,
BarakThis looks like a known issue. Have you seen this?
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B259551
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
What hardware is your SQL Server running on?
http://vyaskn.tripod.com/poll.htm
"Barak Turovsky" <barak.turovsky@.comverse.com> wrote in message
news:7DA294DF-065F-431A-91D6-AA23B4AA50CE@.microsoft.com...
Hi,
I've encountered with very strange problem on this issue on one of my my SQL
7 Servers.
The integrity checks job on the database failed, and caused the database to
enter the single user mode, thus preventing applications to access the
database. I had to manually switch the database to normal mode to repair the
problem.
Right now, every time i try to run the integrity checks job, it fails and
causes the database to enter the single user mode again.
Any ideas how to solve the problem?
Thanks in advance,
Barak
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?
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--
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?
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,
Jamie
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
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
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/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
>
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...
>
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:
>
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:
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:
Subscribe to:
Posts (Atom)