I received "msg 515" from several tables when I ran DBCC
checktable or checkdb.
I checked all system tables to see if there were any
corrupt tables but they were all fine.
Tempdb is not full and may grow another 120GB.
In tables which returned "msg 515" there were no null
entries where the columns do not allow null value.

I do not know when some tables were corrupt since I do not
run DBCC so often as it takes over 20 hours.
I might get same message even I restore the database from
one of the backup.

Anyone know anything more about msg 515? How to deal with
it??

***Here is the return message from DBCC*****
Server: Msg 515, Level 16, State 2, Line 3
Cannot insert the value NULL into column '', table '';
column does not allow nulls. INSERT fails.
Server: Msg 8921, Level 16, State 1, Line 1
CHECKTABLE terminated. A failure was detected while
collecting facts. Possibly tempdb out of space or a system
table is corrupt. Check previous errors.
CHECKTABLE found 0 allocation errors and 1 consistency
errors not associated with any single object.
repair_fast is the minimum repair level for the errors
found by DBCC CHECKTABLE (UCDW_PROD.dbo.FYSIKER ).

Report this post to a moderator

Have you tried running the sp_checkdbtempsize procedure to find out how much
tempdb space is required by CHECKDB to be able to run successfully? I think
you're running out of space while CHECKDB is running.

--
Paul Randal
DBCC Technical Lead, SQL Server Storage Engine
Microsoft, Redmond, WA

This posting is provided "AS IS" with no warranties, and confers no rights.
"didi" <carlsdootar@hotmail.com> wrote in message
news:6f5b01c284be$084864d0$2ae
2c90a@phx.gbl...
> I received "msg 515" from several tables when I ran DBCC
> checktable or checkdb.
> I checked all system tables to see if there were any
> corrupt tables but they were all fine.
> Tempdb is not full and may grow another 120GB.
> In tables which returned "msg 515" there were no null
> entries where the columns do not allow null value.
>
> I do not know when some tables were corrupt since I do not
> run DBCC so often as it takes over 20 hours.
> I might get same message even I restore the database from
> one of the backup.
>
> Anyone know anything more about msg 515? How to deal with
> it??
>
> ***Here is the return message from DBCC*****
> Server: Msg 515, Level 16, State 2, Line 3
> Cannot insert the value NULL into column '', table '';
> column does not allow nulls. INSERT fails.
> Server: Msg 8921, Level 16, State 1, Line 1
> CHECKTABLE terminated. A failure was detected while
> collecting facts. Possibly tempdb out of space or a system
> table is corrupt. Check previous errors.
> CHECKTABLE found 0 allocation errors and 1 consistency
> errors not associated with any single object.
> repair_fast is the minimum repair level for the errors
> found by DBCC CHECKTABLE (UCDW_PROD.dbo.FYSIKER ).
>

Report this post to a moderator

The database is in SQL 7 enterprise.
I could not find "sp_checkdbtempsize procedure"
Is this one of the original stored procedure?



>-----Original Message-----
>Have you tried running the sp_checkdbtempsize procedure
to find out how much
>tempdb space is required by CHECKDB to be able to run
successfully? I think
>you're running out of space while CHECKDB is running.
>
>--
>Paul Randal
>DBCC Technical Lead, SQL Server Storage Engine
>Microsoft, Redmond, WA
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"didi" <carlsdootar@hotmail.com> wrote in message
> news:6f5b01c284be$084864d0$2ae
2c90a@phx.gbl...
>> I received "msg 515" from several tables when I ran DBCC
>> checktable or checkdb.
>> I checked all system tables to see if there were any
>> corrupt tables but they were all fine.
>> Tempdb is not full and may grow another 120GB.
>> In tables which returned "msg 515" there were no null
>> entries where the columns do not allow null value.
>>
>> I do not know when some tables were corrupt since I do
not
>> run DBCC so often as it takes over 20 hours.
>> I might get same message even I restore the database
from
>> one of the backup.
>>
>> Anyone know anything more about msg 515? How to deal
with
>> it??
>>
>> ***Here is the return message from DBCC*****
>> Server: Msg 515, Level 16, State 2, Line 3
>> Cannot insert the value NULL into column '', table '';
>> column does not allow nulls. INSERT fails.
>> Server: Msg 8921, Level 16, State 1, Line 1
>> CHECKTABLE terminated. A failure was detected while
>> collecting facts. Possibly tempdb out of space or a
system
>> table is corrupt. Check previous errors.
>> CHECKTABLE found 0 allocation errors and 1 consistency
>> errors not associated with any single object.
>> repair_fast is the minimum repair level for the errors
>> found by DBCC CHECKTABLE (UCDW_PROD.dbo.FYSIKER ).
>>
>
>
>.
>

Report this post to a moderator

