07-06-2009 08:14 AM
Solved! Go to Solution.
07-06-2009 10:49 AM
Yeah, I hadn't heard of that possibility either, but I figured I'd check it out. It turns out to be a Sybase bug where heavy load on a filesystem device that is on a full filesystem will generate errors. So, it isn't a corrupted file at all. Oh well. :)
Thanks for your response.
07-06-2009 09:59 AM
07-06-2009 10:49 AM
Yeah, I hadn't heard of that possibility either, but I figured I'd check it out. It turns out to be a Sybase bug where heavy load on a filesystem device that is on a full filesystem will generate errors. So, it isn't a corrupted file at all. Oh well. :)
Thanks for your response.