Database Administration (MOSC)

MOSC Banner

high "connection management call elapsed time"

edited Sep 27, 2014 5:00AM in Database Administration (MOSC) 3 commentsAnswered

Statistic Name Time (s) % of DB Time

connection management call elapsed time 4,666.75 19.05

This in awr report (10 mins), I find OMS launches 3812 connection times.

Elapsed Time (s) Executions Elapsed Time per Exec (s) %Total %CPU %IO SQL Id SQL      Module      SQL Text

536.23           3,812                0.14                                    2.19          3.21 0.01 3r3nmx18apvn3 OMS      BEGIN restrict_logon_pkg.screen_logon; end;

518.91           3,805                0.14                                    2.12           0.24 0.01 8vz9nm0akvgz5 OMS      MERGE INTO Restrict_LOGON_Log

In our system, we have a trigger, each login will run restrict_logon_pkg.screen_logon, and record the login information or failed login into table restrict_login_log. Why OMS launch 3812 connections in 10 minutes? In awr report, sometimes it about more than 4000. Is anyway to reduce this?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center