SQL Anywhere 10.0.1.3831

E. 2009-09-11 21:55:41. SQL statement failed: (-305) I/O error Fatal
error: A disk read from file "D:\FHMSL\iFHMS\Data\Feedlot111.db"
failed with error code: (38) -- transaction rolled back
E. 2009-09-11 21:55:41. Error while executing hook procedure
sp_hook_dbmlsync_end.

Received this error while running a proc during sync. Tried to
validate the db in Sybase Central resulting in the same error.

I saw the post at
http://groups.google.com/group/sybas...4160e576?fwc=1
and am wondering if there is another way besides using a backup copy
or rebuilding from Consolidated. It is quite possible that the db was
run on a lower build, corrupted, and updated as suggested in the post.
Could a physical disk problem such as bad sectors also cause this?

Sohaib,

=====================
C:\>net helpmsg 38

Reached the end of the file.
=====================

It seems that the file is shorter than expected on the filesystem. This
could happen in various ways, but likely it's at the filesystem level.
Bad blocks or a sudden power outage with outstanding writes against a
disk might produce a database that looks like this. We have initial
reports from some customers that running the database as a service with
automatic restarts (for Windows Update) may also produce a scenario like
this in very specific instances.

Going to your backup copy is the way to get the database back up and
running. You may be able to use the transaction log to bring the
database up-to-date (e.g: dbeng10 <database> -a Feedlot111.log) -
http://dcx.sybase.com/html/dbdaen10/...-dbengine.html

Regards,

Sohaib Uthmani wrote:
--
Jeff Albion, Sybase iAnywhere

iAnywhere Developer Community :
http://www.sybase.com/developer/libr...ere-techcorner
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
SQL Anywhere Patches and EBFs :
http://downloads.sybase.com/swd/summ...&timeframe =0
Report a Bug/Open a Case : http://case-express.sybase.com/cx/