Results 1 to 3 of 3
  1. #1
    Join Date
    Nov 2003
    Posts
    3

    Unanswered: Error: 605, Severity: 21, State: 1

    I'm currently helping in error-checking problematic SQL-server 2000
    installation.

    They've started to get this error in the log usually when the reindex-job is
    running on the database but sometimes at other times too:
    DBCC CHECKDB (ProductionDB) executed by DOMAIN\user01 found 0 errors and
    repaired 0 errors.
    Getpage: bstat=0x9, sstat=0, cache
    pageno is/should be: objid is/should be:
    Getpage: bstat=0x9, sstat=0, cache
    Getpage: bstat=0x9, sstat=0, cache
    pageno is/should be: objid is/should be:
    Getpage: bstat=0x9, sstat=0, cache
    (1:1772011)/(1:1772011) 0/930818378
    pageno is/should be: objid is/should be:
    pageno is/should be: objid is/should be:
    (1:1772011)/(1:1772011) 0/930818378
    (1:1772011)/(1:1772011) 0/930818378
    (1:1772011)/(1:1772011) 0/930818378
    ... IAM indicates that page is allocated to this object
    ... IAM indicates that page is allocated to this object
    ... IAM indicates that page is allocated to this object
    ... IAM indicates that page is allocated to this object
    Error: 605, Severity: 21, State: 1
    Attempt to fetch logical page (1:1772011) in database 'ProductionDB' belongs
    to object '0', not to object 'Table1'..

    The server is a failover-clustered server with SQL 2000 and Windows 2000.

    Before this problem they had a problematic HD that they replaced. The
    problem seemed to be gone after the replacement but resurfaced a little
    later.
    I started to think that the problem was related to the write-cache, so I
    checked the write-cache on raid-controller and it was turned off. Wanting to
    know if there was a possibility that the write-cache on the HDs was the
    problem I got the answer that there is no cache on the disks or at least no
    possablity to turn of the disk cache on them?
    I also get this message in the beginning of the sqliostress-testlog:
    "*** WARNING: Write caching ALLOWED"

    I still had a feeling that the problem was hardware related and ran
    sqliostress.exe and it came through fine. Thinking that the problem just
    appears under load I ran 5 simultanious instances of sqliostress and got a
    problem in one of the logs:



    Pattern for page 1 is A
    ERROR: LSN not found for page 1. Currently at slot 1 page 1 in log
    searching for LSN 3
    ---------------------------------------------------------------
    ERROR: Did not find expected pattern in file for page 1.
    Bytes read = 8192
    Potential torn write
    ---------------------------------------------------------------
    Sector: 0 LSN: 3 Page: 0
    [AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA...[sic]

    ERROR: Appears to be a premature truncation of file. Pages expected: 32000,
    Pages Read: 1, Last Error: 0
    Current LSN is 32001
    Verifing complete.


    Ok, what next? Is the problem the HD-cache or something else in the
    raid-system that possibly could create this problem or should I look
    somewhere else?

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,799
    Provided Answers: 11
    John
    Check the system event logs for message numbers 50 or 55. Also look for anything under source that looks like it may be related to disk. If you have such errors, chances are, the problem is still somewhere between the cpu and the disk. Easisest fixes will be checking to see that firmware on the various controllers, disks, and whatnot are all up to the same (good) level. Consult with your hardware vendor as to what that good level is.

    Good luck, and let us know what you find.

  3. #3
    Join Date
    Nov 2003
    Posts
    3

    Thumbs up Right!

    I found three event 50s in the system log.
    The description of the events is missing but now that I knew what to look for it was there.

    Everything should be up to date firmware-wise though but I'm talking to the vendor.

    Will let you know what they find.

    Thanx!!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •