ORA-28000: The account is locked.

Products

• CA 7 Workload Automation
• iDash Workload Automation for CA 7

Issue/Introduction

The Oracle DB was moved last weekend and we are trying to point the new but when we update the URL we received the error message.

  The error message is saying the account is locked.  I am not able to update the password.  

21-03-04 12.10.45 [ WARN] idashdb-import-PUA-thread-2:com.ca.idash.core.db.DbConnectionManager: Primary connection failed: java.sql.SQLException:ORA-28000: The account is locked.
. Using secondary.
21-03-04 12.10.45 [ERROR] idashdb-import-PUA-thread-3:com.ca.idash.core.db.DbConnectionManager: java.sql.SQLException:ORA-28000: The account is locked.

java.sql.SQLException: java.sql.SQLException:ORA-28000: The account is locked.

 at com.ca.idash.core.db.DbConnectionManager.getConnection(DbConnectionManager.java:228)
 at com.ca.idash.core.db.DbConnectionManager.getPrimaryConnection(DbConnectionManager.java:111)
 at com.ca.idash.core.db.DbConnectionManager.getConnectionUsingPrimary(DbConnectionManager.java:676)
 at com.ca.idash.core.db.DbConnectionManager.internalGetConnection(DbConnectionManager.java:655)
 at com.ca.idash.core.db.DbConnectionManager.getConnection(DbConnectionManager.java:612)
 at com.ca.idash.core.db.DbConnectionManager.getConnection(DbConnectionManager.java:597)
 at com.ca.idash.core.db.etl.AbstractTableImporter.getSourceConnection(AbstractTableImporter.java:390)
 at com.ca.idash.core.db.etl.AbstractTableImporter.executeImport(AbstractTableImporter.java:164)
 at com.ca.idash.core.db.etl.AbstractTableImporter.call(AbstractTableImporter.java:135)
 at com.ca.idash.core.db.etl.AbstractTableImporter.call(AbstractTableImporter.java:39)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
 at java.lang.Thread.run(Thread.java:748)

Environment

iDASH Workload Automation

Cause

The account is locked from too many failed login attempts. 

Resolution

Consult your DBA to unlock the offending account in the database.