Re: Problem Locking in Exclusive Mode

Jim Burks (jburks@promus.com) wrote: : In article <2ncnm5$p2c@emory.mathcs.emory.edu>, nnob@seq1.loc.gov (Nick Nobbe) says: : > : > Trying a rather massive delete (25 K rows) while in a transaction and : > locking the table in exclusive mode, Informix reports something along : > the lines of "Unable to update transaction log" and also "ISAM error". : > : > Selecting smaller sets for deletion worked, however. : > : > Also, with no problem whatsoever, setting locking to share mode. : > : > Using Informix SE 5.01 with SCO Unix 3.2.2. Is this a known bug? : > In addition to Jim Burks suggestions, you can create another database with an identically defined table in it (same name etc etc). Then link the original datafiles (with extrme care - do it the wrong way and you're searching for that backup tape!) to the datafiles int the new database. You then run the new database without transactions for the purposes of these deletes .... assuming of course you don't mind the deletes not being logged... apart from that it seems to work fine. Note that this is partly possible because of the locking method used on the SCO platform. (Both normal & symbolic links will work). Bye the way, make sure you reproduce any indexes in the new version of the table BEFORE doing the links. Scott McClintock MU Systems Pty Ltd Brisbane - Down Under.