Re: Identify user with incorrect password locking the database
From: Matthias Hoys <matthias.hoys_at_gmail.com>
Date: Mon, 5 Nov 2012 00:37:30 -0800 (PST)
Message-ID: <929393ab-60b1-45cd-a6c9-2c1d03c0acd1_at_googlegroups.com>
On Sunday, November 4, 2012 11:34:18 AM UTC+1, Gerard H. Pille wrote:
> rexnfx611_at_gmail.com wrote:
>
> > I've recently changed the password on my database. Now the database keeps getting locked out from some program that's using the old credentials. There were a lot of client programs that used the same credentials. Is there any way to track down the offending program and which machine this is originating from? We've already changed our lockout policy as much as we can given company policy.
>
> > Thanks,
>
> >
>
>
>
> I'd check the listener logs for starters.
Date: Mon, 5 Nov 2012 00:37:30 -0800 (PST)
Message-ID: <929393ab-60b1-45cd-a6c9-2c1d03c0acd1_at_googlegroups.com>
On Sunday, November 4, 2012 11:34:18 AM UTC+1, Gerard H. Pille wrote:
> rexnfx611_at_gmail.com wrote:
>
> > I've recently changed the password on my database. Now the database keeps getting locked out from some program that's using the old credentials. There were a lot of client programs that used the same credentials. Is there any way to track down the offending program and which machine this is originating from? We've already changed our lockout policy as much as we can given company policy.
>
> > Thanks,
>
> >
>
>
>
> I'd check the listener logs for starters.
You could also check out the system view DBA_AUDIT_TRAIL... if you enabled db auditing...
Matthias Received on Mon Nov 05 2012 - 09:37:30 CET