lupinbandit
MIS
First, an evironment check. We have DB2 v7 databases running on AIX v4.3.3 servers and use Crystal v8.5 for reporting purposes.
Now, the problem. When many/most/all (no one is quite sure how pervasive) our reports are run, a failed login (or two) occurs on the AIX server before the successful login is made. The person running the report does not see the failed login, but it does get recorded on the AIX server.
The even bigger problem is that the failed login may not be the person running the report. The failed login seems to occur, at least quite often, on the userid of the person who created the report. Therefore, person A may run a report 10 or 12 times and have no problems, but person B (who created the report) might be accumulating 10-12 (or sometimes 20-24) failed login attempts. That locks person B's account. One creator's userid now has over 9,000 unsuccessful login attempts.
Any idea why these reports automatically bang the creator's userid?
Now, the problem. When many/most/all (no one is quite sure how pervasive) our reports are run, a failed login (or two) occurs on the AIX server before the successful login is made. The person running the report does not see the failed login, but it does get recorded on the AIX server.
The even bigger problem is that the failed login may not be the person running the report. The failed login seems to occur, at least quite often, on the userid of the person who created the report. Therefore, person A may run a report 10 or 12 times and have no problems, but person B (who created the report) might be accumulating 10-12 (or sometimes 20-24) failed login attempts. That locks person B's account. One creator's userid now has over 9,000 unsuccessful login attempts.
Any idea why these reports automatically bang the creator's userid?