Re: Identify user with incorrect password locking the database
From: Gerard H. Pille <ghp_at_skynet.be>
Date: Sun, 04 Nov 2012 11:34:18 +0100
Message-ID: <509644aa$0$3112$ba620e4c_at_news.skynet.be>
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,
>
Date: Sun, 04 Nov 2012 11:34:18 +0100
Message-ID: <509644aa$0$3112$ba620e4c_at_news.skynet.be>
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. Received on Sun Nov 04 2012 - 11:34:18 CET