DX Unified Infrastructure Management

Hello,

Good Day!!

After resting password on oracle connection, we see the the below error when we try to establish the connection. Even after the DBA team unlock the user account, again after some time the account will get locked. Kindly let us know if someone has faced the issue and the steps followed to fix it.

Error in log: Profile: Aug  1 06:23:55:455 [0001] oracle: Profile: test query profile, Oracle error! Status: -1, - ORA-28000: the account is locked 

Status of the account when its locked : Locked(Timed)

Note: We are not modifying password from our end in GUI of probe interface.

Thanks in Advance!!

Hello,

do you see that on the data_engine probe or any oracle monitoring probe?

Do you have any other connection like UIM SOI connector accessing the database?

When searching in the our database I found a hit related to data_engine, where such a problem disappeared after entering correct user details and a cold start of data_engine (deactivate/activate).

Also credentials in the UIM SOI connector needs to be adjusted, if you have that.

If that does not help, I suggest to reach out to support within a support case.

Regards

Hello Albert,

Thanks for your quick turnaround.

We see that on oracle monitoring probe which is configured on client server to monitor oracle DB. DBA team has confirmed that none of  other apps running on the server are using credentials what we have defined for nimbus user account to establish the connection.

As a fix we removed the database folder under nimbus directory, redeployed the probe and defined username/password. For a moment, we were able to establish the connection with same old username and password but after sometime again we got the error as locked.

So, the probe login works for a moment and then user is locked.

This looks like something else is trying to access oracle db with wrong credentials causing the lock.
Like a scheduled script trying to connect with an incorrect password or anything else.
I suggest to turn on some oracle auditing for connection attempts, then look at the results. DBA_AUDIT_TRAIL will show where the failed attempts are coming from,

Unfortunately, I am not a DBA so can't really help further.
There are a couple of ORA-28000 related threads when doing a google search.

It might also be worth checking 

   - alarm_enrichment. If alarm enrichment is setup check the db user in the enrichment-source\cmdb section

        of the nas.cfg

   - Also check to see if Unified Reporter is installed on the ump robot. Wasp ~~> webapps ~~> jasperserver-pro ~~> jdbc

Greg

If possible can you rest the old password and check . The old password is attempting somewhere .It is domain account ? If domain account means you can check in domain controller for source .