|
Hi all, I have encountered an assertion problem when doing some development with SQL Anywhere 16, which I have narrowed down and recreated in an empty database. I'm not sure if it makes a difference but the dbinit command was as follows: "C:\Program Files\SQL Anywhere 16\Bin32\dbinit.exe" -o "%TESTPATH%\testoutput.log" -p 4096 -s -t test.log -z 1252latin1(CaseSensitivity=Ignore) -zn uca(CaseSensitivity=Ignore;AccentSensitivity=Ignore;PunctuationSensitivity=Primary) "%TESTPATH%\test.db" Running the following statements: CREATE TABLE "DBA"."testing" ("key" INTEGER NOT NULL, PRIMARY KEY ( "key" )); INSERT INTO "DBA"."testing" ("key") VALUES (1); ALTER TABLE "DBA"."testing" ADD "test1" SMALLINT DEFAULT 0 NOT NULL; ALTER TABLE "DBA"."testing" ADD "test2" SMALLINT DEFAULT 0 NOT NULL; ALTER TABLE "DBA"."testing" ALTER "test1" DROP DEFAULT; ALTER TABLE "DBA"."testing" ALTER "test2" DROP DEFAULT; SELECT * FROM "DBA"."testing"; Results in the following error and the failure of the database service: Internal database error *** ERROR *** Assertion failed: 200610 (16.0.0.1324) Attempting to normalize a non-continued row (0x238:0x0) -- transaction rolled back SQLCODE=-301, ODBC 3 State="HY000" It appears to be the dropping of two defaults in a row that causes the problem (it can do one just fine as far as I can tell). Any thoughts or suggestions? |
|
Support have notified me that this is fixed in EBF 16.0.0.1506 or above. |
I should point out I have now logged this with Sybase through official support channels.
Thanks for reporting this issue Simon - I can also reproduce this quite easily. Thank you for the succinct reproducible.
May I ask which support channel you used - was this a case through your existing support plan or was this through the 'Report a Bug' website?
A case on our support plan via a colleague. I have received a case id and they have said they are looking into it.