Friday, March 30, 2012

I'd like to get a good book of SQL...

Would all of you give me a suggestion of valuable book in terms of SQL ?

I confused what kind of SQL book is going to be good for me to study since

I begin to jump into MS-SQL...

Furthermore, I'd know that various level of book as begginer, intermediate , advance...

Thanks for your help in advance..

In my opinion the best T-SQL book is

The Guru's Guide to Transact-SQL
by Ken Henderson
http://www.amazon.com/exec/obidos/tg/detail/-/0201615762/ref=ase_sql08-20/102-4703055-5891314?v=glance&s=books

Although Ken's book doesn't deal with SQL Server 2005 you should definitely get it

You can also get Pro SQL server 2005

http://www.amazon.com/exec/obidos/ASIN/1590594770/sql08-20/102-5735017-0910517?%5Fencoding=UTF8&camp=1789&link%5Fcode=xm2 In addition to Ken's book since Pro SQL server 2005 deals with the new stuff in SQL server 2005 only

Denis the SQL Menace

http://sqlservercode.blogspot.com/

|||

I started out with Microsoft SQL Server 2005 - A Beginner's Guide by Dusan Petkovic. (ISBN 0072260939) pub. McGraw Hill.

I am a beginner to SQL Server 2005 and this book has helped quite a bit.

|||

whats better than free

http://blog.pinpub.com/archives/sqlblog/2006/01/more_sample_cha.html

sql

Id getting generated differently

Hi,

I created a PDA application with a database, which has a table with a uniqueidentifier field and primarykey.

While doing the bulk insert from dataset into sql mobile database, It is inserting the record but it is not inserting the id which was entered into the sql server 2005 database, instead the id by creating a new id and the code is as below.

conAdap = new SqlCeDataAdapter(strQuery, conSqlceConnection);

SqlCeCommandBuilder cmdBuilder = new SqlCeCommandBuilder(conAdap);

conAdap.Fill(dsData);

int r =conAdap.Update(dsData);

Please help me.

Thank you,

Prashant

Hi Prashant - I'm not sure I understand your issue. Could you explain in more detail and also give me somee information about the schema of the table itself? I'm interested in the list of columns, their types, PK, FKs, Indexes, and default values you have assigned on columns.

I'm also interested to know if the table is the product of an RDA pull with tracking on or merge replication article.

thanks,

Darren

ID for New record

Hi,
How can I insert a new record in sql table and retrun the ID of that reocrd using a stored procedure?
Thanks,From Books Online:

INSERT INTO jobs (job_desc,min_lvl,max_lvl)
VALUES ('Accountant',12,125)
SELECT @.@.IDENTITY AS 'Identity'

In stored proc:

create procedure sp_Test

@.outputvalue int output
as

INSERT INTO jobs (job_desc,min_lvl,max_lvl)
VALUES ('Accountant',12,125)
SELECT @.outputvalue = @.@.IDENTITY|||Thanks DMWCincy.|||Watch out fot @.@.IDENTITY, better use SCOPE_IDENTITY() besuase @.@.IDENTITY will return the last increment for the table, not necessarily the one that was generated by you transaction.

ID Field Reset

This morning I made a change to two tables in my live system. All I did was add a new column in each called 'suspense' with a data type of bit and a default value of '0'.

When the users started using the system they noticed that the record ID numbers had reset and were starting from 1 and going up 2, 3, 4 etc. The last good id number was about 20500. The id columns are set as primary key with identity and increment of 1.

This shouldn't happen should it? Is it a bug? I never touched the ID column, just added the new one.I bet you made the change using Enterprise Mangler. EM tends to make these changes not with a simple alter table add column, but with a drop and re-create of the table. You can try running DBCC CHECKIDENT(table) on the table, which should reset the identity column nicely.|||That's interesting. I am going to test that on my test system now to see what happens.

Thanks!

ID Edition? General MS SQL training?

I have two questions.

First is there an easy way to tell what
edition of MS SQL Server is on a machine?
I found some code that is supposed to do
this, but if I put that code into the query
analyzer, it doesn't work. (Doesn't look
like SQL query in any case.)

A more general question: Education about SQL.

I have an MS in biostats so I'm not totally
computer illiterate, but I've never programmed
anything GUI.

Thanks for any answers

Michael Young<mcl2@.vms.cis.pitt.edu> wrote in message
news:c5eton$kp4$1@.usenet01.srv.cis.pitt.edu...
> I have two questions.
> First is there an easy way to tell what
> edition of MS SQL Server is on a machine?
> I found some code that is supposed to do
> this, but if I put that code into the query
> analyzer, it doesn't work. (Doesn't look
> like SQL query in any case.)
> A more general question: Education about SQL.
> I have an MS in biostats so I'm not totally
> computer illiterate, but I've never programmed
> anything GUI.
> Thanks for any answers
> Michael Young

SELECT @.@.VERSION
SELECT SERVERPROPERTY('Edition')

The second one is only in SQL2000 only. As for education, you might want to
start with some general books on databases and the SQL language, although
Microsoft's own training material is usually pretty good. You may find some
useful information here:

