This content has been marked as final. Show 4 replies
Unfortunately, this problem keeps recurring. I just want to focus upon SYSMAN for now.
In SQLPlus, I try to sign on using SYSMAN. It says the ACCOUNT IS LOCKED. So then I successfully sign on using 'SYSMAN as DBA'. From there I unlock the SYSMAN account and then I can successfully sign on with SYSMAN. I then close SQLPlus and wait for a few minutes. But when I try again to sign on using SYSMAN I get the same error of ACCOUNT IS LOCKED. :(
I know that one possibility for this kind of error is that some other program has made multiple unsuccessful attempts to sign on using SYSMAN. However, there are no other programs that are using the Database in the interim. I have SQLDeveloper on the machine and I mostly use that program when I want to run code and query the database- but it is not opened for the process I describe above.
What could be causing the SYSMAN account to keep locking?
You can audit create session by SYSMAN and then watch in audit_trail who is accessing: AUDIT CREATE SESSION BY SYSMAN BY ACCESS WHENEVER NOT SUCCESSFUL;
If you want to connect to database using privileged account you can use: CONNECT / AS SYSDBA (doesn't ask you for passwd).
Alternatively, you can create new profile for SYSMAN account and put FAILED_LOGIN_ATTEMPTS parameter to UNLIMITED. (not recommended for security reasons).
Zoran, thanks for the reply. I haven't done any auditing so I'm trying to read up on it. From this article [url http://www.oracle-base.com/articles/10g/Auditing_10gR2.php] http://www.oracle-base.com/articles/10g/Auditing_10gR2.php it seems that there are 3 views which hold the auditing data:
* DBA_AUDIT_TRAIL - Standard auditing only (from AUD$).
* DBA_FGA_AUDIT_TRAIL - Fine-grained auditing only (from FGA_LOG$).
* DBA_COMMON_AUDIT_TRAIL - Both standard and fine-grained auditing.
I'll examine the many fields returned and see what I can figure out and maybe come back with more questions.