DDIC and SAP* locked in client 000 - DB deletion still valid?

[Private_Member_19084]

Hi experts,

in internet I found a lot about, how to solve the problem if sap* and ddic is locked in client 000.

Is it still valid, to delete in that case on DB-level the sap* user?

Kind regards

[former_member185954 · Accepted solution]

Hello Christian,

Yes it is valid and its a feature to allow you to login in case you get locked out and should be only used as an emergency measure, the question do you have the authorization in your organisation to do this? Also, you may have to disable some parameters that forbid automatic login using sap*

Regards,

Siddhesh

[Private_Member_19084 · Accepted solution]

Hello Siddesh,

thank you very much.

I will have the authority for this

Kind regards

[hemanth2 · Accepted solution]

Hi Christian,

To view the entries of the "sap*" user type in following command:

select * from <db_schema>.usr02 where mandt = '000' and bname = 'SAP*'; (maybe you have to change "mandt" to your client)

to delete the "sap*" user type in the following commands:

delete from <db_schema>.usr02 where mandt = '000' and bname = 'SAP*'; (maybe you have to change "mandt" to your client)

Because USR02 is a buffered table please logon to any client and execute /$tab in the transaction code field to synchronize the buffers. If you can't logon to any client, the system must be restarted.

Regards, hemanth

[former_member185954 · Accepted solution]

Hello Hemanth,

Generally, if you execute a 'commit' after your query in SQLPLUS, Query Analyser or whatever tool you are using depending your database type, there is no need for /$tab, a database commit forces SAP Application to update its internal buffers.

Regards,

Siddhesh

[hemanth2 · Accepted solution]

yes, this is something like a best practise that is advised always