Re: Log in Storm Caused Database Crash

I would definitely second what Upendra has said, and start looking at the entry points for your internet facing services:

Particularly the HTTP server logs will show you what exactly has been happening - if the connections were from the outside and not due to a middle-tier fault (e.g. a connection pool that's mis-configured and kept making new connections).

Other things I'd look at is if you had auditing enabled in the database - check if there are entries in DBA_AUDIT_TRAIL. This would allow you to determine from where exactly the database has been hit. If it's off, an alternative would be to look at the listener logs to see where the connections originated from. That data could point you to the application / web server you need to focus on.

Stefan

On Mon, Oct 2, 2017 at 11:45 AM, Ravi Teja Bellamkonda < raviteja.bellamkonda7_at_gmail.com> wrote:

> 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_at_hotmail.com>
> 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/B19
>> 306_01/server.102/b14237/statviews_3125.htm#REFRN23400
>>
>>
>> DBA_HIST_ACTIVE_SESS_HISTORY - Oracle Help Center
>> <https://docs.oracle.com/cd/B19306_01/server.102/b14237/statviews_3125.htm#REFRN23400>
>> 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_at_freelists.org <oracle-l-bounce_at_freelists.org> on
>> behalf of Ravi Teja Bellamkonda <raviteja.bellamkonda7_at_gmail.com>
>> *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.
>>
>> [image: Inline image 1]
>>
>>
>> Logons cumulative also increased during this interval.
>>
>> [image: Inline image 2]
>>
>> 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
>

-- 
//
zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
Visit us at zztat.net | Support our Indiegogo campaign at igg.me/at/zztat |
_at_zztat_oracle










--
http://www.freelists.org/webpage/oracle-l





image/png attachment: image.png



image/png attachment: image.png