adjacent row delete bug
Posted in 1995
Topics: Error Codes & Troubleshooting, Connectivity: ESQL/C, 4GL & Embedded SQL, Platform-Specific Issues, Clustering, Grid & MACH11
All ... we are having a bit of a time with the adjacent row delete problem. I'm not cure of the Informix cust support verbage but basically we have been told that Informix will lock indices of adjacent rows to one we are locking explicity in a transaction. *(**********************************************************************)* -245 Could not position within a file via an index. The database server encountered an error looking up a row through an index. Check the accompanying ISAM error code for more information. The table file or the index file may have been corrupted. Unless the ISAM error code or an operating system message points to another cause, run the bcheck utility to verify file integrity. -144 ISAM error: key value locked. The current operation inserts a row having a certain primary key value, or updates a row to have a certain primary key value, but that key value has been deleted from the index by a transaction which has not yet been committed. This error is only seen when the lock mode is set to NOT WAIT. Treat it the same as error -107, record is locked: roll back the current transaction and re-execute it after a delay. Then, if the other transaction\\ was committed, the lock will no longer exist. If it was rolled back, the key will exist and this operation will receive a duplicate-key error. *(**********************************************************************)* We narrowed(or so we thought) our user model such we we could insert barrier rows between indexed groups of data. Since our deamon process manage data based on the unique indices on the table, a one-barrier row insertion between groups of data precluded the adjacent row anomoly. We are now seeing the problem with NON-adjacent rows. I am assuming we are banging up against another bug. Does anyone know a another like bug ?? While we are one the subject data and indices storage ... how does one determine the order of data and the related indeces ?? Is the ordering different for clustered indices(I assume so.) We are running HP-UX 9.01 INFORMIX EMBEDDED SQL for C Version 5.00.UC1 INFORMIX-4GL Run Time Facility Version 4.10.UE2 INFORMIX-SQL Version 4.10.UE2 INFORMIX-OnLine Version 5.00.UC4 Thanks in advance. Keith