Informix error 310
Baan: Baan IVc4
Yesterday, we got an Informix error 310 "SQL: Cardinality Violation" when running a very simple update session. The update only sets a tcyesno field to either Yes or No. The table contains a tcitem as primary key, one tcyesno field and two integer fields and has about 65.000 rows. So, all basic.
I found that one item had this problem; when I just skipped the update for this specific item, the complete table could be updated.
The quick solution was: Reorgainze Tables. After that, all wored fine.
Now my question: Has anyone ever had such an error, too? I guess that this problem came from the fact, that our db resides on SSDs now.