Receiving recbase.cpp:1374 error

Question

Post reply

Receiving recbase.cpp:1374 error

Robert Koros

SSC Enthusiast

Points: 176
More actions
April 24, 2003 at 11:43 am

#81467

Good morning to all,
First some history, short version. Setting up replication, errors due to
inconsistency in tables and the associated indexes. Run DBCC to get a list
of issues, then run DBCC with Repair Rebuild, corrected most of the issues.
The ones that were not corrected the recommended course of action is to drop
and recreate the index. For a particular table, I have done that, including
the PK. Not normally a big deal but now I am receiving the error message
recbase.cpp:1374 and there is nothing on the MS site. Closest I can find is
recbase.cpp:1378 which state that this is a known issue with SQL 2000 and
the workaround is to drop and recreate the key. I am stuck because I cannot
recreate the PK or any indexes.
SQL Server 2000 SP3.
Any suggestions??
Thanks,
Robert

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 1

quote:
am stuck because I cannot
recreate the PK or any indexes.

Do you get any errors when try to recreate the PK or indexes?

Robert Koros SSC Enthusiast Points: 176 More actions · Answer 2

Yes, I get the same error. Doesn't matter if I use a script or I use EM. Have you seen this before??

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 3

Have you tried option 'REPAIR_ALLOW_DATA_LOSS'? You may have to BCP data out, drop table, recreate it, BCP data in and recreate the PK and indexes as work around.

Robert Koros SSC Enthusiast Points: 176 More actions · Answer 4

I have not tried it as this is a fairly complex data model, foreign keys, cascading updates and deletes, etc. Data loss would be a bad thing. I am in the process of creating a second table, moving the data across, then drop the original and rename the new one that is built correctly. I am curious as to what would cause this error and if there is a more efficient workaround.

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 5

I would suggest you run dbcc with 'REPAIR_ALLOW_DATA_LOSS' to this table after you move everything to new table and before drop it. The result may be interesting.

Robert Koros SSC Enthusiast Points: 176 More actions · Answer 6

I will have to try it. Once the data is safe the Repair_Allow_Data_Loss works fine, it doesn't appear as if data is lost, but I going to test some more. I want to ensure that nothing is lost on the production db.

Thanks for the help.