Submitted by: Francisco Fernández (fcofdezapei)

Duplicates CORE1958

I have an insert query that fires a trigger in my database, this trigger tries to update a table in an decimal(12,5) data collumn. This is like a resume table that keeps the sum of the collumn at first one. The trigger tries to reduce the value of the collumn of the master table so it gets a negative value. This action fires a check that validates the value must be higher or equal to zero.

The first time I do the insert I get a correct error indicating this situation an telling me that the check is violated like this:

Operation violates CHECK constraint on view or table.
Operation violates CHECK constraint INTEG_167 on view or table LOTES_X_ALMACEN.
At trigger 'CHECK_143'
At trigger 'BI_KARDEX' line: 81, col: 7.

Then without doing a commit or rollback to the transaction, I do the same insert query (only changing the primary key of the registry I tried to insert the first time) and this time I get the check error, but this one:

Operation violates CHECK constraint on view or table.
Operation violates CHECK constraint INTEG_167 on view or table LOTES_X_ALMACEN.
At trigger 'CHECK_143'
At trigger 'BI_KARDEX' line: 81, col: 7.
internal gds software consistency check (decompression overran buffer (179), file: sqz.cpp line: 222).

After this any query produces the following result:

Unsuccessful execution caused by a system error that precludes
successful execution of subsequent statements.
internal gds software consistency check (can't continue after bugcheck).

I hope this information can be usefull. I also have a little database 4mb aprox. and a script that we created to reproduce the bug, but I don't know if I can send it to you.

Thank's in advance.

P.S. Sorry if my english isn't good enougth.