Re: Lock errors - your knee jerk opinions?

sumGirl wrote: > I have a process that runs everyday, lots of short jobs usually back > to back, loading data into tables. This process has been around since > our business was tiny, but over the past few years we hacve grown alot > and now from time to time I have seen the following error messages. > Each time I see the error its always it seems like its when my data > loads are larger than normal and the process is very long running (12+ > hours) and that seems to be the only thing in common during the > errors. > > I know from experieince that I can usually just resubmit the same > exact job and data and its likely to run fine on the second try. I > know you dont know my code and table structures, but whats your knee > jerk opinion of whats going on? I am a sysadmin and not a programmer, > but my opinion is that the application lacks any lock maangement logic > and the fact that it runs as well as it does normally might be the > product of good luck/good timing? > > -211 > __________________________________________________________ > Cannot read system catalog catalog-table. ... > > -144 > __________________________________________________________ > ISAM error: key value locked. ... What is the O/S? What is the version of IDS? Are there drop / create tables / indexes? Are there update statistics? Can you repro in a test environment? You could trap the error and see what sql is actually running (onmode -I)