AnsweredAssumed Answered

ORA-28000: the account is locked

Question asked by tfighter on Jun 28, 2012
Latest reply on Oct 5, 2012 by tfighter

I hope everyone is having a spectacular Summer! Seeking some advice...please and thank you...

Environment: 12.1.1 (Oracle)

Issue: since going live in February, on (2) separate occasions, when attempting to re-start bg services in Production instance, we encounter

FATAL 2012-06-15 19:48:24,135 [http-80-1] union.persistence (none:none:none) Failed to initialize Context properties java.sql.SQLException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-28000: the account is locked

Background: If the number of failed login attempts exceeds 10, the account gets locked and the background services won't re-start until the DBA issues alter user userid account unlock -> then the background service starts successfully. "Clarity" is the Login Name (nsa, Database settings). "Clarity owns" the tables. Concurrent database connections are set to UNLIMITED. Number of failed login attempts to lock after 10.

DBA: "I have queried several times at the LCOUNT for the Clarity user. In querying the failed logon attempts, I saw that the count is set at '2'. Then a short time later, I checked again and it was '0'. A few minutes later, it was at '1'. According to the information that I've found, the user has to make 10 continuously failed logon attempts, in order for the Clarity account to lock. The account will lock on the 11th non-successful attempt. However, if there is one successful attempt to connect, the value is reset to '0'."

Troubleshooting: Created a case with CA Support and in terms of resolution, the case is going absolutely nowhere. :sad According to CA Support, everybody thinks it is DB (oracle) settings issue. Support cannot tell us what Clarity process uses the nsa account to attempt to connect to the database. We have no custom scripts running. We have not modified the Clarity database. Only customizations are through Studio and some custom crystal reports.

The positive is we have a workaround. The negative is the unknown cause and possibility we the app could be down without notice. Has anyone run into this locking scenario? Does anyone know what Clarity process is causing the account to get locked?