Is your workaround "database resident connection pools". This can reduce
significantly the contention on logon
Why does a batch need to have a large number of login/logout - or is it
simply that the batch runs while the high rate of login/logout are going on?
Does the technology you're using requirement a lot of login/logout, or is
it a feature of the way the application is written.
Ilmar Kerm's comment is most important - what, exactly, do you mean by
module? If it's not already done, and if it's an "application module"
would it be possible to set up several services, one per module and make
sure that each module connects to its designated service.
Regards
Jonathan Lewis
On Mon, 18 Oct 2021 at 10:45, Krishnaprasad Yadav <chrishna0007@xxxxxxxxx>
wrote:
Hi All ,
Thanks for your suggestion ,
In our environment , listener log is disabled , since it has huge
connection coming in , on average login per sec for per instance is ~150.
Now situation is CPU is used almost 100% during batch run ,and these batch
run has huge login and log out .
we are trying to achieve two things :
1. get connection management historical data, since we feel it is due to
huge login , system is reaching to 100 % so trend of it would help us to
relate
2. Implementing a workaround which helped , but we need to figure out
which modules need to add in it ,hence needed login per sec module wise
Regards,
Krishna
On Mon, 18 Oct 2021 at 14:20, Ilmar Kerm <ilmar.kerm@xxxxxxxxx> wrote:
If by "module" you mean "service", then:
select * from gv$service_stats where stat_name='logons cumulative';
I sample it regularly and then calculate logons per time unit from there.
On Mon, Oct 18, 2021 at 8:07 AM Krishnaprasad Yadav <
chrishna0007@xxxxxxxxx> wrote:
Hi Experts ,
Is there any way to find out login per sec of specific modules from the
database .
It will be great if someone share some lights on this
Regards,
Krishna
--
Ilmar Kerm
