SAPSID User Locked

[Former Member]

Hi ,

From oracle audit feature we came to know that sapsid user account was locked because someone entered the wrong password,from the audit file which is generated by Oracle we came to know the Server name,O/S user name who has entered the wrong password.

Now my question is Server name which is identify by thru oracle audit is an application server where no oracle binary is resided(only tnsping is there) means we can't run sqlplus thru application server then how can be sapsid user locked thru application server.

Regards

Tarun Mittal

[Former Member · Accepted solution]

You need to know how an application server connects to the database in the first place. In short this is how:

- when you start sap, it tries to connect to the db with the OPS$ user. sidadm is able to logon without password.

- the OPS$ user has the password of the SAPSID account stored in the table SAPUSER

- now SAP can logon with SAPSID/pw

So in your case, i could be that you changed the password of SAPSID, but did not update the entry in the SAPUSER table. This way the application server gets the old password and the SAPSID user is locked.

Remember, you should always use BR*Tools to change the SAPSID password, because it will take care of the SAPUSER table as well.

Regards, Michael

[Former Member · Accepted solution]

We has the same ideas about the isssue

Can we konw is there any other way it can be locked thru application server?

[Former Member · Accepted solution]

You can verify if the connection works now, with the command R3trans -d. In the generated trans.log file, you can see every step nicely.

Another possibilty the user is locked from the application server could be a faulty environnement of the sidadm user. Something like wrong NLS_LANG, but i have never seen this happen in real life. Another possibilty is that somebody was trying to set up a direct database connection (transaction DBCO), but this is not very likely as well.

Best regards, Michael

[Former Member · Accepted solution]

Hi Michael,

We have checked the last date of reset password as given below.

NAME CTIME PTIME

-

---

-

---

-

---

SAPSID 26-MAY-04 26-MAY-04

it means nobody has changed the password even there is no change in nls_lang parameter as well as nobody has authorization to run the DBCO transaction code.

Then, How can be the account lock thru application server.

Kindly suggest.

Thanks,

Tarun Mittal