We recently upgraded our databases from SQL Anywhere 10 to SQL Anywhere 12 (188.8.131.5256).
After this we receive an assertion failures very often.
Here is some of them:
Is there a way to prevent such failures? Were they resolved in the EBF?
asked 30 Aug '11, 03:34
The first and last assertions that you mentioned (201129 and 200130) are indicative of physical corruption of the database file, which we see from customers periodically when the database is stored on an SD card. Unfortunately, SD card storage is, often, not nearly as robust as other media. The second assertion, 201501, has a number of potential causes, but physical corruption is one of them.
I suggest you copy the database from the SD card, put it on a Windows XP (or Vista or Windows7) machine and see if you can start the database; then try to validate the database file using dbvalid.
answered 31 Aug '11, 09:52
Sounds to me like an error of the underlying filesystem. Is the error independent of the used hardware?
answered 30 Aug '11, 04:50