| Author |
Message |
balford
Joined: 14 May 2008 Posts: 1 Location: Seattle, WA USA
|
Posted: Tue Jun 10, 2008 11:44 pm Post subject: Unhandled BLOB type for 167 |
|
|
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 |
|
| Back to top |
|
 |
meb97me
Joined: 04 Nov 2008 Posts: 1
|
Posted: Tue Nov 04, 2008 12:15 pm Post subject: |
|
|
hi
not resolved this i'm afraid but i've just come across the same issue myself
so any help also appreciated |
|
| Back to top |
|
 |
Robert
Joined: 30 Oct 2006 Posts: 428 Location: Cambridge, UK
|
Posted: Tue Nov 04, 2008 2:56 pm Post subject: |
|
|
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
Developer, Red Gate Software Ltd |
|
| Back to top |
|
 |
|
|
All times are GMT + 1 Hour
|
| Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group