Re: account locking up
- From: Oleksandr Denysenko <odenysenko@xxxxxxxxx>
- To: andrejs.kaulins@xxxxxxxxx
- Date: Thu, 11 Apr 2013 15:32:03 +0300
Hi.
It's better to use
DBA_AUDIT_SESSION<http://docs.oracle.com/cd/E11882_01/server.112/e25513/statviews_3079.htm#REFRN23021>to
check for history of logon issues.
Actually, there not only 1017 code when you have some troubles,
but, for example, 28000, 28001
Oleksandr Denysenko
2013/4/11 Andrejs Kaulins <andrejs.kaulins@xxxxxxxxx>
> Hi,
>
> All successful and unsuccessful connections is written in database audit
> trail, try to look at aud$ where you will find username , user host ,
> action_name (logon) , returncode (if you have problems, you will get code
> 1017)
>
> Best regards,
> Andrejs
> Senior Oracle DBA
>
> On 2013. gada 11. apr., at 07:53, C P <carlospena999@xxxxxxxxx> wrote:
>
> > All,
> > We recently migrated an application into a 11g database in a server.
> After
> > the upgrade one of the accounts necessary for connecting to the DB keeps
> > locking up, because some application is trying to log in with wrong
> > password. Our application team is unable to come up with a full list of
> > servers or locations where the connections could come from. I was trying
> to
> > find the information from the listener log. It has few entries close
> > (within a minute or two) the time of lock issues, but the status code is
> > '0' which I think indicates a success. I am assuming it is not a failed
> > connection. Is there a way in which to figure out where the connections
> are
> > coming from. TIA
> >
> > CP.
> >
> >
> > --
> > //www.freelists.org/webpage/oracle-l
> >
> >
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
Best Regards,
Oleksandr Denysenko
--
//www.freelists.org/webpage/oracle-l
Other related posts:
