Assertion Error

[Baron]

for some unknown reason I get the following error on Sqlanywhere 10 Database:

Internal database error ***ERROR*** Assertion failed: 202000 (10.0.1.3903).
Invalis string continuation at row id 0x11bee:0x0 -
transaction rolled back
SQLCODE=-301, ODBC 3 State="HY000"

Even when I try to rebuild the DB I get the same error during unloading. Could someone please help finding a solution?

[Breck_Carter]

Restore from a backup.

[VolkerBarth]

You might also try with the latest 10.0.1 EBF (10.0.1.4310 on Windows, AFAIK), if that issues the same assertion...

[Breck_Carter]

Where do you find V10 EBFs? I've only been able to find V12 in the archives...

https://support.sap.com/software.html
Support Packages & Patches - Access downloads
Archive by Alphabetical Index (A-Z)
S - SYBASE SQL ANYWHERE - 12.0
WINDOWS ON X64 64-BIT
Latest download: SQL Anywhere 12.0.1.4436 EBF

[VolkerBarth]

I don't find them, I just happen to save the last EBF of each major version we have used:)

(Not sure whether I could find that within archived versions of our SAP Support Portal accounts...)

[Breck_Carter]

[VolkerBarth]

LOL! That was not meant by my claim "I don't find them":)

Of course, they are perfectly filed so I don't have to search for them...

[Baron]

I could isolate the error source, there is was one cell (1 row / 1 column) in one of the tables which included some EXPLODABLE content. as soon as I try to query the row containing this row then I get the error, even when I try to update the value of this cell to a new value I get the same error.

The only solution was for me to delete this entire row, and then could find the same row in another remote DB and inserted it to this defective DB. The funny thing is that the remote DB has a correct value in this cell!! The DB is now healthy. Thanks for your efforts, could you but tell me what is meant with EBF?

[VolkerBarth]

An EBF is an Emergency Bug Fix, the former name for what now is called a SP aka Support/Service Pack.

Note when data is corrupted silently, it may be due to bad RAM...

[Baron]

OK, thanks. Is there any such repairing tool available for DB of SQLAnyhwere 10?

[Breck_Carter]

Stellar Phoenix Repair for SQL Anywhere

[Vlad]

The second time you suggest it 🙂