migration problem (7.24 to 7.30)
Hello All, After we have migrate the informix-server from 7.24 to 7.30.UC2 we get a lot errors : sqlerr -245 (could not position within a file via an index) and the ISAM error -154 (lock timeout expired). By registration (updates and inserts) we use Stored Procedures, we set LOCK MODE TO WAIT 12, and ISOLATION LEVEL TO DIRTY READ; Is it a good idea to increase the lock mode or to change the isolation level (to Cursor Stability). Other sugestions ? Thanks in advance, Siebe de Klaver (s.w.deklaver@interedge.nl)
Siebe de Klaver wrote: > > Hello All, > > After we have migrate the informix-server from 7.24 to 7.30.UC2 > we get a lot errors : sqlerr -245 (could not position within a file > via an index) > and the ISAM error -154 (lock timeout expired). > > By registration (updates and inserts) we use Stored Procedures, we set > > LOCK MODE TO WAIT 12, and ISOLATION LEVEL TO DIRTY READ; > > Is it a good idea to increase the lock mode or to change the isolation > level (to Cursor Stability). > > Other sugestions ? > > Thanks in advance, > > Siebe de Klaver (s.w.deklaver@interedge.nl) Hi Siebe, just some suggestions: First have a look at your tables lock_level. If it is page, change to row. Another thing to mention is a new feature of 7.3: subquery-flattening. We have a similar problem with correlated subqueries in update-statements, where a bunch of rows is locked, though the statement does not do any update, as the where-clause doesn't match any row. You can disable subquery-flattening by setting the environment-variable NO_SUBQF to 1 before starting the server. If it helps you, keep in mind that subquery-flattening is a performance-feature, and examine every new versions of the engine, whether this is still necessary. This one is reported to technical support, but isn't yet acknowledged as bug. (so i can't tell you which version will have a fix for this) hth martin
In article <36DBBBE3.5C544FF0@interedge.nl>, Siebe de Klaver <s.w.deklaver@interedge.nl> wrote: > > --------------9C0966D59D9C234AA5093509 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > Hello All, > > After we have migrate the informix-server from 7.24 to 7.30.UC2 > we get a lot errors : sqlerr -245 (could not position within a file via > an index) > and the ISAM error -154 (lock timeout expired). > > By registration (updates and inserts) we use Stored Procedures, we set > LOCK MODE TO WAIT 12, and ISOLATION LEVEL TO DIRTY READ; > > Is it a good idea to increase the lock mode or to change the isolation > level (to Cursor Stability). > > Other sugestions ? > > Thanks in advance, > > Siebe de Klaver (s.w.deklaver@interedge.nl) > Probably in your old database your locking granuality was row, but when you you migrate to your new database, your locking granuality became page, which is default. If this is your case - check your locking granuality to row. With best regards, Juri Dovgart, Bank's "Ukraine" System Administrator ‰ -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own