Re: Lock Timeouts - Help needed

James McCallum <james.mccallum@bradford.gov.uk> wrote in article <6slvjg$evj$1@newsreader1.core.theplanet.net>... > We have migrated from an Online 5.0 engine on a SPARC machine to > Online 7.02 on an Intel machine. > > We ran the normal dbexport and dbimport and got the database up and > running. We then ran update statistics to optimise the system. > > We are now getting masses of Lock Timeouts on tables across the > database. <snip> When you did the dbimport, most likely all tables defaulted to a locking mode of page. You need to execute ALTER TABLE statements now to change the locking mode back to row. You also probably lost extent sizing and dbspace placement information during the dbexport/dbimport. If your database is in a single dbspace then the dbspace placements won't matter. Also, the dbimport will have greatly reduced the number of extents initially, but you may need to alter your next extent sizes to get good allocations going forward. If your database is small, this is not likely to matter much. When doing a dbexport/dbimport to migrate data under 7.x and later, you can use the "-ss" option on the dbexport to preserve lock mode, dbspace and extent sizes. When coming from 5.x you don't have this option. In either case you CAN edit the schema file produced by dbexport to set the proper options on the create table statements prior to doing the dbimport. Finally, update statistics is a whole different animal under 7.x than 5.x. A simple global "update statistics" will probably not yield the best possible performance. Check out http://www.objectsoft.com for a a shell script which does one of the Informix recommended sequences of update statistics commands. I believe there is also an ESQL/C version of something similar in the IIUG archives. HTH Irwin Goldstein Objective Software Systems, Inc.