Re: isql detail table update?
Posted in 1993
In article <2casnkINN9n9@emory.mathcs.emory.edu>, jerry <warlok!kysilk.sherwood.com!jerry@uunet.UU.NET> wrote: >---- original message from Joseph A. Miele / News Administrator ---- >++ >++ In article <753287674snz@ipaedin.demon.co.uk>, >++ Malcolm McLean <Mmclean@ipaedin.demon.co.uk> wrote: >++ >In article <CGGnwp.4G5@perk.jpr.com> news@perk.jpr.com writes: >++ > >++ >Try this:- > >You are running out of locks, the only way around it is to lock the >table in exclusive mode. When you do that then you only have to have >one lock. Your other choice is to really crank up the kernal locks, >set it in the thousands. > > >begin work; > >lock table atkliqud in exclusive mode; > >++ > >++ >update atkliqud >++ > set unit_type = "Sludge" >++ > where atkliqud.tk_num in ( >++ > select >++ > atkliquh.tk_num from atkliquh >++ > where atkliquh.job_num = 100 >++ > ); > >commit work; > >++ > >++ >-- >++ >++ >++ Your query works me if only a few records are updated. In a case where a >++ few thousand records are updated I get the following isql runtime errors: >++ >++ Sometimes: >++ 346:Could not update a row in the table >++ 121:ISAM error: could not write log record >++ >++ Othertimes: >++ Fatal system error: ignoring modifying buffer >++ 408: Invalid message type received from sqlexec process. >++ >++ I think these errors are OS kernel related. Were running SCO ODT 3.0. I >++ tried bumping the FLCKRECS up to 300 from 100 and that did not make a >++ difference. Any other ideas? >++ > Jerry: Your correct again. Thankx. Iv'e been on the phone for two days now with informix trying to fix this and your locking the table in exclusive mode is exactly what they have FINALLY suggested. NEW Problem discovered: When diagnosing why I was having problems I discoverd that bcheck on systables give the following error when every anyone is in the database: C-ISAM ERROR: 113 unknown error code. Any Ideas? -- Unix at Home perk machine Joseph A. Miele jam@perk.jpr.com Dir MIS Spectraserv, Inc. 76207.1365@compuserve.com