DBCC CHECKDB return Errors
-
Environment:
SQL Server 2K sp3a Producr version 8.00.818 on Windows Server 2K3 - 2 nodes MSCS Cluster (Single instance).
We have Maintenance Plan scheduled and every week a Database Integrity Check is running thru a job on all of our databases.
This was done before, for at least 4 years on SQL Server 7 on a NT4 MSCS CLuster and now for at least 1 year on the new HW and SW platform.
Never had any problem since now when I received the following errors:
DBCC CHECKDB (SOI_Abitanti_PROD01) executed by LUGANO\SQL-Service found 1 errors and repaired 0 errors.
[Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 2048062382, index ID 0: Page (1:15733) could not be processed. See other errors for details.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in table 'presenza' (object ID 2048062382).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in database 'SOI_Abitanti_PROD01'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss i
When I saw this error I just re-check the database with DBCC CHECKDB but this time there was no errors anymore.
What could be the cause of that?
Do I have to worry about this?
You also may have to consider the following:
1)this database is no more updated, it's just a read only database for history purpose.
2)We recently have installed Lotus Domino 6.5.3 (1 month ago)
3)We recently upgraded from IBM DIrector version 4.12 to version 4.21. (1 month ago)
Please advise.
Kind regards.
Franco -
This is why I'm not a fan of using Maintenance Plans. I much prefer to code all the jobs myself so I get detailed output. When I'm in DBA mode (I'm currently doing SQL development) I use ISQL to run my DBCCs and pipe the output to a text file. It's run as a batch file that keeps 10 days of logs so I can review older runs in case I missed something.
Basically the batch file would do the following steps on every database every night (we didn't have terrabyte data stores):
dbcc checkdb
dbcc newalloc
dbcc checkcatalog
We originally also did checktable(syslogs) but that was turned off for 2000.
The advantage of the text file was that it gave you detail including full error messages.
But that's just me.
As far as what happened to you, I don't know. SQL Server can fix simple problems itself, that's the whole purpose for DBCCs. A lot of errors are transient, i.e. they show up on one run and are gone on the next. So if the error doesn't repeat, I wouldn't worry about it. The important thing is to look up the error message online and make sure it isn't one of the important ones. Consistency errors like what you got are generally not a problem and the DBCC handles it.
I really like SQL 2K compared to older versions because I would almost never see errors in my DBCC logs.
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font] -
Thanks a lot for the detailed explanation and for your time.
Regards.
Franco
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply