SAPR3 is keep on locking in Oracle

[Former Member]

Hi SAP gurus,

we have just change our hostname. I already changed all necessary parameters. Now Im facing new problem.

SAPR3 user is keep on locking in ORACLE every time I started MMC "ORA-28000: the account is locked".

Please let me know what to do?

Thanks in advance

[Former Member · Accepted solution]

Hi

Check SAP Note 951167 - ORA-28000: the account is locked

Cheers.....,

Raghu

[JPReyes · Accepted solution]

Additional to that this can be caused by a problem with the ops users. Read note 400241

[Former Member · Accepted solution]

Hi Juan Reyes,

Thanks for the note, already checking it and it may resolved my issue because im getting this error from BRCONNECT

BR0830I Password changed successfully in table OPS$<old_hostname>\QASADM.SAPUSER fo
r user SAPSR3

which is the old hostname does not exist any more.

Will provide feedback after i tried the note.

If anyone have still comments please do so.

Thank you.

[lakshminarayanan_m · Accepted solution]

Hi,

Delete OPS$ user from oracle level,

>Sql : drop user "OPS$hostname\SIDADM" cascade;

>Sql : drop user "OPS$hostname\SAPSERVICESID" cascade;

Then run oradbusr.sql from location where file available.

After that , change password for SAPSR3 user. your problem will get resolve.

Reply...

Regards

MLN

[Former Member · Accepted solution]

Hi MLN,

I hope your resolution will solved my problem, Im out of the office right now and will try to test your suggestion tomorrow.

Thank you so much for the support.

BR,

Joel

[Former Member · Accepted solution]

Hi MLN,

Thanks a lot, your solution works perfectly.

BR,

Joel

[lakshminarayanan_m · Accepted solution]

Hi,

What happen to your problem.. its get resolve?

Please update

Regards

Lakshminarayanan

[Former Member · Accepted solution]

Hi Lakshminarayanan,

Yes it is already resolved thanks to you. Though I have a little problem, Im still getting error from MMC

SAP-Basis System: Operating system call           recv failed (error no. 10054)

But we can already login to SAP server.

BR,

Joel

[lakshminarayanan_m · Accepted solution]

Hi,

Great !.....

Its an normal error only , u can ignore it...

Check any spcial errors in ST22, SM22..

Regards

MLN

[Former Member · Accepted solution]

Hey Thanks for Soln,

worked for me.

My Scenario: Change of hostname and IP of existing system.

Thanks & Regards,

Ishan

[Former Member]

Hi Joel,

Always SAP recommends to delete old users and recreate new OPS$ users after every data restore (Qas refresh), this could avoid inconsistancy (in connecitons with OPS$ mechanism).

Please follow below recommended notes:

If you are on Windows NT---SAP Note 50088

If you are on *nix -

---

SAP Note 400241

Regards

Nick Loy