Linkage Problem

Feb 1, 2007

I have ran a DBCC CHECKDB on a database that was suspect because of a drive space issue. I am getting these errors:

DBCC results for 'SC_Table'.
There are 79 rows in 2 pages for object 'SC_Table'.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1755153298, index ID 1. Page (1:6107122) is missing a reference from previous page (1:6107110). Possible chain linkage problem.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1755153298, index ID 1. Page (1:6107124) is missing a reference from previous page (1:6107121). Possible chain linkage problem.
DBCC results for 'SC_Table'.

I have tried to run DBCC DBREINDEX on the table and the problem was not corrected. I also ran DBCC CHECKDB ('SCDB', REPAIR_REBUILD) with no luck due due to the .mdf filling the entire drive before failing. Does anyone have any suggestions?

View 4 Replies

Chain Linkage Mismatch....

Dec 8, 2003

Server: Msg 8908, Level 22, State 6,
on index defragmentation on a table.

Table error: Database ID 490, object ID 517576882, index ID 0. Chain linkage mismatch. (1:13020)->next = (1:13021), but (1:13021)->prev = (1:13080).

from error.log found corresponding error on dbcc checkdatabase on this same database:
I/O error (bad page ID) detected during read at offset 0x00000006614000 in file
'T:DataABCABC_data.mdf'..
Waiting for type 0x4, current count 0x100022, current owning EC 0x76A85540.
Error: 823, Severity: 24, State: 2

is there a way to fix this chain linkage mismatch error?
thanks
-D

View 4 Replies View Related

Page Linkage Failed

Jan 12, 1999

When I run :
SP_DBOPTION HIS, 'SINGLE USER', TRUE
GO
DBCC CHECKDB(HIS)
GO
DBCC NEWALLOC(HIS)
GO
SP_DBOPTION HIS, 'SINGLE USER', FALSE
GO

I receive "linkage failed for INDID 1; processed 1 pages" in the error log, I assumed
the database is damage, but when I run "select name from master..sysdatabases
where status & 256 = 256", no rows return which means the database is not corrupt, or
when I run "dbcc checktable" no errors are produce. What is Page linkage failed telling
me?

View 1 Replies View Related

Linkage From 2 Drop Down Tables?

Jun 15, 2007

Hello all, im using visual web developer btw. Im using the excellent tutorial here at http://www.asp.net/learn/videos/view.aspx?tabid=63&id=49 Works a treat. For my catalogue/database. i have 2 tables using the drop down menu - one is a "Buyers guide" (a list of the product) and an "application list" (this one is a list of the motorbike).

So in essence they are the same tables, but of course moved around with slightly different ways. What i would like to, is to some how make a refferenced link to each - Once one of the drop down menus has been linked to a product, theres a column that tells u what bike is being used....i therefore want to have a link so the seconmdary drop down menu - but i do not know how i can do this. Any ideas guys/gals? thx.

View 1 Replies View Related

Chain Linkage Mismatch Errors

May 4, 2004

Recently I have been getting a barrage of errors such as:

DESCRIPTION:Error: 8908, Severity: 22, State: 6
Table error: Database ID 16, object ID 1893581784, index ID 2. Chain
linkage mismatch. (1:17214)->next = (1:17060), but (1:17060)->prev =
(3:178).

and

DESCRIPTION:Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:164756) in database 'Clients' belongs
to object 'activities', not to object 'entity_address_check'.

The problem began to originally manifest itself with a couple errors
similar to:

DESCRIPTION:Error: 605, Severity: 21, State: 1
Attempt to fetch logical page (1:4930) in database 'tempdb' belongs to
object '1732152167', not to object
'#allrowstable____________________________________ __________________________________________________ _________________000100003472'.

So far all of the errors have been isolated to indexes and I have been
able to repair the problems with CHECKDB fast_rebuild or by dropping
the index that is causing the error and recreating it. At times the
errors will appear for a couple hours overnight and then resolve
themselves before the morning. Originally the problem began to appear
on a single SQL Servers and now appears daily on all three SQL
Servers.

We've investigated whether the NOLOCK optimizer was the culprit but
out of all of our views and procedures there was nothing compiled with
that optimizer in any of the databases, so this seems an unlikely
cause (SEE http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B308886
)

We've reviewed IO on the servers, and nothing appears out of the
ordinary. We have even checked into the possibility of unreport IO
errors (SEE http://support.microsoft.com/default.aspx?scid=kb;en-us;826433&Product=sql2k
) but this still is inconclusive. HP did admit that their disc array
is not fully compatible with W2K Adv Server SP3, but the problem only
recently appeared and the upgrade to SP3 was completed nearly 2 months
ago.

