Application waiting for a user lock.
From: Mladen Gogala <mgogala_at_yahoo.com>
Date: Mon, 16 Feb 2015 22:43:07 -0500
Message-ID: <54E2B8CB.3030705_at_yahoo.com>
The wait events look like this:
/Event Waits Time (s) (ms) Time
Date: Mon, 16 Feb 2015 22:43:07 -0500
Message-ID: <54E2B8CB.3030705_at_yahoo.com>
The wait events look like this:
/Event Waits Time (s) (ms) Time
----------------------------------------- ------------ ----------- ------ ------
*PL/SQL lock timer 60 3,601
60012 52.0
*CPU time 3,233 46.7
db file sequential read 97,875 75 1 1.1 control file sequential read 13,019 5 0 .1 log file parallel write 1,344 4 3 /
Obviously, the application is using DBMS_LOCK. Is there anything that
can be done to make it cheaper? Not only
is the whole thing horribly slow, it also devours vast amounts of CPU.
I cannot go into the source, it's a 3rd party
application and someone discovered the keyword "WRAPPED". I've been
looking for a hidden instance parameter
which would change the DBMS_LOCK behavior and make it cheaper. Any ideas?
-- Mladen Gogala Oracle DBA http://mgogala.freehostia.com -- http://www.freelists.org/webpage/oracle-lReceived on Tue Feb 17 2015 - 04:43:07 CET