Could not find row in sysindexes with index ID

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

Could not find row in sysindexes with index ID

Author

Topic

sc415191
Starting Member

4 Posts

Posted - 2005-12-19 : 22:41:04

Please help
1. my database can not truncate log and I use this command
BACKUP LOG IMVDB2 WITH NO_LOG
and after that I received result as below
->The log was not truncated because records at the beginning of the log are pending replication. Ensure the Log Reader Agent is running or use sp_repldone to mark transactions as distributed.

2. so I drop all replicate but it's still return same error
so I try to run
DBCC CHECKDB --> but no error meesage
DBCC CHECKALLOC --> but no error meesage
DBCC CHECKTABLE ('sysindexes') --> but no error meesage
but I tried to run
3. DBCC PAGE (IMVDB2, 1, 13015, 3) i recieved
-->Server: Msg 2591, Level 16, State 14, Line 1
Could not find row in sysindexes with index ID 2 for table 'object ID (334220541)'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

so what can I do the next to fix this problem, please help[/b]

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2005-12-21 : 09:24:25

I think there's some info/context missing from your explanation - why are you running DBCC PAGE, and on that page in particular?

Paul Randal
Lead Program Manager, Microsoft SQL Server Storage Engine
(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.)

sc415191
Starting Member

4 Posts

Posted - 2005-12-21 : 20:49:51

coz I suppose this problem may came from page error and I ever seen this "DBCC PAGE (IMVDB2, 1, 13015, 3)" command in this web so I try to run and checking so how to do
or the thing that I can do is restore the last back up ka please help

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2005-12-22 : 20:27:24

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=59509

Tara Kizer
aka tduggan

nevada
Starting Member

1 Post

Posted - 2005-12-22 : 23:49:18

The reason why sc415191 try to truncate log because now the transaction log is growing.
Now it's size is 17 Gbs. The database recovery mode is set to simple. It means log size
should not so big.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources