You can also look at you listener log to see number of connection attempts to
system.
If it was a true overwhelming connection storm then you will also probably have
information in the alert.log where errors are being reported spawning against
the database.
Matthew Parker
Chief Technologist
Dimensional DBA
425-891-7934 (cell)
D&B 047931344
CAGE 7J5S7
<mailto:Dimensional.dba@xxxxxxxxxxx> Dimensional.dba@xxxxxxxxxxx
<http://www.linkedin.com/pub/matthew-parker/6/51b/944/> View Matthew Parker's
profile on LinkedIn
<http://www.dimensionaldba.com/> www.dimensionaldba.com
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Ravi Teja Bellamkonda
Sent: Sunday, October 1, 2017 9:45 PM
To: Upendra nerilla <nupendra@xxxxxxxxxxx>
Cc: oracle-l <oracle-l@xxxxxxxxxxxxx>
Subject: Re: Log in Storm Caused Database Crash
Hi Upendra,
Thank you for your response. This is an internet facing application and we were
expecting a burst load to check for the capacity of the system. Is there a way
to measure what no of sessions in the database is breaking point. I was
doubting if any Sub-Optimal Connection Pooling might have caused this.
Highly appreciated your help here.
On Sun, Oct 1, 2017 at 7:39 PM, Upendra nerilla <nupendra@xxxxxxxxxxx
<mailto:nupendra@xxxxxxxxxxx> > wrote:
Is this an internet facing application or internal? If it is external facing
application, investigate if there was DoS type attack or a spike in the user
sessions due to any issues with application servers?
If you need to isolate where the connections originated from, you could look
into DBA_Hist views.
You may want to start with this one..
https://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_3125.htm#REFRN23400
<https://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_3125.htm#REFRN23400>
DBA_HIST_ACTIVE_SESS_HISTORY - Oracle Help Center
docs.oracle.com <http://docs.oracle.com>
DBA_HIST_ACTIVE_SESS_HISTORY. DBA_HIST_ACTIVE_SESS_HISTORY displays the history
of the contents of the in-memory active session history of recent system
activity.
Also look into any application server logs and see if there were any issues
with the application server itself..
-Upendra
_____
From: oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx <mailto:oracle-l-bounce@xxxxxxxxxxxxx> > on
behalf of Ravi Teja Bellamkonda <raviteja.bellamkonda7@xxxxxxxxx
<mailto:raviteja.bellamkonda7@xxxxxxxxx> >
Sent: Sunday, October 1, 2017 9:25 PM
To: oracle-l
Subject: RE: Log in Storm Caused Database Crash
Hi List,
We ran into an issue recently and wanted some help in figuring out this issue.
Database was not responding and one thing from AWR observed before fail over
was the login storm.
Logons cumulative also increased during this interval.
Logons cumulative were 1237 in total in the before AWR report. Any suggestions
are highly appreciated.
--
Thanks & Regards,
Ravi Teja
--
Thanks & Regards,
Ravi Teja Bellamkonda