Re: isql detail table update?

---- 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? ++ ++ -- ++ Unix at Home perk machine ++ Joseph A. Miele jam@perk.jpr.com ++ Dir MIS Spectraserv, Inc. 76207.1365@compuserve.com ++ -- Jerry M. Denman -- Director of Technical Services 4gen!warlok!jerry Sherwood Systems (a division of Sherwood Mfg Co. Inc.) jerry@sherwood.com 4760 N. Central Phone:(602) 230-8188 Phoenix AZ, 85012 FAX:(602) 230-9491 ------------------------------------------------------------------------------ More harder stuff faster, with less good people and it's got to be more right -- Bill Orr, Informix Software