it's the Oracle Agent!
not a user.
But why sleep 1 minute when Tom said over 10 min was a problem? Maybe they
fixed it since then (?).
On Wed, Jan 27, 2016 at 9:27 AM, Patrice sur GMail <patrice.boivin@xxxxxxxxx
wrote:
This is a bit strange
We have a slow WAN to begin with, then I noticed waits related to this
plsql package in session waits in the database, turns out it is coming from
a thin jdbc client.
SID SERIAL# INST_ID OSUSER EVENT
P1 P2 P3 SQL_TEXT PROGRAM
---------- ---------- ---------- ------------ --------------------
---------- ---------- ---------- ----------------------------------------
------------------------
166 1 1 oracle PL/SQL lock timer
0 0 0 BEGIN dbms_lock.sleep(60); END; JDBC
Thin Client
I searched through all the plsql code in the database and didn't find a
sleep(60) anywhere.
Not helpful. I'll track down the source.
Is it possible FM11g tells sessions to sleep when idle or when the network
is slow?
I saw a whole discussion on AskTom where he mentioned that anything above
10 minutes isn't ideal because it can create problems, loop the sleep
statements instead. This is set for an hour.
-- Patrice
My profiles: [image: Facebook]
<http://www.facebook.com/home.php?#!/profile.php?id=100000206805521>[image:
LinkedIn] <http://ca.linkedin.com/pub/patrice-boivin/a/933/5a9>[image:
Twitter] <http://www.twitter.com/PatriceBoivin>
