Last updated on July 17th, 2015 at 06:05 pm
unsuccessful logins from the applsys.FND_UNSUCCESSFUL_LOGINS table.
example, the unsuccessful logins for the last week.
SELECT B.USER_NAME, U.ATTEMPT_TIME FROM applsys.FND_UNSUCCESSFUL_LOGINS U, applsys.FND_USER B WHERE U.USER_ID = B.USER_ID --AND B.USER_NAME LIKE NVL(:USER_NAME, '%') AND TRUNC(U.ATTEMPT_TIME) > TRUNC(SYSDATE-7) ORDER BY U.ATTEMPT_TIME;
We can check the auditing level in the system by checking the Profile
Here are the various settings possible
i) None means do not audit any users who sign on to Oracle Applications.
ii) Auditing at the User level tracks: who signs on to your system, the times users log on and off
iii) Auditing at the Responsibility level performs the User level audit functions + the responsibilities users choose + how much time users spend using each responsibility
iv) Auditing at the Form levelperforms the Responsibility level audit functions + the forms users choose + how long users spend using each form + System Administrator visible, updatable at all levels.
The Unsuccessful login report can be generated through concurrent request also
Signon Audit Unsuccessful Logins– Use this report to view who unsuccessfully attempted to sign on to Oracle Applications as another user. An unsuccessful login occurs when a user enters a correct username but an incorrect password. You can generate Signon Audit Unsuccessful Logins Reports for any users, regardless of whom you are auditing.