Re: Large UPDATE crashes (ISAM error -121)

Path: emory!wupost!sdd.hp.com!usc!ucla-cs!ucla-mic!agsm!ggordon From: ggordon@agsm.ucla.edu (Glen Gordon) Newsgroups: comp.databases.informix Message-ID: <ggordon.700279774@uclagsm> Date: 11 Mar 92 02:16:52 GMT References: <953@rand.mel.cocam.oz.au> Nntp-Posting-Host: risc.agsm.ucla.edu shaneb@auzodt3.mel.cocam.oz.au (Shane Booth) writes: >I have often had a problem with UPDATE's on tables with large >numbers of rows where you wish to change a fair proportion of >the records. This morning, I had a 12000 row database, each >row is 224 bytes in size. I tried to update ~8000 of these rows >in a single UPDATE, and isql came back with ISAM error -121: > Cannot write to transaction log >Three questions: > 1) Has anyone had this problem before? Yes. The system acquires a lock or two for each row which is updated. There are a finite number of locks available in the system. When all locks have been acquired, everything stops. > 3) Is there any way to get around the problem without > a) doing 50 small UPDATE's instead, or > b) going to On-line? Lock your table in exclusive mode before doing a large update. --Glen -- Glen Gordon | Internet: ggordon@agsm.ucla.edu Computing Services | Bitnet : ggordon@uclagsm.bitnet Anderson Graduate School of Management | AT&Tnet : (213) 206-6590 University of California, Los Angeles | Fax : (213) 206-2002