Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.oracle    |    Overblown overpriced overengineered SHIT    |    2,288 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 353 of 2,288    |
|    Tim Callaghan to All    |
|    Diagnosing Transaction Enqueue (TX) Lock    |
|    11 Sep 03 15:53:21    |
      XPost: comp.databases.oracle.misc, comp.databases.oracle.server       From: tcallahan@crunchtime.com              We have an inhouse replication process which is causing us headaches       when we try to run more than one copy of it against the same target       database (we support unlimited remote databases so we may have to       process in 20 replication files on a Monday morning).              The issue I'm seeing is that computer 1 starts processing in the       inserts/updates and continues through the process.              Computer 2 starts processing inserts/updates fine as well but at some       point gets blocked by computer 1.              The lock is a TX lock and I'm trying to understand what could cause       it.              Any help would be appreciated.              Tim Callaghan              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca