Hi Kjell,

>>Sounds like a "traditional" deadlock to me, but I don't know why it

would happen on insert... Any triggers that could be writing the same
record somewhere? Or anything else lika that, that gets triggered as a
side effect of the inserts?

Ah, good thought! My initial thought was, no, I don't, but I wet to go look and I see there is this on after insert of new tasks:

post_event 'new_task';

I'd forgotten I'd been experimenting with events at once stage!

And this on insertion of new support incidents:

IF (NEW.ID IS NULL) THEN
NEW.ID = GEN_ID(GEN_CUSTOMERINCIDENTS_ID,0);

(Which the person who originally wrote the app put in there, which I'm not so sure it's even needed...the FIBPlus component should be handling this AFAIK)


I think the next thing I'll try though, after setting up a dummy server (if the problem persists on the other server), will be to restore the database, to get it onto the new ODS, and see if that changes anything.

BTW, I use no_wait for all my transactions, so I usually get a deadlock exception rather than a hang. It's also so locked up, I can't get into the database at all. If it was just a deadlock, surely I should be able to at least get to the monitoring tables? And into other tables in the database that are not locked up?

Thanks
Maya