I found sp_checkdbtempsize.
The sp returns different values depend in which database I
run this query.
I would like to know what this returned means.
It obviously is not the size of TEPMPDB, right?
And which size is enough for certain size of database?

Thank you.
>-----Original Message-----
>Have you tried running the sp_checkdbtempsize procedure
to find out how much
>tempdb space is required by CHECKDB to be able to run
successfully? I think
>you're running out of space while CHECKDB is running.
>
>--
>Paul Randal
>DBCC Technical Lead, SQL Server Storage Engine
>Microsoft, Redmond, WA
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"didi" <carlsdootar@hotmail.com> wrote in message
> news:6f5b01c284be$084864d0$2ae
2c90a@phx.gbl...
>> I received "msg 515" from several tables when I ran DBCC
>> checktable or checkdb.
>> I checked all system tables to see if there were any
>> corrupt tables but they were all fine.
>> Tempdb is not full and may grow another 120GB.
>> In tables which returned "msg 515" there were no null
>> entries where the columns do not allow null value.
>>
>> I do not know when some tables were corrupt since I do
not
>> run DBCC so often as it takes over 20 hours.
>> I might get same message even I restore the database
from
>> one of the backup.
>>
>> Anyone know anything more about msg 515? How to deal
with
>> it??
>>
>> ***Here is the return message from DBCC*****
>> Server: Msg 515, Level 16, State 2, Line 3
>> Cannot insert the value NULL into column '', table '';
>> column does not allow nulls. INSERT fails.
>> Server: Msg 8921, Level 16, State 1, Line 1
>> CHECKTABLE terminated. A failure was detected while
>> collecting facts. Possibly tempdb out of space or a
system
>> table is corrupt. Check previous errors.
>> CHECKTABLE found 0 allocation errors and 1 consistency
>> errors not associated with any single object.
>> repair_fast is the minimum repair level for the errors
>> found by DBCC CHECKTABLE (UCDW_PROD.dbo.FYSIKER ).
>>
>
>
>.
>

Report this post to a moderator

If you want to run dbcc checkdb agsinst database 'foo', run
sp_checkdbtempsize, giving it 'foo'. The return value is the amount of space
(in Kb I think) that DBCC needs to have available in tempdb, to be able to
run dbcc checkdb against database 'foo'.

If it returns, say 150 Mb, and you only have 120 Mb in tempdb, the odds are
that it will run out of space while running dbcc checkdb.

--
Paul Randal
DBCC Technical Lead, SQL Server Storage Engine
Microsoft, Redmond, WA

This posting is provided "AS IS" with no warranties, and confers no rights.
"didi" <carlsdottar@hotmail.com> wrote in message
news:4df101c2859f$aabe2ec0$95e
62ecf@tkmsftngxs02...
> I found sp_checkdbtempsize.
> The sp returns different values depend in which database I
> run this query.
> I would like to know what this returned means.
> It obviously is not the size of TEPMPDB, right?
> And which size is enough for certain size of database?
>
> Thank you.
> >-----Original Message-----
> >Have you tried running the sp_checkdbtempsize procedure
> to find out how much
> >tempdb space is required by CHECKDB to be able to run
> successfully? I think
> >you're running out of space while CHECKDB is running.
> >
> >--
> >Paul Randal
> >DBCC Technical Lead, SQL Server Storage Engine
> >Microsoft, Redmond, WA
> >
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >"didi" <carlsdootar@hotmail.com> wrote in message
> > news:6f5b01c284be$084864d0$2ae
2c90a@phx.gbl...
> >> I received "msg 515" from several tables when I ran DBCC
> >> checktable or checkdb.
> >> I checked all system tables to see if there were any
> >> corrupt tables but they were all fine.
> >> Tempdb is not full and may grow another 120GB.
> >> In tables which returned "msg 515" there were no null
> >> entries where the columns do not allow null value.
> >>
> >> I do not know when some tables were corrupt since I do
> not
> >> run DBCC so often as it takes over 20 hours.
> >> I might get same message even I restore the database
> from
> >> one of the backup.
> >>
> >> Anyone know anything more about msg 515? How to deal
> with
> >> it??
> >>
> >> ***Here is the return message from DBCC*****
> >> Server: Msg 515, Level 16, State 2, Line 3
> >> Cannot insert the value NULL into column '', table '';
> >> column does not allow nulls. INSERT fails.
> >> Server: Msg 8921, Level 16, State 1, Line 1
> >> CHECKTABLE terminated. A failure was detected while
> >> collecting facts. Possibly tempdb out of space or a
> system
> >> table is corrupt. Check previous errors.
> >> CHECKTABLE found 0 allocation errors and 1 consistency
> >> errors not associated with any single object.
> >> repair_fast is the minimum repair level for the errors
> >> found by DBCC CHECKTABLE (UCDW_PROD.dbo.FYSIKER ).
> >>
> >
> >
> >.
> >

Report this post to a moderator