Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

DBCC error

2 posts in Backup and Recovery Last posting was on 2001-05-29 12:02:47.0Z
PB Posted on 2001-05-21 18:23:29.0Z
From: "PB" <bagewadi@yahoo.com>
Subject: DBCC error
Date: Mon, 21 May 2001 14:23:29 -0400
Lines: 144
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <A$O$vXi4AHA.261@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.backup+recovery
NNTP-Posting-Host: 63.236.129.10
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:240
Article PK: 1060758

Hi ,

I am getting following dbcc error in our production db. It says table
corrupt but the object id is 0!!! Is this serious?

Is error 2540,2546 on syslogs is common? Please see at the end.

This db is replicated in warm-standby. If I need to fix this, what is the
procedure to fix this db and replicated db?
Our system is 24X7.

We are on Adaptive Server Enterprise/11.9.2.3/1150/P/SWR 9098 ESD
1/Sun_svr4/OS 5.5.1/FBO/Thu Jul 6 01:53:18 2000

Thanks in Advance



Alloc page 988928 (# of extent=1 used pages=1 ref pages=1)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989184, extent id=989184, logica
l page#=989185, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989184, extent id=989184, logica
l page#=989186, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989184, extent id=989184, logica
l page#=989187, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989184, extent id=989184, logica
l page#=989188, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989184, extent id=989184, logica
l page#=989189, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989184, extent id=989184, logica
l page#=989190, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989184, extent id=989184, logica
l page#=989191, object id in extent=0, index id in extent=0, object name=0)
Alloc page 989184 (# of extent=1 used pages=1 ref pages=8)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989440, extent id=989440, logica
l page#=989441, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989440, extent id=989440, logica
l page#=989442, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989440, extent id=989440, logica
l page#=989443, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989440, extent id=989440, logica
l page#=989444, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989440, extent id=989440, logica
l page#=989445, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989440, extent id=989440, logica
l page#=989446, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989440, extent id=989440, logica
l page#=989447, object id in extent=0, index id in extent=0, object name=0)
Alloc page 989440 (# of extent=1 used pages=1 ref pages=8)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989696, extent id=989696, logica
l page#=989697, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989696, extent id=989696, logica
l page#=989698, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989696, extent id=989696, logica
l page#=989699, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989696, extent id=989696, logica
l page#=989700, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989696, extent id=989696, logica
l page#=989701, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989696, extent id=989696, logica
l page#=989702, object id in extent=0, index id in extent=0, object name=0)
Msg 2521, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is linked but not allocated. Run DBCC TABLEALLOC to
correct the problem. (alloc page#=989696, extent id=989696, logica
l page#=989703, object id in extent=0, index id in extent=0, object name=0)
Alloc page 989696 (# of extent=1 used pages=1 ref pages=8)
Msg 2546, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Extent id 989968 on allocation pg# 989952 has objid 8 and
used bit on, but reference bit off.
Msg 2540, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is allocated but not linked; check the following pages
and ids: allocation pg#=989952 extent id=989976 logical pg#=989
976 object id on extent=8 (object name = syslogs) indid on extent=0
Msg 2540, Level 16, State 1:
Server 'PROD', Line 1:
Table Corrupt: Page is allocated but not linked; check the following pages
and ids: allocation pg#=989952 extent id=989976 logical pg#=989
977 object id on extent=8 (object name = syslogs) indid on extent=0
Alloc page 989952 (# of extent=1 used pages=14 ref pages=1)


WD Posted on 2001-05-29 12:02:47.0Z
From: WD
Date: Tue, 29 May 2001 08:02:47 -0400
Newsgroups: sybase.public.sqlserver.backup+recovery
Subject: Re: DBCC error
Message-ID: <559046FF9771FEBE00422C4985256A5B.004D4F7685256A54@webforums>
References: <A$O$vXi4AHA.261@forums.sybase.com>
Lines: 16
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.sqlserver.backup+recovery:217
Article PK: 1060735

Hi,

Well, the dbcc error indicates that some of your tables have gone corrupt.

This may be either due to the tables really going corrupt or maybe there
were some transactions in progress on those tables while dbcc was going
on....

What you can do is run dbcc again in single user mode and see if the errors
are coming again and if they do, just run the commands dbcc has outlined
for you in the error messages.

Hope this solves your query. If you need any help, you can contact me at
wilfy@hotmail.com. As I rarely visit Newsgroups. By the way, I am Wilfred
from Mumbai, India.

Have a nice day.