http://vyaskn.tripod.com/sqlbooks.htm

Simon|||<mcl2@.vms.cis.pitt.edu> wrote in message
news:c5eton$kp4$1@.usenet01.srv.cis.pitt.edu...
> I have two questions.
> First is there an easy way to tell what
> edition of MS SQL Server is on a machine?
> I found some code that is supposed to do
> this, but if I put that code into the query
> analyzer, it doesn't work. (Doesn't look
> like SQL query in any case.)
> A more general question: Education about SQL.
> I have an MS in biostats so I'm not totally
> computer illiterate, but I've never programmed
> anything GUI.
> Thanks for any answers
> Michael Young

SELECT @.@.VERSION
SELECT SERVERPROPERTY('Edition')

The second one is only in SQL2000 only. As for education, you might want to
start with some general books on databases and the SQL language, although
Microsoft's own training material is usually pretty good. You may find some
useful information here:

http://vyaskn.tripod.com/sqlbooks.htm

Simon

ID Creation/ASP/SQL Server

Using SQL Server with ASP for an intranet website.
I'm generating a ID using a user defined function. (getting the Maximum and
adding 1 to get a new ID )
During testing i have got 2 similar ids (example: 31000,31000) for 2 records
when there is concurrent access to a website
here i need to track the ID generated,manipulate and convert into string
format (example: U31000_CTF_FILE)
so im generating it thru function.
is there any other best way to generate & track IDs.
Note: im not using any stored procedures moreover i want to use normal ASP
code only
please help
-dnkHi
You can try somethimg like that
CREATE PROC spNewIds
AS
DECLARE @.new_id INT
BEGIN TRANSACTION
SELECT @.new_id =COALESCE(MAX(Id)+1,0) FROM MyTable WITH (UPDLOCK,HOLDLOCK)
INSERT INTO AnotherTable (colname) VALUES (@.new_id )
COMMIT TRANSACTION
"DNKMCA" <dnk@.msn.com> wrote in message
news:uPeCLiOFGHA.916@.TK2MSFTNGP10.phx.gbl...
> Using SQL Server with ASP for an intranet website.
> I'm generating a ID using a user defined function. (getting the Maximum
> and
> adding 1 to get a new ID )
> During testing i have got 2 similar ids (example: 31000,31000) for 2
> records
> when there is concurrent access to a website
> here i need to track the ID generated,manipulate and convert into string
> format (example: U31000_CTF_FILE)
> so im generating it thru function.
> is there any other best way to generate & track IDs.
> Note: im not using any stored procedures moreover i want to use normal
> ASP
> code only
> please help
> -dnk
>|||Why don't you just have a dummy table with an IDENTITY column?
CREATE TABLE dbo.MyTable(ID INT IDENTITY(1,1))
Now In the ASP code,
set rs = conn.execute("SET NOCOUNT ON; INSERT dbo.MyTable DEFAULT VALUES;
SELECT SCOPE_IDENTITY()")
Response.Write rs(0)
Though I'm not sure I understand the objection to using stored procedures,
or what you mean by "track IDs"...
"DNKMCA" <dnk@.msn.com> wrote in message
news:uPeCLiOFGHA.916@.TK2MSFTNGP10.phx.gbl...
> Using SQL Server with ASP for an intranet website.
> I'm generating a ID using a user defined function. (getting the Maximum
> and
> adding 1 to get a new ID )
> During testing i have got 2 similar ids (example: 31000,31000) for 2
> records
> when there is concurrent access to a website
> here i need to track the ID generated,manipulate and convert into string
> format (example: U31000_CTF_FILE)
> so im generating it thru function.
> is there any other best way to generate & track IDs.
> Note: im not using any stored procedures moreover i want to use normal
> ASP
> code only
> please help
> -dnk
>sql

ID Column has backed down !

hi
honestly, i can't understand
why the pointer has backed down...
in design view, i see the value 147.720
while the last id-key is 147.772
what happens ?
thanks
atte, Hernn
You need to post your DDL so we can better understand the question. Are you
working with the identity property or is this a home-grown id?
--Brian
(Please reply to the newsgroups only.)
"bajopalabra" <bajopalabra@.hotmail.com> wrote in message
news:essjRIIuFHA.204@.TK2MSFTNGP10.phx.gbl...
> hi
> honestly, i can't understand
> why the pointer has backed down...
> in design view, i see the value 147.720
> while the last id-key is 147.772
> what happens ?
> thanks
> --
> atte, Hernn
>

ID Column has backed down !

hi
honestly, i can't understand
why the pointer has backed down...
in design view, i see the value 147.720
while the last id-key is 147.772
what happens ?
thanks
atte, HernnYou need to post your DDL so we can better understand the question. Are you
working with the identity property or is this a home-grown id?
--Brian
(Please reply to the newsgroups only.)
"bajopalabra" <bajopalabra@.hotmail.com> wrote in message
news:essjRIIuFHA.204@.TK2MSFTNGP10.phx.gbl...
> hi
> honestly, i can't understand
> why the pointer has backed down...
> in design view, i see the value 147.720
> while the last id-key is 147.772
> what happens ?
> thanks
> --
> atte, Hernn
>

ID Column has backed down !

hi
honestly, i can't understand
why the pointer has backed down...
in design view, i see the value 147.720
while the last id-key is 147.772
what happens ?
thanks
--
atte, HernánYou need to post your DDL so we can better understand the question. Are you
working with the identity property or is this a home-grown id?
--
--Brian
(Please reply to the newsgroups only.)
"bajopalabra" <bajopalabra@.hotmail.com> wrote in message
news:essjRIIuFHA.204@.TK2MSFTNGP10.phx.gbl...
> hi
> honestly, i can't understand
> why the pointer has backed down...
> in design view, i see the value 147.720
> while the last id-key is 147.772
> what happens ?
> thanks
> --
> atte, Hernán
>

I'd changed the server name, sql server can't start

hi, I have changed the host name of windows 2K server , then sql server 2000
can not start now, how can I restore the config? I don't want to reinstall
the sql server, thanks.Hi Tigershome,
To solve this, register your server again. Enter Enterprise Manager,
right-click on your SQL Server Group, then select New SQL Server
Registration... Follow the wizard and when it asks you for the server, type
the name of your new Windows 2K server. Continue and finish the wizard, and
your SQL Server will be up and running. If not, please post again.
Jerome Smith
"tigershome" <tigershome@.etang.com> wrote in message
news:OlLC7FZqDHA.2488@.TK2MSFTNGP12.phx.gbl...
> hi, I have changed the host name of windows 2K server , then sql server
2000
> can not start now, how can I restore the config? I don't want to reinstall
> the sql server, thanks.
>
>

Id (indentity) is increments on faults.

Hi,

When i eg. manually ad entries to a table and, cancels the insert Ms SQL
increment the counter on the ID anyway. Is there a way to avoid this
behavior?

Regards
AndersFlare (dct_flare@.hotmail.com) writes:
> When i eg. manually ad entries to a table and, cancels the insert Ms SQL
> increment the counter on the ID anyway. Is there a way to avoid this
> behavior?

Yes, don't use the IDENTITY property, but roll your own. IDENTITY works
that way by design. By grabbing one number which never has to be
rolled back, insertions into tables with IDENTITY columns can scale
better.

One way to get a key on your on is:

BEGIN TRANSACTION

SELECT @.id = coalesce(MAX(id), 0) + 1 FROM tbl (UPDLOCK)

INSERT tbl (id, col1, col2, ...)
VALUES (@.id, @.par1, @.par2, ...)

COMMIT TRANSACTION

The UPDLOCK is required to avoid that two processes grab the
same id.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.aspsql

Iconsistent DB

