October 18, 2011 at 4:57 am
Job 'Integrity Checks Job for DB Maintenance Plan 'xxxxxxx Database Maintenance Plan'' : Step 1, 'Step 1' : Began Executing 2011-10-17 22:30:02
output
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
(null)
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.2039
Copyright (C) Microsoft Corporation, 1995 - 1998
(null)
Logged on to SQL Server 'xxxxxxxxxxxx'
as 'NT AUTHORITY\SYSTEM' (trusted)
(null)
Starting maintenance plan 'xxxxxxxxx Database Maintenance Plan' on 10/17/2011 10:30:03 PM
(null)
[1] Database Assert: Check Data and Index Linkage...
(null)
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 2576: [Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (3:51165) object ID 1275867612 index ID 0 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:424) object ID 1275867612 index ID 9 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:481) object ID 1275867612 index ID 10 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (3:22) object ID 1291867669 index ID 0 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:256) object ID 1307867726 index ID 0 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 1275867612)' (object ID 1275867612).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object ID 1291867669)' (object ID 1291867669).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object ID 1307867726)' (object ID 1307867726).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 5 allocation errors and 0 consistency errors in database 'Assert'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Assert ).
(null)
(null)
The following errors were found:
(null)
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (3:51165) object ID 1275867612 index ID 0 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:424) object ID 1275867612 index ID 9 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:481) object ID 1275867612 index ID 10 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (3:22) object ID 1291867669 index ID 0 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]IAM page (0:0) is pointed to by the previous pointer of IAM page (1:256) object ID 1307867726 index ID 0 but was not detected in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 3 allocation errors and 0 consistency errors in table '(Object ID 1275867612)' (object ID 1275867612).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object ID 1291867669)' (object ID 1291867669).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 0 consistency errors in table '(Object ID 1307867726)' (object ID 1307867726).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 5 allocation errors and 0 consistency errors in database 'Assert'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Assert ).
(null)
** Execution Time: 0 hrs, 34 mins, 35 secs **
(null)
(null)
Deleting old text reports...
0 file(s) deleted.
(null)
(null)
End of maintenance plan 'xxxxxxxx Database Maintenance Plan' on 10/18/2011 12:14:59 AM
(null)
SQLMAINT.EXE Process Exit Code: 1 (Failed)
(null)
Msg 22029, Sev 16: sqlmaint.exe failed. [SQLSTATE 42000]
Integrity job is failing with the above error details.Please help me to resolve this issue.
October 18, 2011 at 5:04 am
I think the easiest way is to google for something along the lines of 'sql server 2000 error 2576'.
Ronald HensbergenHelp us, help yourself... Post data so we can read and use it: http://www.sqlservercentral.com/articles/Best+Practices/61537/-------------------------------------------------------------------------2+2=5 for significant large values of 2
October 18, 2011 at 5:21 am
Thanks Ronald. So it seems to be some problem with the indexes or data in the database...Either may be corrupted.. Am i rgt? How i can further proceed in this case to fix this issue..Appriciate your help.. Thanks in advance.!!!!!
October 18, 2011 at 5:25 am
Are you in a hurry to fix this?
I'd call in an expert on this one. I'm just not 100% sure you can fix it without losing any data (index 0).
October 18, 2011 at 5:41 am
Not so urgent Ronald.Any help on this would do when you find time.This job is failing from long time with the same error.Thanks again.
October 18, 2011 at 5:47 am
Mithra (10/18/2011)
Not so urgent Ronald.Any help on this would do when you find time.This job is failing from long time with the same error.Thanks again.
While we wait for Gail, do you have any valid backups in case we need them?
Pls test them to make sure they are not corrupt as well.
October 18, 2011 at 5:50 am
Failing for a long time, just how long is that? Also, do you have a good backup from before you started getting this error?
October 18, 2011 at 7:21 am
Let me see if I have this correctly, a job has been reporting that your database is corrupt for a long time and nothing's been done? Wow.
Got a clean backup?
If nto, you'll have to repair. Take the database into single user mode and run CheckDB with the repair allow data option. This looks like metadata corruption and iirc it can be repaired without actually losing anything. In most cases.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 18, 2011 at 7:23 am
You might want to take a backup of the corrupt db as well before running repair. That way you can try again with other options in need be & possible.
October 18, 2011 at 7:48 am
Okay, still learning interesting things about logs and reports.
IAM page (0:0) is pointed to by the previous pointer of IAM page (1:481) object ID 1275867612 index ID 10 but was not detected in the scan.
I'm not sure how to translate this. Obviously, the IAM page with object ID 1275867612, index of 10 is "missing". But what's that bit at the beginning mean?
October 18, 2011 at 8:00 am
Brandie Tarvin (10/18/2011)
Obviously, the IAM page with object ID 1275867612, index of 10 is "missing".
Nope, the IAM page is intact. The sentence reads <one IAM page> was pointed to by <another IAM page> but was not detected in the scan. It's the first one that's missing, SQL knows its missing because <another IAM page> has a pointer to it.
But what's that bit at the beginning mean?
IAM pages form a chain, they each have a pointer to the previous IAM chain and the next. This one says its pointing to 0,0 which was not seen. Now that's obviously not possible, as there is no page 0,0. What this actually means is that the pointer from sysindexes to the firstIAM is missing (query sysindexes on SQL 2000 and there's a column firstIAM that's binary, it's a page reference to the first IAM page in the chain). Hence the comment that this is metadata corruption.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 18, 2011 at 8:15 am
Thank you for the clarification.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply