Re: Just wondering about ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit ...
From: Mikhail Velikikh <mvelikikh_at_gmail.com>
Date: Thu, 12 Nov 2020 17:46:32 +0000
Message-ID: <CALe4Hpn3QVxtgcD-4fhkcbNjcdkdb2QS-Wor39f=WBqYHtJZgw_at_mail.gmail.com>
Date: Thu, 12 Nov 2020 17:46:32 +0000
Message-ID: <CALe4Hpn3QVxtgcD-4fhkcbNjcdkdb2QS-Wor39f=WBqYHtJZgw_at_mail.gmail.com>
On Thu, 12 Nov 2020 at 15:24, Luis Claudio Dias dos Santos < lsantos_at_pobox.com> wrote:
> 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?
>
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Thu Nov 12 2020 - 18:46:32 CET