Just wondering about ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit ...
From: Luis Claudio Dias dos Santos <lsantos_at_pobox.com>
Date: Thu, 12 Nov 2020 12:21:32 -0300
Message-ID: <CAPWdmV9c1E=OYqB2G6M4qd6vYS=VKtBViNc2-_VsAjonOz7szw_at_mail.gmail.com>
Is there way to define a logon timeout?
Date: Thu, 12 Nov 2020 12:21:32 -0300
Message-ID: <CAPWdmV9c1E=OYqB2G6M4qd6vYS=VKtBViNc2-_VsAjonOz7szw_at_mail.gmail.com>
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 - 16:21:32 CET