Glad to hear that:)

However, please note that paragraph from the doc you have quoted:

Even if the validation process does not return errors after validating a database, once an assertion condition has been hit, there is still potential for corruption of the database file during runtime. The only way to guarantee removal of all pre-existing corruptions in the database file is to rebuild the database using the unload/reload process. The ability to restart the database file on a database server alone does not guarantee that the database file is free from corruption. See: The rebuild process for SQL Anywhere 10 and later databases

In addition to Volker's suggestion, you should do hardware-level checks of both the hard drive AND the computer memory. Memory failures can appear as data errors, even hard drive errors... every single piece of software uses memory to perform data checking, so you really never know what the problem is until you check the memory.