Encina server and updated to Oracle 7.0.15
From: Alan Beal <beal_at_austin.ibm.com>
Date: 29 Sep 1994 22:51:22 GMT
Message-ID: <36fgda$qug_at_news.manassas.ibm.com>
Date: 29 Sep 1994 22:51:22 GMT
Message-ID: <36fgda$qug_at_news.manassas.ibm.com>
I have an Encina server that does an insert of a record in a Oracle 7.0.15 table. When I run many clients against this server, I sometimes get an oracle error -2049, distributed deadlock. I can run SQL*DBA and watch when this happens because there is a session that is requesting a S lock on a resource that already has a X lock on it. The trouble is that I can't figure out what the resource ids are in the SQL*DBA monitor locks display. Can someone help me with this?
The Encina server is using a MON_EXCLUSIVE scheduling policy and we are running 4 PAs. Is there something we can do to prevent these deadlocks? We are on AIX 3.2.5.
alan beal
-- Alan Beal Loral Federal Systems Owego, NY (607) 751-2026 beal_at_lfs.loral.comReceived on Thu Sep 29 1994 - 23:51:22 CET