I attached a base and when initiating the system appears the following
message: Error 823
I/O error <error> detected during <operation> at offset <offset> in file
'<file>'
Executei dbcc checkdb and showed some errors, executed dbcc checkdb with
repair_rebuild, but it did not correct with error (The repair level on the
DBCC statement caused this repair to be bypassed. The system cannot self
repair this error.)
It has another possibility to correct?
And I do not have backup brought up to data.If you don't have a backup then you're only option is to run checkedb with
the REPAIR_ALLOW_DATA_LOSS option. Note that this will break the
transactional consistency of relationships between tables and so on. If
you're unsure how to proceed you should contact PSS who will walk you
through it (http://support.microsoft.com/)
Regards
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carla" <Carla@.discussions.microsoft.com> wrote in message
news:3A6CAEB4-B4DC-48BB-B6AE-67B6979DB453@.microsoft.com...
> I attached a base and when initiating the system appears the following
> message: Error 823
> I/O error <error> detected during <operation> at offset <offset> in file
> '<file>'
> Executei dbcc checkdb and showed some errors, executed dbcc checkdb with
> repair_rebuild, but it did not correct with error (The repair level on the
> DBCC statement caused this repair to be bypassed. The system cannot self
> repair this error.)
> It has another possibility to correct?
> And I do not have backup brought up to data.|||Hi,
I used to REPAIR_ALLOW_DATA_LOSS, but i continued with the same errors.
This is end the error
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 1094862163)' (object ID 1094862163).
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 1229017694)' (object ID 1229017694).
CHECKDB found 62 allocation errors and 1 consistency errors in database
'itlsys'.
Help me
"Paul S Randal [MS]" wrote:
> If you don't have a backup then you're only option is to run checkedb with
> the REPAIR_ALLOW_DATA_LOSS option. Note that this will break the
> transactional consistency of relationships between tables and so on. If
> you're unsure how to proceed you should contact PSS who will walk you
> through it (http://support.microsoft.com/)
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Carla" <Carla@.discussions.microsoft.com> wrote in message
> news:3A6CAEB4-B4DC-48BB-B6AE-67B6979DB453@.microsoft.com...
> >
> > I attached a base and when initiating the system appears the following
> > message: Error 823
> > I/O error <error> detected during <operation> at offset <offset> in file
> > '<file>'
> > Executei dbcc checkdb and showed some errors, executed dbcc checkdb with
> > repair_rebuild, but it did not correct with error (The repair level on the
> > DBCC statement caused this repair to be bypassed. The system cannot self
> > repair this error.)
> > It has another possibility to correct?
> > And I do not have backup brought up to data.
>
>|||Can you post the actual errors it found please?
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carla" <Carla@.discussions.microsoft.com> wrote in message
news:8C62BD23-7200-4E44-9133-C72ED17DD359@.microsoft.com...
> Hi,
> I used to REPAIR_ALLOW_DATA_LOSS, but i continued with the same errors.
> This is end the error
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object
> ID 1094862163)' (object ID 1094862163).
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object
> ID 1229017694)' (object ID 1229017694).
> CHECKDB found 62 allocation errors and 1 consistency errors in database
> 'itlsys'.
> Help me
>
> "Paul S Randal [MS]" wrote:
> > If you don't have a backup then you're only option is to run checkedb
with
> > the REPAIR_ALLOW_DATA_LOSS option. Note that this will break the
> > transactional consistency of relationships between tables and so on. If
> > you're unsure how to proceed you should contact PSS who will walk you
> > through it (http://support.microsoft.com/)
> >
> > Regards
> >
> > --
> > Paul Randal
> > Dev Lead, Microsoft SQL Server Storage Engine
> >
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> > "Carla" <Carla@.discussions.microsoft.com> wrote in message
> > news:3A6CAEB4-B4DC-48BB-B6AE-67B6979DB453@.microsoft.com...
> > >
> > > I attached a base and when initiating the system appears the following
> > > message: Error 823
> > > I/O error <error> detected during <operation> at offset <offset> in
file
> > > '<file>'
> > > Executei dbcc checkdb and showed some errors, executed dbcc checkdb
with
> > > repair_rebuild, but it did not correct with error (The repair level on
the
> > > DBCC statement caused this repair to be bypassed. The system cannot
self
> > > repair this error.)
> > > It has another possibility to correct?
> > > And I do not have backup brought up to data.
> >
> >
> >|||Server: Msg 8946, Level 16, State 12, Line 2
Table error: Allocation page (1:323520) has invalid PFS_PAGE page header
values. Type is 0. Check type, object ID and page ID on the page.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID -2130691967, index ID 18764, page (1:323520). Test
(IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID -2130691967, index ID 18764, page (1:323520). Test
(IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
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 inconsistent. Check
previous errors.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:299256) to (1:307343). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:307344) to (1:315431). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:315432) to (1:323519). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:323520) to (1:331607). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:331608) to (1:339695). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:339696). Test (m_headerVersion
== HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:339696). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:339696). Test (m_freeData >=PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:339696) to (1:347783). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:347784). Test (m_headerVersion
== HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:347784). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:347784). Test (m_freeData >=PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:347784) to (1:355871). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:355872). Test (m_headerVersion
== HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:355872). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:355872). Test (m_freeData >=PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:355872) to (1:363959). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:363960) to (1:372047). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:372048) to (1:380135). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:380136) to (1:388223). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:388224) to (1:396311). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:396312). Test (m_headerVersion
== HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:396312). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:396312). Test (m_freeData >=PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:396312). Test (*(((int*)
&m_reservedB) + i) == 0) failed. Values are 0 and 892941614.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:396312) to (1:404399). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:404400) to (1:412487). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:412488) to (1:420575). See other errors for cause.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 1 consistency errors in table '(Object
ID -2130691967)' (object ID -2130691967).
DBCC results for 'itlsys'.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:420576) to (1:428663). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 8224, page (1:412488). Test
(m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 8224, page (1:412488). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 8224, page (1:412488). Test (m_freeData
>= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 8224, page (1:412488). Test (*(((int*)
&m_reservedB) + i) == 0) failed. Values are 0 and 791763761.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1160, index ID 8224, page (1:380136). Test
(m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1160, index ID 8224, page (1:380136). Test (m_slotCnt
< MaxSlot) failed. Values are 10240 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1160, index ID 8224, page (1:380136). Test (*(((int*)
&m_reservedB) + i) == 0) failed. Values are 1 and -1207959552.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 50345345, index ID 18764, page (1:315432). Test
(IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
(m_headerVersion == HEADER_7_0) failed. Values are 53 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
(m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt *
sizeof (Slot)) failed. Values are 0 and -8256.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
(m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
(m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
(m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 8224 and 8096.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
(m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976311, index ID 32, page (1:372048). Test
(m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976311, index ID 32, page (1:372048). Test
(m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 13619 and 8096.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976311, index ID 32, page (1:372048). Test
(m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976311, index ID 32, page (1:372048). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 1 and 538976288.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 771751936, index ID 13618, page (1:420576). Test
(m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 771751936, index ID 13618, page (1:420576). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
(m_headerVersion == HEADER_7_0) failed. Values are 51 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
(m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 8224 and 8096.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
(m_slotCnt < MaxSlot) failed. Values are 14080 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538980630.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
(m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
(m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt *
sizeof (Slot)) failed. Values are 14640 and 8094.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
(m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 13614 and 8096.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 825897010.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1094862163, index ID 18764, page (1:331608). Test
(IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 33 allocation errors and 0 consistency errors not associated
with any single object.
DBCC results for 'sysobjects'.
There are 838 rows in 13 pages for object 'sysobjects'.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object
ID 1160)' (object ID 1160).
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 50345345)' (object ID 50345345).
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 8 allocation errors and 0 consistency errors in table '(Object
ID 538976288)' (object ID 538976288).
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 4 allocation errors and 0 consistency errors in table '(Object
ID 538976311)' (object ID 538976311).
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 2 allocation errors and 0 consistency errors in table '(Object
ID 771751936)' (object ID 771751936).
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 4 allocation errors and 0 consistency errors in table '(Object
ID 824188960)' (object ID 824188960).
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 4 allocation errors and 0 consistency errors in table '(Object
ID 892418303)' (object ID 892418303).
Server: Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1229017694, index ID 18764, page (1:307344). Test
(IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 1094862163)' (object ID 1094862163).
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 1229017694)' (object ID 1229017694).
CHECKDB found 62 allocation errors and 1 consistency errors in database
'itlsys'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.|||Ah - you've hit one of the few page corruptions that are unrepairable - a
PFS page header. SQL Server cannot fix this error, so unless you have a
backup, your only option is to extract the data from the database into a new
database. You also need to run hardware diagnostics on your system as I'm
guessing that a portion of the PFS page has been zeroed out.
You should contact PSS to help you as this is beyond the scope of the
newsgroups.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carla" <Carla@.discussions.microsoft.com> wrote in message
news:1F022C26-9F0B-41E0-B1D7-3CADE197E37D@.microsoft.com...
> Server: Msg 8946, Level 16, State 12, Line 2
> Table error: Allocation page (1:323520) has invalid PFS_PAGE page header
> values. Type is 0. Check type, object ID and page ID on the page.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID -2130691967, index ID 18764, page (1:323520). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID -2130691967, index ID 18764, page (1:323520). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> 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 inconsistent. Check
> previous errors.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:299256) to (1:307343). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:307344) to (1:315431). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:315432) to (1:323519). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:323520) to (1:331607). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:331608) to (1:339695). See other errors for
cause.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:339696). Test
(m_headerVersion
> == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:339696). Test ((m_type
> >=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE
&&
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:339696). Test (m_freeData >=> PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:339696) to (1:347783). See other errors for
cause.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:347784). Test
(m_headerVersion
> == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:347784). Test ((m_type
> >=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE
&&
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:347784). Test (m_freeData >=> PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:347784) to (1:355871). See other errors for
cause.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:355872). Test
(m_headerVersion
> == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:355872). Test ((m_type
> >=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE
&&
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:355872). Test (m_freeData >=> PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:355872) to (1:363959). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:363960) to (1:372047). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:372048) to (1:380135). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:380136) to (1:388223). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:388224) to (1:396311). See other errors for
cause.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:396312). Test
(m_headerVersion
> == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:396312). Test ((m_type
> >=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE
&&
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:396312). Test (m_freeData >=> PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:396312). Test (*(((int*)
> &m_reservedB) + i) == 0) failed. Values are 0 and 892941614.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:396312) to (1:404399). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:404400) to (1:412487). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:412488) to (1:420575). See other errors for
cause.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 1 consistency errors in table
'(Object
> ID -2130691967)' (object ID -2130691967).
> DBCC results for 'itlsys'.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:420576) to (1:428663). See other errors for
cause.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 8224, page (1:412488). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 8224, page (1:412488). Test ((m_type
> >=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE
&&
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 8224, page (1:412488). Test (m_freeData
> >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof
(Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 8224, page (1:412488). Test (*(((int*)
> &m_reservedB) + i) == 0) failed. Values are 0 and 791763761.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1160, index ID 8224, page (1:380136). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1160, index ID 8224, page (1:380136). Test
(m_slotCnt
> < MaxSlot) failed. Values are 10240 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1160, index ID 8224, page (1:380136). Test
(*(((int*)
> &m_reservedB) + i) == 0) failed. Values are 1 and -1207959552.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 50345345, index ID 18764, page (1:315432). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 53 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
> (m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt *
> sizeof (Slot)) failed. Values are 0 and -8256.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
> (m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
> (m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 8224 and 8096.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
> (m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976311, index ID 32, page (1:372048). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976311, index ID 32, page (1:372048). Test
> (m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 13619 and 8096.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976311, index ID 32, page (1:372048). Test
> (m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976311, index ID 32, page (1:372048). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 1 and 538976288.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 771751936, index ID 13618, page (1:420576). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 771751936, index ID 13618, page (1:420576). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 51 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
> (m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 8224 and 8096.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
> (m_slotCnt < MaxSlot) failed. Values are 14080 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538980630.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
> (m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt *
> sizeof (Slot)) failed. Values are 14640 and 8094.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
> (m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 13614 and 8096.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 825897010.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1094862163, index ID 18764, page (1:331608). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 33 allocation errors and 0 consistency errors not associated
> with any single object.
> DBCC results for 'sysobjects'.
> There are 838 rows in 13 pages for object 'sysobjects'.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 3 allocation errors and 0 consistency errors in table
'(Object
> ID 1160)' (object ID 1160).
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object
> ID 50345345)' (object ID 50345345).
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 8 allocation errors and 0 consistency errors in table
'(Object
> ID 538976288)' (object ID 538976288).
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 4 allocation errors and 0 consistency errors in table
'(Object
> ID 538976311)' (object ID 538976311).
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 2 allocation errors and 0 consistency errors in table
'(Object
> ID 771751936)' (object ID 771751936).
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 4 allocation errors and 0 consistency errors in table
'(Object
> ID 824188960)' (object ID 824188960).
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 4 allocation errors and 0 consistency errors in table
'(Object
> ID 892418303)' (object ID 892418303).
> Server: Msg 8939, Level 16, State 98, Line 1
> Table error: Object ID 1229017694, index ID 18764, page (1:307344). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object
> ID 1094862163)' (object ID 1094862163).
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object
> ID 1229017694)' (object ID 1229017694).
> CHECKDB found 62 allocation errors and 1 consistency errors in database
> 'itlsys'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>

Iconsistent DB

I attached a base and when initiating the system appears the following
message: Error 823
I/O error <error> detected during <operation> at offset <offset> in file
'<file>'
Executei dbcc checkdb and showed some errors, executed dbcc checkdb with
repair_rebuild, but it did not correct with error (The repair level on the
DBCC statement caused this repair to be bypassed. The system cannot self
repair this error.)
It has another possibility to correct?
And I do not have backup brought up to data.
If you don't have a backup then you're only option is to run checkedb with
the REPAIR_ALLOW_DATA_LOSS option. Note that this will break the
transactional consistency of relationships between tables and so on. If
you're unsure how to proceed you should contact PSS who will walk you
through it (http://support.microsoft.com/)
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carla" <Carla@.discussions.microsoft.com> wrote in message
news:3A6CAEB4-B4DC-48BB-B6AE-67B6979DB453@.microsoft.com...
> I attached a base and when initiating the system appears the following
> message: Error 823
> I/O error <error> detected during <operation> at offset <offset> in file
> '<file>'
> Executei dbcc checkdb and showed some errors, executed dbcc checkdb with
> repair_rebuild, but it did not correct with error (The repair level on the
> DBCC statement caused this repair to be bypassed. The system cannot self
> repair this error.)
> It has another possibility to correct?
> And I do not have backup brought up to data.
|||Hi,
I used to REPAIR_ALLOW_DATA_LOSS, but i continued with the same errors.
This is end the error
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 1094862163)' (object ID 1094862163).
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 1229017694)' (object ID 1229017694).
CHECKDB found 62 allocation errors and 1 consistency errors in database
'itlsys'.
Help me
"Paul S Randal [MS]" wrote:

> If you don't have a backup then you're only option is to run checkedb with
> the REPAIR_ALLOW_DATA_LOSS option. Note that this will break the
> transactional consistency of relationships between tables and so on. If
> you're unsure how to proceed you should contact PSS who will walk you
> through it (http://support.microsoft.com/)
> Regards
> --
> Paul Randal
> Dev Lead, Microsoft SQL Server Storage Engine
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Carla" <Carla@.discussions.microsoft.com> wrote in message
> news:3A6CAEB4-B4DC-48BB-B6AE-67B6979DB453@.microsoft.com...
>
>
|||Can you post the actual errors it found please?
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carla" <Carla@.discussions.microsoft.com> wrote in message
news:8C62BD23-7200-4E44-9133-C72ED17DD359@.microsoft.com...
> Hi,
> I used to REPAIR_ALLOW_DATA_LOSS, but i continued with the same errors.
> This is end the error
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object
> ID 1094862163)' (object ID 1094862163).
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object[vbcol=seagreen]
> ID 1229017694)' (object ID 1229017694).
> CHECKDB found 62 allocation errors and 1 consistency errors in database
> 'itlsys'.
> Help me
>
> "Paul S Randal [MS]" wrote:
with[vbcol=seagreen]
rights.[vbcol=seagreen]
file[vbcol=seagreen]
with[vbcol=seagreen]
the[vbcol=seagreen]
self[vbcol=seagreen]
|||Server: Msg 8946, Level 16, State 12, Line 2
Table error: Allocation page (1:323520) has invalid PFS_PAGE page header
values. Type is 0. Check type, object ID and page ID on the page.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID -2130691967, index ID 18764, page (1:323520). Test
(IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID -2130691967, index ID 18764, page (1:323520). Test
(IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
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 inconsistent. Check
previous errors.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:299256) to (1:307343). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:307344) to (1:315431). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:315432) to (1:323519). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:323520) to (1:331607). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:331608) to (1:339695). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:339696). Test (m_headerVersion
== HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:339696). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:339696). Test (m_freeData >=
PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:339696) to (1:347783). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:347784). Test (m_headerVersion
== HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:347784). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:347784). Test (m_freeData >=
PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:347784) to (1:355871). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:355872). Test (m_headerVersion
== HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:355872). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:355872). Test (m_freeData >=
PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:355872) to (1:363959). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:363960) to (1:372047). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:372048) to (1:380135). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:380136) to (1:388223). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:388224) to (1:396311). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:396312). Test (m_headerVersion
== HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:396312). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:396312). Test (m_freeData >=
PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 0, page (1:396312). Test (*(((int*)
&m_reservedB) + i) == 0) failed. Values are 0 and 892941614.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:396312) to (1:404399). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:404400) to (1:412487). See other errors for cause.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:412488) to (1:420575). See other errors for cause.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 1 consistency errors in table '(Object
ID -2130691967)' (object ID -2130691967).
DBCC results for 'itlsys'.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
The repair level on the DBCC statement caused this repair to be
bypassed.
Server: Msg 8998, Level 16, State 1, Line 1
Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify
database ID 7 pages from (1:420576) to (1:428663). See other errors for cause.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 8224, page (1:412488). Test
(m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 8224, page (1:412488). Test ((m_type
>=DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE &&
level == BASIC_HEADER)) failed. Values are 0 and 101.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 8224, page (1:412488). Test (m_freeData
>= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
failed. Values are 0 and 8192.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 0, index ID 8224, page (1:412488). Test (*(((int*)
&m_reservedB) + i) == 0) failed. Values are 0 and 791763761.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1160, index ID 8224, page (1:380136). Test
(m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1160, index ID 8224, page (1:380136). Test (m_slotCnt
< MaxSlot) failed. Values are 10240 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1160, index ID 8224, page (1:380136). Test (*(((int*)
&m_reservedB) + i) == 0) failed. Values are 1 and -1207959552.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 50345345, index ID 18764, page (1:315432). Test
(IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
(m_headerVersion == HEADER_7_0) failed. Values are 53 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
(m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt *
sizeof (Slot)) failed. Values are 0 and -8256.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
(m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
(m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
(m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 8224 and 8096.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
(m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976311, index ID 32, page (1:372048). Test
(m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976311, index ID 32, page (1:372048). Test
(m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 13619 and 8096.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976311, index ID 32, page (1:372048). Test
(m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 538976311, index ID 32, page (1:372048). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 1 and 538976288.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 771751936, index ID 13618, page (1:420576). Test
(m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 771751936, index ID 13618, page (1:420576). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
(m_headerVersion == HEADER_7_0) failed. Values are 51 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
(m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 8224 and 8096.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
(m_slotCnt < MaxSlot) failed. Values are 14080 and 4048.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538980630.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
(m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
(m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt *
sizeof (Slot)) failed. Values are 14640 and 8094.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
(m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 13614 and 8096.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
(*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 825897010.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 1094862163, index ID 18764, page (1:331608). Test
(IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 33 allocation errors and 0 consistency errors not associated
with any single object.
DBCC results for 'sysobjects'.
There are 838 rows in 13 pages for object 'sysobjects'.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object
ID 1160)' (object ID 1160).
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 50345345)' (object ID 50345345).
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 8 allocation errors and 0 consistency errors in table '(Object
ID 538976288)' (object ID 538976288).
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 4 allocation errors and 0 consistency errors in table '(Object
ID 538976311)' (object ID 538976311).
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 2 allocation errors and 0 consistency errors in table '(Object
ID 771751936)' (object ID 771751936).
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 4 allocation errors and 0 consistency errors in table '(Object
ID 824188960)' (object ID 824188960).
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
CHECKDB found 4 allocation errors and 0 consistency errors in table '(Object
ID 892418303)' (object ID 892418303).
Server: Msg 8939, Level 16, State 98, Line 1
Table error: Object ID 1229017694, index ID 18764, page (1:307344). Test
(IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 1094862163)' (object ID 1094862163).
The system cannot self repair this error.
CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object
ID 1229017694)' (object ID 1229017694).
CHECKDB found 62 allocation errors and 1 consistency errors in database
'itlsys'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
|||Ah - you've hit one of the few page corruptions that are unrepairable - a
PFS page header. SQL Server cannot fix this error, so unless you have a
backup, your only option is to extract the data from the database into a new
database. You also need to run hardware diagnostics on your system as I'm
guessing that a portion of the PFS page has been zeroed out.
You should contact PSS to help you as this is beyond the scope of the
newsgroups.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Carla" <Carla@.discussions.microsoft.com> wrote in message
news:1F022C26-9F0B-41E0-B1D7-3CADE197E37D@.microsoft.com...
> Server: Msg 8946, Level 16, State 12, Line 2
> Table error: Allocation page (1:323520) has invalid PFS_PAGE page header
> values. Type is 0. Check type, object ID and page ID on the page.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID -2130691967, index ID 18764, page (1:323520). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID -2130691967, index ID 18764, page (1:323520). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> 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 inconsistent. Check
> previous errors.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:299256) to (1:307343). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:307344) to (1:315431). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:315432) to (1:323519). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:323520) to (1:331607). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:331608) to (1:339695). See other errors for
cause.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:339696). Test
(m_headerVersion[vbcol=seagreen]
> == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:339696). Test ((m_type
&&
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:339696). Test (m_freeData >=
> PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:339696) to (1:347783). See other errors for
cause.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:347784). Test
(m_headerVersion[vbcol=seagreen]
> == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:347784). Test ((m_type
&&
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:347784). Test (m_freeData >=
> PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:347784) to (1:355871). See other errors for
cause.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:355872). Test
(m_headerVersion[vbcol=seagreen]
> == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:355872). Test ((m_type
&&
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:355872). Test (m_freeData >=
> PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:355872) to (1:363959). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:363960) to (1:372047). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:372048) to (1:380135). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:380136) to (1:388223). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:388224) to (1:396311). See other errors for
cause.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:396312). Test
(m_headerVersion[vbcol=seagreen]
> == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:396312). Test ((m_type
&&
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:396312). Test (m_freeData >=
> PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 0, page (1:396312). Test (*(((int*)
> &m_reservedB) + i) == 0) failed. Values are 0 and 892941614.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:396312) to (1:404399). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:404400) to (1:412487). See other errors for
cause.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:412488) to (1:420575). See other errors for
cause.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 1 consistency errors in table
'(Object
> ID -2130691967)' (object ID -2130691967).
> DBCC results for 'itlsys'.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> Server: Msg 8998, Level 16, State 1, Line 1
> Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to
verify
> database ID 7 pages from (1:420576) to (1:428663). See other errors for
cause.[vbcol=seagreen]
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 8224, page (1:412488). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 8224, page (1:412488). Test ((m_type
&&[vbcol=seagreen]
> level == BASIC_HEADER)) failed. Values are 0 and 101.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 8224, page (1:412488). Test (m_freeData
(Slot))
> failed. Values are 0 and 8192.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 0, index ID 8224, page (1:412488). Test (*(((int*)
> &m_reservedB) + i) == 0) failed. Values are 0 and 791763761.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1160, index ID 8224, page (1:380136). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1160, index ID 8224, page (1:380136). Test
(m_slotCnt
> < MaxSlot) failed. Values are 10240 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1160, index ID 8224, page (1:380136). Test
(*(((int*)
> &m_reservedB) + i) == 0) failed. Values are 1 and -1207959552.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 50345345, index ID 18764, page (1:315432). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 53 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
> (m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt *
> sizeof (Slot)) failed. Values are 0 and -8256.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
> (m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:363960). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
> (m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 8224 and 8096.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
> (m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976288, index ID 8224, page (1:388224). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976311, index ID 32, page (1:372048). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976311, index ID 32, page (1:372048). Test
> (m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 13619 and 8096.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976311, index ID 32, page (1:372048). Test
> (m_slotCnt < MaxSlot) failed. Values are 8224 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 538976311, index ID 32, page (1:372048). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 1 and 538976288.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 771751936, index ID 13618, page (1:420576). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 32 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 771751936, index ID 13618, page (1:420576). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538976288.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 51 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
> (m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 8224 and 8096.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
> (m_slotCnt < MaxSlot) failed. Values are 14080 and 4048.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 824188960, index ID 8224, page (1:404400). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 538980630.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
> (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
> (m_freeData >= PAGEHEADSIZE && m_freeData <= (UINT)PAGESIZE - m_slotCnt *
> sizeof (Slot)) failed. Values are 14640 and 8094.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
> (m_freeCnt <= PAGESIZE - PAGEHEADSIZE) failed. Values are 13614 and 8096.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 892418303, index ID 25966, page (1:299256). Test
> (*(((int*) &m_reservedB) + i) == 0) failed. Values are 0 and 825897010.
> Server: Msg 8939, Level 16, State 1, Line 1
> Table error: Object ID 1094862163, index ID 18764, page (1:331608). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 33 allocation errors and 0 consistency errors not associated
> with any single object.
> DBCC results for 'sysobjects'.
> There are 838 rows in 13 pages for object 'sysobjects'.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 3 allocation errors and 0 consistency errors in table
'(Object
> ID 1160)' (object ID 1160).
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object
> ID 50345345)' (object ID 50345345).
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 8 allocation errors and 0 consistency errors in table
'(Object
> ID 538976288)' (object ID 538976288).
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 4 allocation errors and 0 consistency errors in table
'(Object
> ID 538976311)' (object ID 538976311).
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 2 allocation errors and 0 consistency errors in table
'(Object
> ID 771751936)' (object ID 771751936).
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 4 allocation errors and 0 consistency errors in table
'(Object
> ID 824188960)' (object ID 824188960).
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> CHECKDB found 4 allocation errors and 0 consistency errors in table
'(Object
> ID 892418303)' (object ID 892418303).
> Server: Msg 8939, Level 16, State 98, Line 1
> Table error: Object ID 1229017694, index ID 18764, page (1:307344). Test
> (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057
and -1.
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object
> ID 1094862163)' (object ID 1094862163).
> The system cannot self repair this error.
> CHECKDB found 1 allocation errors and 0 consistency errors in table
'(Object
> ID 1229017694)' (object ID 1229017694).
> CHECKDB found 62 allocation errors and 1 consistency errors in database
> 'itlsys'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>