Problem with customer database: dbsrv16 keeps crashing while unloading a database. it crashes always at the same table with failure: "Assertierung fehlgeschlagen" seems to fail always at unloading the same table.
What can cause such a problem? I have inconsistencies in another databases primekey index too, used by the same software.
Appending the crash details here:
Server SQL Anywhere 16 126.96.36.1992:
Command dbunload -v -c "UID=sirius;PWD=***;Server=sa16jw;DBF=/home/jw/Kunden/PerformanceTest/Database/PerformanceTest.db;LINKS=TCPIP()" -r "/home/jw/Kunden/PerformanceTest/reload.sql" -ii "/home/jw/Kunden/PerformanceTest/unload"
asked 08 Feb, 12:01
There used to be tech note titled "I've Got An Assertion! What Should I Do?" but I can no longer find it.
You may have a corrupted disk, or RAM errors, or a combination of both.
In an ideal world, you will restore the database to a different computer, from a recent backup.
In a less-than-ideal world, you may not have a usable backup, so...
If you suspect RAM errors, further attempts to use the database may result in permanent disk errors as corrupt RAM values are written to the disk. It is suggested you stop updating the database until the data can be rescued.
If you already know which table is having problems, you can uses dbunload with -t to unload all the other tables.
If the primary key is having problems, try dropping the primary key before unloading that table.
Do not write the unloaded data to the same suspect disk; consider using an external USB 3 drive.
Run an extended RAM check on the suspect computer, or just replace the RAM (especially if you have recently installed suspect chips).
Same thing with the disk drive, to make sure any corruption is transient; i.e., bad stored values rather failing bits.
Do that before trying to rebuild the database from the unloaded data.
answered 10 Feb, 14:03