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.
| Author |
Topic |
|
agiotti
Starting Member
37 Posts |
 Posted - 2009-04-01 : 20:07:04
|
Hello All, Environment:Windows 2000 sp4SQL Server 2000 sp4 build 2187EMC SAN attached storage.We cannot move off this platform until the third-party vendor certifies their application. :-(Receiving the following error when DBCC run prior to the backing up the database. Once the error is generated maintenance halts. We would then manually run DBCC’s with the ALL_ERRORMSGS option and the error disappears.Problem is occurring once a week. Different tables each occurrence.Same database – more than one database on the server sharing the same physical disks no problems with them.We have asked the hardware team to run diagnostics and check all the firmware and drivers. They are very reluctant because there are no errors found in the event logs and HP integrated log viewer.We have asked the SAN team to look for any issues, they replied with no errors found, i.e. HBA, power path logs, fabric, etc…Any guidance would be appreciated. I also plan on running SQLIOSim to hammer the server.Msg 2533, Sev 16: Table error: Page (1:303495) allocated to object ID 2105058535, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header. [SQLSTATE 42000]Msg 2533, Sev 16: Table error: Page (1:303512) allocated to object ID 2105058535, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header. [SQLSTATE 42000]Msg 0, Sev 16: DBCC For Database: QSDB Started at: Apr 1 2009 7:52AM [SQLSTATE 01000]Msg 2533, Sev 16: Table error: Page (1:303513) allocated to object ID 2105058535, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header. [SQLSTATE 42000]Msg 2533, Sev 16: Table error: Page (1:303514) allocated to object ID 2105058535, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header. [SQLSTATE 42000]Msg 2533, Sev 16: Table error: Page (1:303515) allocated to object ID 2105058535, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header. [SQLSTATE 42000]Msg 2533, Sev 16: Table error: Page (1:303516) allocated to object ID 2105058535, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header. [SQLSTATE 42000]Msg 2533, Sev 16: Table error: Page (1:303517) allocated to object ID 2105058535, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header. [SQLSTATE 42000]Msg 2533, Sev 16: Table error: Page (1:303518) allocated to object ID 2105058535, index ID 0 was not seen. Page may be invalid or have incorrect object ID information in its header. [SQLSTATE 42000]Msg 8990, Sev 16: CHECKDB found 0 allocation errors and 10 consistency errors in table 'GroupMembersTemp' (object ID 2105058535). [SQLSTATE 01000]Msg 8989, Sev 16: CHECKDB found 0 allocation errors and 10 consistency errors in database 'QSDB'. [SQLSTATE 01000]Msg 8958, Sev 16: repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (QSDB ). [SQLSTATE 01000]Thanks in Advance,Paul Randal hope your out there.  |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2009-04-02 : 04:04:13
|
| When you run the DBCC, have you got any of the repair options turned on?REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST | REPAIR_REBUILD If so, this may be why you are not seeing an error afterwards. |
 |
|
|
|
|
|
|
|
Disappearing DBCC Errors