RE: Just wondering about ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit ...

  • From: "Clay Jackson (cjackson)" <Clay.Jackson@xxxxxxxxx>
  • To: "mark.powell2@xxxxxxx" <mark.powell2@xxxxxxx>, ORACLE-L <oracle-l@xxxxxxxxxxxxx>
  • Date: Thu, 12 Nov 2020 15:38:56 +0000

What Mark said - I think the only way this would work is to put a "wrapper" 
around the sqlplus executable (or whatever executable you're using)  that 
attempted the connection and then "handled" the failure - OR, you could set up 
some sort of "session" monitor that would tell you when you were getting close 
to the limit.


Clay Jackson
Database Solutions Sales Engineer
[cid:image001.jpg@01D6B8C6.DF7DD750]<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.quest.com%2Fsolutions%2Fdatabase-performance-monitoring%2F&data=02%7C01%7CClay.Jackson%40quest.com%7C6c57a6f83b6c490b3b4708d83edb5e24%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637328459211276950&sdata=QId%2B4IzV9yh9ogPm8bagnDkPxeBziolrNZGcYO8%2FrYk%3D&reserved=0>
clay.jackson@xxxxxxxxx<mailto:clay.jackson@xxxxxxxxx>
office  949-754-1203  mobile 425-802-9603




From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf 
Of Powell, Mark
Sent: Thursday, November 12, 2020 7:31 AM
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: Re: Just wondering about ORA-02391: exceeded simultaneous 
SESSIONS_PER_USER limit ...

CAUTION: This email originated from outside of the organization. Do not follow 
guidance, click links, or open attachments unless you recognize the sender and 
know the content is safe.


Luis, I do not believe you could do this in an after logon trigger because I do 
not believe you get a successful login to begin with hence the trigger does not 
fire.  You would need to write a logon routine that issues the login and on 
failure checks the return code and if ORA-02391 sleeps then tries again.


Mark Powell
Database Administration
(313) 592-5148


________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx> 
<oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>> on behalf 
of Luis Claudio Dias dos Santos <lsantos@xxxxxxxxx<mailto:lsantos@xxxxxxxxx>>
Sent: Thursday, November 12, 2020 10:21 AM
To: ORACLE-L <oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>>
Subject: Just wondering about ORA-02391: exceeded simultaneous 
SESSIONS_PER_USER limit ...

Is there way to define a logon timeout?

In detail: if some app user is about to get ORA-02391 after a logon attempt the 
logon process would wait for n seconds before receive an ORA-02391.

If within this n seconds some other sessions logoff the attempt would be 
successful...

Is this possible in declarative way? Or with a LOGON trigger?




JPEG image

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 11-2020