Question Re: SA16 applying transaction log causes assertion in Technology Q&A

SA16 applying transaction log causes assertion

Former Member — Fri, 13 Sep 2013 16:26:48 GMT

We have a client who is running Sybase 16.0.0.1535 and experienced an assertion error. We are trying to assist them with repairing the database by re-applying the current translated log file to the last good backup (using DBISQL to read the translated log file to the DB). It runs for a while and then crashes with the error:

Could not execute statement. Internal database error ERROR Assertion failed: 200610 (16.0.0.1535) Attempting to normalize a non-continued row (0xb26:0x0) -- transaction rolled back SQLCODE=-301, ODBC 3 State="HY000" File: "Trans.sql" on line 83027, column 1 You can continue executing or stop.

--SQL-1012-0004124849 alter table "DBA"."user_tab6_data" alter "Type_of_Misdemeanor" varchar(35)

Any help on this is greatly appreciated!

Re: SA16 applying transaction log causes assertion

Former Member — Sat, 14 Sep 2013 16:29:39 GMT

Have you validated the database to make sure the originaly DB is not corrupt?

Re: SA16 applying transaction log causes assertion

Former Member — Sat, 14 Sep 2013 17:14:01 GMT

An unload/reload of a copy of the backup database may be necessary to remove any inconsistencies. Also, are you running any TRUNCATE statements on the database start-up event? It may be necessary to upgrade to the latest EBF

Re: SA16 applying transaction log causes assertion

Former Member — Mon, 16 Sep 2013 13:42:39 GMT

Thanks so much for the prompt replies! I had validated the backup copy of the database and also rebuilt that backup copy prior to trying to apply the translated log file to it and had receved the same error.
We are not running any truncate statements at startup.
I just got done trying to fix it with the latest EBF (16.0.0.1644) that was posted on Friday and that did fix the issue! I was able to apply the translated log file to the backup copy without any issues.