Post reply

Time to reinstall Sql Server?

  • October 21, 2003 at 12:50 am

    #160886

    I have a maddening problem with Sql 2K Server, Sp3.

    Maybe once a week the Integrity job (via Database Maintenance plan) for a particular server reports a database anomaly:

    13] Database Pers: Check Data and Index Linkage...

    [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 516912913, index ID 0: Page (1:23566) could not be processed. See other errors for details.

    [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 516912913, index ID 0, page (1:23566), row 16. Test (ColumnOffsets + (int)sizeof (UINT16) <= (nextRec - pRec)) failed. Values are 33 and 32.

    [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in table 'tblPersHist' (object ID 516912913).

    What's maddedning is that the error seems to be randon and hits random DB's on the same server. Last week the nightly Integrity check failed. I re-ran it the next morning and it passed and I didn't have any problems with the server for a week. Then all of a sudden the problems were back in a different database. This time I ran the Integrity job and it still failed on the the DB\table.

    This is the only sql server in the joint that acts so strangely. Any thoughts on what to do about this one?

    TIA,

    Bill

  • October 21, 2003 at 6:02 am

    #478922

    Nothing else happening at the same time as the intregrity checks? Reorgs maybe?

    Cheers,

    - Mark


    Cheers,
    - Mark

  • October 21, 2003 at 5:18 pm

    #479018

    How's you network connectivity?

    Maybe you have a dodgy NIC or driver.

    Hope this helps

    Phill Carter

    --------------------

    Colt 45 - the original point and click interface

    --------------------
    Colt 45 - the original point and click interface

  • October 22, 2003 at 3:15 am

    #479049

    I think you have to make this table again by

    1- make a new table with the same design in a new DB

    2- copy data from orginal table to that table

    3- make integrity check on that new DB and table .. so you know if the problem is in the data you copied ..

    4- in the faulty table .. remove its relathionship with other tables ..

    (note : (Idea) here you can go to your faulty table and open design Table and change fields size a little bit .. and save again the table .. and chack integrity again on that table ...

    if ok ... then make relationship again and skip the rest of these steps

    else .. then complete the steps below)

    5- remove the table from Db .. and make integrity check again on DB to make sure that problem has been solved

    6- copy the new table to that DB and make again the relathionships with other tables ..

    7- make integrity check again on DB to make sure that the problem has been solved..

    I hope this helps you

    Alamir Mohamed

    Alamir_mohamed@yahoo.com


    Alamir Mohamed
    Alamir_mohamed@yahoo.com

  • October 22, 2003 at 5:18 am

    #479063

    - did you perform checkdisk ?

    - does the server report memory-bank-problems ? (eventvwr/system)

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • October 22, 2003 at 6:09 am

    #479070

    (Assuming the answer to Mark's execllent question is negative.)

    As you have determined that the problem is with the server and not any particular database, it's either a hardware problem or corrupted system software (as in your subject). It's most likely a hardware problem if SQL Server is otherwise behaving. It's not a network issue as DBCC runs on the server. Assuming this is true server hardware (with ECC memory), I'd suspect the disk channel.

    --Jonathan



    --Jonathan

  • October 22, 2003 at 6:46 am

    #479084

    Are there any errors in the Windows Event Logs for the same time as the SQL errors?

    -SQLBill

  • October 23, 2003 at 9:02 pm

    #479392

    Thanks to evetyone for their help.

    For reasons I don't understan I beleive that the culprit was the "reorg" job we run nightly at 12am. I stopped that job and our problems seem to have vanished (time willl tell.)

    From what I understand the reorg doesn't lock the databases fully and the integrity job may be picking up some data "in transit" from the reog job.

    Bill

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

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