Weird issues with id locks and auto-generated ids

Posted in 2004

CKGeier@nwc.edu — Tue, 25 May 2004 14:00:07 -0500 — source: Usenet: comp.databases.informix

This is a multipart message in MIME format. --=_alternative 006861EF86256E9F_= Content-Type: text/plain; charset="US-ASCII" One of our users terminals got stuck in a loop today. She was trying to update an id record, and it kept saying the record was locked. I ran 'wholock' and saw that her process was adding thousands of exclusive locks on an index to the id record. I told her to press escape and that seemed to release them. I then looked to see if someone else had that record locked, but they didn't. So I told her to try again, and it started to add the exclusive index locks again, this time I couldn't stop it without trying to close her database connections (that didn't work) and finally I had to kill her processes. Well, as you probably know, that left thousands of locks open on the system. Well, also, at the same time, there was a long transaction and we finally had to shutdown. After bringing it back up, we had a problem that has occurred before. Before letting others onto the system, we added a test record to the id record and it added the auto-generated id number of 658342. However, the maximum before we had the trouble was set to 555872, and there were no records in between the two numbers, nor should there be. So this loop the user was in appeared to update the maximum auto-generated number in this id table. How could this happen? This is entirely weird! Anyone else seen this? AIX 5.1 IDS 7.31 UD6 C Geier System Admin/IS support St. Paul, MN --=_alternative 006861EF86256E9F_= Content-Type: text/html; charset="US-ASCII" One of our users terminals got stuck in a loop today. She was trying to update an id record, and it kept saying the record was locked. I ran 'wholock' and saw that her process was adding thousands of exclusive locks on an index to the id record. I told her to press escape and that seemed to release them. I then looked to see if someone else had that record locked, but they didn't. So I told her to try again, and it started to add the exclusive index locks again, this time I couldn't stop it without trying to close her database connections (that didn't work) and finally I had to kill her processes. Well, as you probably know, that left thousands of locks open on the system.  Well, also, at the same time, there was a long transaction and we finally had to shutdown. After bringing it back up, we had a problem that has occurred before. Before letting others onto the system, we added a test record to the id record and it added the auto-generated id number of 658342. However, the maximum before we had the trouble was set to 555872, and there were no records in between the two numbers, nor should there be. So this loop the user was in appeared to update the maximum auto-generated number in this id table. How could this happen? This is entirely weird! Anyone else seen this? AIX 5.1 IDS 7.31 UD6 C Geier System Admin/IS support St. Paul, MN --=_alternative 006861EF86256E9F_=-- sending to informix-list