Errors while running DBCC CheckDb

I get the following errors when DBCC CheckDb is executed
on 'fmcomp003' database :
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1881) with latch type SH.
sysindexes failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
Values are 82 and 0.
DBCC results for 'fmcomp003'.Hi
DBCC CHECKDB has few arguments which you can use in this case
For more details please refer to BOL.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Hi,
I didn't understand the error as well as the severity of
the error. And please tell what is BOL.
Amit Chaudhary
>--Original Message--
>Hi
>DBCC CHECKDB has few arguments which you can use in this
case
>For more details please refer to BOL.
>
>"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
wrote in message
> news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
SH.[vbcol=seagreen]
row[vbcol=seagreen]
>
>.
>|||Amit
Seems your table is corrupted. Do you have a last backup of the database?
Books OnLine comes with SQL Server installation.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2afca01c467e7$5fbe4d70$a401280a@.phx
.gbl...[vbcol=seagreen]
> Hi,
> I didn't understand the error as well as the severity of
> the error. And please tell what is BOL.
> Amit Chaudhary
> case
> wrote in message
> SH.
> row|||BOL is SQL Server documentation (Books On Line)..
Open BOL and search from the message# ( which is the SQL Error number)
8966...
You can also often get good information by simply googling the error number
as well...
To find the table name (from object id 2)
in query analyzer, use the database and
select object_name(2)
Object IDs < 100 are system tables..
IndexID of 0 means it is a table with no clustered index...
You will probably have to restore... You can also open a call to Microsoft
product Support ( PSS) ... I think the call now costs about $249.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||> And please tell what is BOL.
Books OnLine.
http://www.aspfaq.com/2229
http://www.aspfaq.com/
(Reverse address to reply.)|||What is the version of SQL used here?
If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if not
check event viewer for any information on hardware issues on the SQL server
.
--
Satya SKJ
"Amit Chaudhary" wrote:

> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Your sysindexes table has a corruption at the leaf level of the clustered
index. This is not repairable and your only option is to restore from your
last known good backup.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx
.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>|||Repair cannot fix this error.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Satya SKJ" <satyaskj@.yahoo.co.uk> wrote in message
news:53F0C4CC-F7AE-4F72-8AE3-256FEB2C169B@.microsoft.com...
> What is the version of SQL used here?
> If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
> Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if
not check event viewer for any information on hardware issues on the SQL
server.[vbcol=seagreen]
> --
> --
> Satya SKJ
>
> "Amit Chaudhary" wrote:
>

Errors while running DBCC CheckDb

I get the following errors when DBCC CheckDb is executed
on 'fmcomp003' database :
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:1881) with latch type SH.
sysindexes failed.
Server: Msg 8944, Level 16, State 1, Line 1
Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
Values are 82 and 0.
DBCC results for 'fmcomp003'.
Hi
DBCC CHECKDB has few arguments which you can use in this case
For more details please refer to BOL.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||Hi,
I didn't understand the error as well as the severity of
the error. And please tell what is BOL.
Amit Chaudhary
>--Original Message--
>Hi
>DBCC CHECKDB has few arguments which you can use in this
case
>For more details please refer to BOL.
>
>"Amit Chaudhary" <anonymous@.discussions.microsoft.com>
wrote in message[vbcol=seagreen]
>news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
SH.[vbcol=seagreen]
row
>
>.
>
|||Amit
Seems your table is corrupted. Do you have a last backup of the database?
Books OnLine comes with SQL Server installation.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2afca01c467e7$5fbe4d70$a401280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> I didn't understand the error as well as the severity of
> the error. And please tell what is BOL.
> Amit Chaudhary
> case
> wrote in message
> SH.
> row
|||BOL is SQL Server documentation (Books On Line)..
Open BOL and search from the message# ( which is the SQL Error number)
8966...
You can also often get good information by simply googling the error number
as well...
To find the table name (from object id 2)
in query analyzer, use the database and
select object_name(2)
Object IDs < 100 are system tables..
IndexID of 0 means it is a table with no clustered index...
You will probably have to restore... You can also open a call to Microsoft
product Support ( PSS) ... I think the call now costs about $249.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||> And please tell what is BOL.
Books OnLine.
http://www.aspfaq.com/2229
http://www.aspfaq.com/
(Reverse address to reply.)
|||What is the version of SQL used here?
If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if not check event viewer for any information on Hardware issues on the SQL server.
--
Satya SKJ
"Amit Chaudhary" wrote:

> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||Your sysindexes table has a corruption at the leaf level of the clustered
index. This is not repairable and your only option is to restore from your
last known good backup.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Amit Chaudhary" <anonymous@.discussions.microsoft.com> wrote in message
news:2b81b01c467e1$63299ab0$a301280a@.phx.gbl...
> I get the following errors when DBCC CheckDb is executed
> on 'fmcomp003' database :
> Server: Msg 8966, Level 16, State 1, Line 1
> Could not read and latch page (1:1881) with latch type SH.
> sysindexes failed.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table Corrupt: Object ID 2, index ID 0, page (1:1881), row
> 14. Test (ColumnOffsets <= (nextRec - pRec)) failed.
> Values are 82 and 0.
> DBCC results for 'fmcomp003'.
>
|||Repair cannot fix this error.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Satya SKJ" <satyaskj@.yahoo.co.uk> wrote in message
news:53F0C4CC-F7AE-4F72-8AE3-256FEB2C169B@.microsoft.com...
> What is the version of SQL used here?
> If its ver.7 then ensure to apply latest Service pack 4 to the SQL.
> Also run DBCC CHECK with REPAIR clause in order to resolve the issue, if
not check event viewer for any information on Hardware issues on the SQL
server.[vbcol=seagreen]
> --
> --
> Satya SKJ
>
> "Amit Chaudhary" wrote:
sql

Error: Server: Msg 1101, Level 17, State 10 when I run script

Hi All,
I can't not run the query to update data but it raice an error as below:
"Server: Msg 1101, Level 17, State 10, Line 1
Could not allocate new page for database 'TEMPDB'. There are no more pages
available in filegroup DEFAULT. Space can be created by dropping objects,
adding additional files, or allowing file growth."
HDD free space: 5GB
RAM: 1GB
CPU: 2.8MHz
SQL server 2000
Windows 2000 server
What should I do?
Please advice me on this.
Thanks in advance,
TNAs per the error message: Increate the size for your tempdb database (data,
not log).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TN" <TN@.discussions.microsoft.com> wrote in message
news:72E79234-7E66-4C0F-9198-A2564A99BEE4@.microsoft.com...
> Hi All,
> I can't not run the query to update data but it raice an error as below:
> "Server: Msg 1101, Level 17, State 10, Line 1
> Could not allocate new page for database 'TEMPDB'. There are no more pages
> available in filegroup DEFAULT. Space can be created by dropping objects,
> adding additional files, or allowing file growth."
> HDD free space: 5GB
> RAM: 1GB
> CPU: 2.8MHz
> SQL server 2000
> Windows 2000 server
> What should I do?
> Please advice me on this.
> Thanks in advance,
> TN
>|||My tempdb is umlimited file growth.
"Tibor Karaszi" wrote:

> As per the error message: Increate the size for your tempdb database (data
, not log).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "TN" <TN@.discussions.microsoft.com> wrote in message
> news:72E79234-7E66-4C0F-9198-A2564A99BEE4@.microsoft.com...
>
>|||Sometimes autogrow doesn't grow the files fast enough for the operation that
needs the storage.
Solution is to pre-allocate storage.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TN" <TN@.discussions.microsoft.com> wrote in message
news:473EFAC4-F9E0-4CE8-A895-C146BCE11C6C@.microsoft.com...[vbcol=seagreen]
> My tempdb is umlimited file growth.
> "Tibor Karaszi" wrote:
>

Error: Server: Msg 1101, Level 17, State 10 when I run script

Hi All,
I can't not run the query to update data but it raice an error as below:
"Server: Msg 1101, Level 17, State 10, Line 1
Could not allocate new page for database 'TEMPDB'. There are no more pages
available in filegroup DEFAULT. Space can be created by dropping objects,
adding additional files, or allowing file growth."
HDD free space: 5GB
RAM: 1GB
CPU: 2.8MHz
SQL server 2000
Windows 2000 server
What should I do?
Please advice me on this.
Thanks in advance,
TN
As per the error message: Increate the size for your tempdb database (data, not log).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TN" <TN@.discussions.microsoft.com> wrote in message
news:72E79234-7E66-4C0F-9198-A2564A99BEE4@.microsoft.com...
> Hi All,
> I can't not run the query to update data but it raice an error as below:
> "Server: Msg 1101, Level 17, State 10, Line 1
> Could not allocate new page for database 'TEMPDB'. There are no more pages
> available in filegroup DEFAULT. Space can be created by dropping objects,
> adding additional files, or allowing file growth."
> HDD free space: 5GB
> RAM: 1GB
> CPU: 2.8MHz
> SQL server 2000
> Windows 2000 server
> What should I do?
> Please advice me on this.
> Thanks in advance,
> TN
>
|||My tempdb is umlimited file growth.
"Tibor Karaszi" wrote:

> As per the error message: Increate the size for your tempdb database (data, not log).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "TN" <TN@.discussions.microsoft.com> wrote in message
> news:72E79234-7E66-4C0F-9198-A2564A99BEE4@.microsoft.com...
>
>
|||Sometimes autogrow doesn't grow the files fast enough for the operation that needs the storage.
Solution is to pre-allocate storage.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"TN" <TN@.discussions.microsoft.com> wrote in message
news:473EFAC4-F9E0-4CE8-A895-C146BCE11C6C@.microsoft.com...[vbcol=seagreen]
> My tempdb is umlimited file growth.
> "Tibor Karaszi" wrote: