ONLINE 6.0 Locking

> From: jesolom@pbrock.srv.PacBell.COM (Rock Solomon) > Date: 14 Jun 1995 18:15:45 GMT > > I have a database with logging turned off, because I'm making a lot of changes > to it, and will turn logging on later. My problem is that I have declared a > cursor that includes all the records in a table, and update particular ones > in the process. What happens is the program eventually fails because the lock > table overflows. Without "logging", how do I "commit" these updates every so > often so this does not occur? > > -- > ----------------------- > J.E. "Rock" Solomon Jr. > jesolom@PacBell.COM > (510) 867-6615 You must change your program to update fewer rows at a time, or--even better-- increase the number of locks. TFM states that locks are cheap, and the default setting of 2,000 seems ludicrously low to me. I increase the locks to somewhere between 50,000 and 100,000 for databases who's tables contain about that many rows. Max locks is 250,000. The cost is shared memory. If you overlock you run the risk of totally hosing the indexes and data for the table. I've had to restore from archive before for that reason. Watch out! __________________________________________________________________ | Clem Akins Standard Disclaimers Apply | |Reynolds Metals Co, Alloys Plant "Climb High, Cave Deep!" | | Muscle Shoals, Alabama USA cwakins@leia.alloys.rmc.com | |________________________________________________________________|