We are running SQL Server 2000 EE, SP3 build 2195 on Windows 2000
Advanced Server. The server is setup as an A/P cluster on 2 HP
Proliant servers with a HP HTA200 disc array.

If anyone has any insight or suggestions, it would be great to hear
them.

View 2 Replies View Related

DBCC - Chain Linkage Problem

Aug 31, 2005

I'm having a problem where I see consistency errors in my databases on a regular basis (at least twice a week).

I have several databases running on the same instance of SQL Server. During any given week, at least one of the databases will show consistency errors. At times, more than one at the same time will show these errors. These have odd effects on queries, sometimes making a SELECT (for instance) that should run in 5 seconds have to be killed after running for over an hour.

I'm running SQL Server 2000, version 8.00.194. The host OS is Windows 2000 with the latest service pack. RAID 5 is the storage solution.

Below are two DBCC outputs from different databases on the same machine. They are slightly different in that one starts out with "Parent node for page was not encountered"; and the other with "Page is missing a reference from previous page".

My hardware guys assure me there is no hardware failure going. I don't see anything that would suggest there is one in any of the event logs or in the Dell OpenManage system checks.

These DBCC errors are repairable without data loss, yet the databases have to be taken down to single user mode to do so (unacceptable during the day). But at the same time, certain operations in the database become impossible to perform when these errors crop up (such as the aforementioned infinite SELECT problem).

Any help in diagnosing why these pop up, or how to prevent them would be greatly appreciated.

The DBCC outputs:
-----------------------------------------
dbcc checkdb('ValidValues') with no_infomsgs
==========
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 3. Page (1:10921) is missing a reference from previous page (1:75359). Possible chain linkage problem.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 3. Page (1:75354) was not seen in the scan although its parent (1:75424) and previous (1:75352) refer to it. Check any previous errors.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 3. Index node page (1:75424), slot 19 refers to child page (1:75355) and previous child (1:75354), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 3. Index node page (1:75424), slot 20 refers to child page (1:75356) and previous child (1:75355), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 3. Index node page (1:75424), slot 21 refers to child page (1:75357) and previous child (1:75356), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 3. Index node page (1:75424), slot 22 refers to child page (1:75358) and previous child (1:75357), but they were not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 3. Index node page (1:75424), slot 23 refers to child page (1:75359) and previous child (1:75358), but they were not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:10931) was not encountered.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Page (1:10932) is missing references from parent (unknown) and previous (page (1:75671)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:10933) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:10934) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:10937) was not encountered.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Page (1:10940) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:10941) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75664) was not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Index node page (0:0), slot 0 refers to child page (1:75665) and previous child (0:0), but they were not encountered.
Server: Msg 8981, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. The next pointer of (1:75664) refers to page (1:75666). Neither (1:75666) nor its parent were encountered. Possible bad chain linkage.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75673) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75674) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75675) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75676) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75705) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75706) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75707) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75708) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75737) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75738) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75739) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 926626344, index ID 5. Parent node for page (1:75740) was not encountered.
CHECKDB found 0 allocation errors and 29 consistency errors in table 'Company' (object ID 926626344).
CHECKDB found 0 allocation errors and 29 consistency errors in database 'ValidValues'.
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (ValidValues ).

-----------------------------------------

dbcc checkdb('Revenue') with no_infomsgs
==========
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110576) was not encountered.
Server: Msg 8980, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Index node page (0:0), slot 0 refers to child page (1:110577) and previous child (0:0), but they were not encountered.
Server: Msg 8981, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. The next pointer of (1:110576) refers to page (1:110578). Neither (1:110578) nor its parent were encountered. Possible bad chain linkage.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110585) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110586) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110587) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110588) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110617) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110618) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110619) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110620) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110649) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110650) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110651) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:110652) was not encountered.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Page (1:124495) is missing references from parent (unknown) and previous (page (1:110581)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:124512) was not encountered.
Server: Msg 8979, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Page (1:124513) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:124521) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:124650) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:124651) was not encountered.
Server: Msg 8977, Level 16, State 1, Line 1
Table error: Object ID 2089058478, index ID 2. Parent node for page (1:125214) was not encountered.
CHECKDB found 0 allocation errors and 22 consistency errors in table 'Operational_Reporting' (object ID 2089058478).
CHECKDB found 0 allocation errors and 22 consistency errors in database 'Revenue'.
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (Revenue ).

View 2 Replies View Related