Unhandled BLOB type for 167

balfordbalford Posts: 2
edited November 4, 2008 8:56AM in SQL Log Rescue
After processing the full backup file (.bak) and 10 transaction log (.trn) files and reaching 28% on post processing, this error comes up. I should never have bragged about how helpful Log Rescue was going to be.

Has anyone else seen this error and resolved the issue?

Thanks,
Bob Alford
· Share on Twitter

Comments

  • meb97memeb97me Posts: 1
    hi

    not resolved this i'm afraid but i've just come across the same issue myself

    so any help also appreciated
    · Share on Twitter
  • Robert CRobert C Posts: 425 Silver 2
    Hi,

    I've just had a quick look in the code, and it appears to be a varchar entry that for some reason is ending up in an area that SQL Log Rescue thinks should be a BLOB (remembering that SQL2000 didn't support varchar(max)).

    The only thing I can think of here is if a column changed data type some time in the past, from a text column to varchar?

    It might be worth trying again with only the more recent transaction log backups - if the error occurs in an earlier backup, that could allow you to recover at least the latest transactions.

    Sorry I can't be of more help!

    Robert
    Robert Chipperfield
    Red Gate
    · Share on Twitter
Sign In or Register to comment.