SAP* is locked

Hi All,
We have restored our Sandbox system with Production data. Restoration was successful and the system came up fine. But again while loggin into the 000 client with SAP* the password got locked.
We are trying to unlock the SAP* with the following command and getting the following error as No match.
sc1tipl:db2sc1 29> db2 update sapxxx.usr02 set uflag=0 where bname=SAP* and mandt=000
No match.
Kindly suggest???

Hi Ambarish,
This Procedure suggested above is correct except the parameter name is login/no_automatic_user_sapstar
make the value 0 and take a restart and it should work.
You can also log in with DDIC and unlock SAP*. Its password would be the one you gave at the time of installation.
If All these don't help then the only option is to delete the user from OS level. Then take a restart and the user sap* will be available with the default password 06071992
BR
Amit

Similar Messages

How can I konw , Which computer name or IP Address make SAP User lock

Dear all,
I have one issues about SAP user lock,
Now I don't know which computer name or IP Address make user lock.
How can I check it or Can you tell me about the table that keep information about the ip address or computer name?
I can see the computer name when I use t-code al08 or sm04.
But I don't know the table that keep data from this t-code.
Pls suggest me for this issue.
Regards,
Pannee

In SM21
If you double click on the message "User XXXXX locked due to incorrect logon"
You'll see under details the name of the terminal
Terminal............ XXXXXXXXXXX
for IP address just ping the terminal.
Regards
Juan

NW7 Trial - Renew License when SAP* is locked

Hello,
I have the following Problem with my NW7 Trial Installation:
The license has expired and I want to renew it. However the user SAP* is locked because of to many failed attempts and a log in with user DDIC is not possible because of the expired license.
How can I reset the user SAP* so that I can login and renew the license?
Kind regards,
Thomas

Hello Thomas
In the same conditions , I changed the notebook date , adjusting it inside the validity range of the expired license ; in this conditions start the application server and SAP GUI and try to log again with the normal user (maybe BCUSER) .
Install then the new license , logoff , stop server , and change back the date to the current one .
I hope it works for you .

HI SAP experts, I want learn SAP BANK LOCK BOX CONFIGARATION

Hi
SAP experts
I would like to Learn SAP bank Module , Specially for Bank lock Box Configaration . So Kindly give the Information which website
it has been provide the Material and that would be Free of cost
thank YOu
Ranamka

Hi
Please check the below link it might be useful for you
http://srilogix.com/casesWhitepapers/Lockbox%20Process.pdf
Thanks & Regards
Phaneendra

SAP Records Locking for preceeding documents in MM

*Hi Experts,*
Our client have a current requirement. They want that all the preceding documents to be locked once the subsequent documents are converted and posted. Eg- when PR converted to PO, PR to be locked or disable, PO converted to MIGO, PO to be locked, After MIRO, MIGO locked or no reversal or cancellation of MIGO document.
I tried to disable the PR by screen layout assign to release status. Then set the GR based I V to avoid reversal og MIGO, but this to be in a flow. Can you please guide me in some enhancement needed in this or any standard BADI exist or help me in getting the logic for this functionality.
Thanks.

Hi Syed,
Are you saying "PR can not be chaged once PO is created" - is this statement true for your system only because you have done some developement via ABAP help, please confirm.
Because Standard SAP system does not stop you in changing PReq even if PO is created for full qty of Preq.
Hi Pradeep,
You can use "System message attributes settings "(avaialble in SPRO) to trigger a pop up when sombody tries to change a Preq for which PO (full qty)has been created. I believe below meesage number will fulfil your requirement for Preq to PO scenario.
Go to SPRO>MM>Environment Data>Define Attribute of System Messages>System Messages-->Message number - 0076 (Materials of requisition & item & alr. ordered in full).
Thanks,
Yogesh

SAP User Locks

Dear Guys
We have a problem, few users are getting locked by SAP while running the transaction automatically. User are getting messages that you are locked by administrator. But administrator is not lcking user ids. User is also not attmepting to relogin and to reched the login limit.
I dont know why user are getting locked autmoaticlly by SAP. Does any body have solution.

Hi,
Just run a BAPI to unlock the user BAPI_USER_UNLOCK , give the user name in this bapi and run this, the user will be unlocked
Regards
Sudheer

What to do with Enterprise Service when SAP is locked?

Sometimes SAP is running a month-end processing, or needs to lock out users, etc. What kind of best practices are there for handling situations when Enterprise Services need to lock out a user?

"error" 1 is not an error. Read it again.
The second and third errors indicate that the files are corrupted.
You may have a bad disk or file server.
They have nothing to do with the platform -- PSD files are the same between platforms.

SAP* login locked !!!??? how can i upgrade my license?

Hello gurus,
My SAP* login of one of the system got locked, while updating the license. Now the thing is, my license is expired, can only log in through SAP* and that log in also locked how can i upgrade my license??
Thanks and Regards,
Rahul

Hi ,
If all the users are locked, they can be unlocked by
a)Try this command at ur sql plus query level
Go to cmd prompt.
Sqlplus /nolog
conn /as sysdba
this will take you to the sqlprompt.
Just execute the earlier commands there.
sqlplus>UPDATE SAP<schema>.usr02 set uflag=0 where mandt=<CLNT NO> and uflag=64; this statement actually unlocks the users of that particular client. So, try for every client in that sap system.
b) You can delete sap* user
Go to cmd prompt.
Sqlplus /nolog
conn /as sysdba
sqlplus>DELETE SAP<SID>.usr02 where mandt='CLIENT.NO' and bname=SAP*;
Note:-
After doing this restart the system. So, that a new user with the name "sap" gets generated with password "pass". Provided the parameter is set login/no_automatic_user_sapstar= 0 (Automatic user SAP is permitted).
regards,
kanthi

SAP* locked!Unlocking from DB level says unknown table USR02

Hi,
The user SAP* is locked.
I tried to unlock it at DB(MAXDB) by query:
sql_execute update <db_schema>.USR02 set UFLAG=0 where BNAME='SAP*' and MANDT=u2019000u2019
It says:
ERR
-24988,ERR_SQL: SQL error
-4004,Unknown table name:USR02
Anything can be done here to unlock the SAP* user?
Thanks in advance!

Below are 2 scripts that will a) show the status of a user and b) unlock that user.
Note, this was used in MSSQL.
--This script is used to determine the status of users in a system,
--the codes are as follows:
--0 --> not locked
--32 --> globally locked by administrator
--64 --> locally locked by administrator
--128 --> locked due to incorrect loggins
Use '<SID>'
go
setuser '<sid>'
go
select * from USR02
To unlock a user execute the script below.
Update USR02 set UFLAG=0 where BNAME = '<USER>' and MANDT = '<CLIENT>'

Different between database lock and sap lock

Hi All,
What is different between database lock and sap lock why sap introduced locking mechanism.
Thanks
Santosh

From a database perspective, every dialog step forms a physical and logical unit:
the database transaction.. The database lock administration can only coordinate
this type of database transaction. From an SAP point of view, however, this is
not sufficient, because SAP transactions, which are formed from a sequence of
logically related work steps that are consistent in business terms, are generally
made up of several dialog steps. SAP systems need to have their own lock
management. This is implemented using the enqueue work process. This also
ensures that the platform-independence of the lock management is maintained.

BAPI_GOODSMVT_CREATE ERROR: A System Error Has Occurred While Locking

Hi All,
I am having a problem with a Z program that I am writing.
Basically, it uses the BAPI mentioned in the title. The program will read excel file that is being uploaded, and then will segregate the line items by 200 lines.
That means, if I were to upload 1000 line items, the BAPI will be called and executed 5 times (1000/200 = 5).
However, when trying to upload 10000 line items, I received this error after around 3000 line items.
"A system error has occurred while locking".
This happens when IMPORT parameter TEST_RUN is set to 'X'.
I found this after some googling: http://sap.ittoolbox.com/groups/technical-functional/sap-basis/lock-entry-system-error-1674434
I am hoping for your expert thoughts on this.
Thank you.

BAPI TO Upload Inventory Data
* GMCODE Table T158G - 01 - MB01 - Goods Receipts for Purchase Order
* 02 - MB31 - Goods Receipts for Prod Order
* 03 - MB1A - Goods Issue
* 04 - MB1B - Transfer Posting
* 05 - MB1C - Enter Other Goods Receipt
* 06 - MB11
* Domain: KZBEW - Movement Indicator
* Goods movement w/o reference
* B - Goods movement for purchase order
* F - Goods movement for production order
* L - Goods movement for delivery note
* K - Goods movement for kanban requirement (WM - internal only)
* O - Subsequent adjustment of "material-provided" consumption
* W - Subsequent adjustment of proportion/product unit material
report zbapi_goodsmovement.
parameters: p-file like rlgrap-filename default
 'c:\sapdata\TEST.txt'.
parameters: e-file like rlgrap-filename default
 'c:\sapdata\gdsmvterror.txt'.
parameters: xpost like sy-datum default sy-datum.
data: begin of gmhead.
 include structure bapi2017_gm_head_01.
data: end of gmhead.
data: begin of gmcode.
 include structure bapi2017_gm_code.
data: end of gmcode.
data: begin of mthead.
 include structure bapi2017_gm_head_ret.
data: end of mthead.
data: begin of itab occurs 100.
 include structure bapi2017_gm_item_create.
data: end of itab.
data: begin of errmsg occurs 10.
 include structure bapiret2.
data: end of errmsg.
data: wmenge like iseg-menge,
 errflag.
data: begin of pcitab occurs 100,
 ext_doc(10), "External Document Number
 mvt_type(3), "Movement Type
 doc_date(8), "Document Date
 post_date(8), "Posting Date
 plant(4), "Plant
 material(18), "Material Number
 qty(13), "Quantity
 recv_loc(4), "Receiving Location
 issue_loc(4), "Issuing Location
 pur_doc(10), "Purchase Document No
 po_item(3), "Purchase Document Item No
 del_no(10), "Delivery Purchase Order Number
 del_item(3), "Delivery Item
 prod_doc(10), "Production Document No
 scrap_reason(10), "Scrap Reason
 upd_sta(1), "Update Status
 end of pcitab.
call function 'WS_UPLOAD'
exporting
 filename = p-file
 filetype = 'DAT'
* IMPORTING
* FILELENGTH =
tables
 data_tab = pcitab
* EXCEPTIONS
* FILE_OPEN_ERROR = 1
* FILE_READ_ERROR = 2
* NO_BATCH = 3
* GUI_REFUSE_FILETRANSFER = 4
* INVALID_TYPE = 5
* OTHERS = 6
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
exit.
endif.
gmhead-pstng_date = sy-datum.
gmhead-doc_date = sy-datum.
gmhead-pr_uname = sy-uname.
gmcode-gm_code = '01'. "01 - MB01 - Goods Receipts for Purchase Order
loop at pcitab.
itab-move_type = pcitab-mvt_type.
itab-mvt_ind = 'B'.
itab-plant = pcitab-plant.
itab-material = pcitab-material.
itab-entry_qnt = pcitab-qty.
itab-move_stloc = pcitab-recv_loc.
itab-stge_loc = pcitab-issue_loc.
itab-po_number = pcitab-pur_doc.
itab-po_item = pcitab-po_item.
concatenate pcitab-del_no pcitab-del_item into itab-item_text.
itab-move_reas = pcitab-scrap_reason.
append itab.
endloop.
loop at itab.
write:/ itab-material, itab-plant, itab-stge_loc,
 itab-move_type, itab-entry_qnt, itab-entry_uom,
 itab-entry_uom_iso, itab-po_number, itab-po_item,
 pcitab-ext_doc.
endloop.
call function 'BAPI_GOODSMVT_CREATE'
exporting
 goodsmvt_header = gmhead
 goodsmvt_code = gmcode
* TESTRUN = ' '
* IMPORTING
 goodsmvt_headret = mthead
* MATERIALDOCUMENT =
* MATDOCUMENTYEAR =
tables
 goodsmvt_item = itab
* GOODSMVT_SERIALNUMBER =
 return = errmsg
clear errflag.
loop at errmsg.
if errmsg-type eq 'E'.
 write:/'Error in function', errmsg-message.
 errflag = 'X'.
else.
 write:/ errmsg-message.
endif.
endloop.
if errflag is initial.
commit work and wait.
if sy-subrc ne 0.
 write:/ 'Error in updating'.
 exit.
else.
 write:/ mthead-mat_doc, mthead-doc_year.
 perform upd_sta.
endif.
endif.
* FORM UPD_STA *
form upd_sta.
loop at pcitab.
 pcitab-upd_sta = 'X'.
 modify pcitab.
endloop.
call function 'WS_DOWNLOAD'
 exporting
 filename = p-file
 filetype = 'DAT'
* IMPORTING
* FILELENGTH =
 tables
 data_tab = pcitab
* EXCEPTIONS
* FILE_OPEN_ERROR = 1
* FILE_READ_ERROR = 2
* NO_BATCH = 3
* GUI_REFUSE_FILETRANSFER = 4
* INVALID_TYPE = 5
* OTHERS = 6
endform.
Code Formatted by: Alvaro Tejada Galindo on Dec 26, 2008 10:20 AM

SEM-BPS 6.0 error message requested data cannot be locked but at 999 row?

Hi all,
We are using SEM-BPS with WIB and EP 7.0 and I encountered issues for the first time. I normally avoid configuring layouts with large hierarchies but at this one the client insisted. They are in testing right now and selection of relatively small node (approx. 10-20 cost centers) still gave us an error message.
I know layouts has a limit of 9,999 rows and we should have been okay since it is about 200-300 lines per cost center but we are getting the error message below and it mentioned a limit of 999 rows in the selection table.. Any way we can change that?
Thanks,
mary
Requested data cannot be locked (-> see long text)
Notification Number RSPLS092
Diagnosis
In order to edit data from InfoProvider 'ZYEE_C02', the requested data has to be locked exclusively for user 'YEESU01'. The data that is currently being requested is specified by a very large selection table. In order to lock the data exclusively, the system has to store a compressed version of this selection table on the SAP standard lock server. However, the compressed selection table still has more than 999 rows. So that a reasonable number of users are able to change data at the same time, the system limits the number of records allowed in a selection table to 999 records.
Information on Context of Lock Request:
Lock requests can come from BI-Planning or from BW-BPS. The context specifies the following information:
BI-Planning: for a lock request from a query, {Planning Function} for a lock request from a planning function.
BW-BPS: {Planning Area}{Planning Level}{Planning Package}{Planning Function}{Parameter Group}. For lock requests from manual planning the following is true: Planning function = '0-MP' and the parameter group is the technical name of the planning layout.
InfoProvider 'ZYEE_C02' is always a Basis InfoProvider. The current context information is:
'{0-ADHOC}{0-MP}'
System Response
The requested data cannot be locked.
Procedure
You can normally only avoid this by simplifying your selections. For more information, see the documentation on this.
Procedure for System Administration

Hi Mary,
in RSPLSE you use the option that the BI lock table is maintained in the SAP enqueue server. Here there is a limit - as explained in the long text of the message - that the compressed selection table for one enqueue request should not have more than 999 rows. This limit can not be changed.
The selection table seems to be very big, since the compression factor is at least 5. So please check your selection table:
1 check whether you can make the characteristic causing the problem not lock relevant
2 or use the second option that the BI lock table is maintained in a shared memory area of the central instance of the system.
But it is better to keep the selection tables small, e.g. by making some characteristics not lock relevant.
Check sizing note 928044, e.g. in case you want to use 2. The default setting is very small.
Regards,
Gregor

Where we use lock objects in our coding like report

what is the purpose of lock objects s? how we use them in real time? like in devoloping reports?

Hi,,.
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
- Read Lock(Shared Locked)
protects read access to an object. The read lock allows other transactions read access but not write access to
the locked area of the table
- Write Lock(exclusive lock)
protects write access to an object. The write lock allows other transactions neither read nor write access to
the locked area of the table.
- Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
Check these links
Re: Lock Objects
http://help.sap.com/saphelp_47x200/helpdata/en/ce/931bb5c79911d5993e00508b6b8b11/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm
http://www.sapdevelopment.co.uk/dictionary/lock_enqueue.htm
http://help.sap.com/saphelp_nw04/helpdata/en/a2/3547360f2ea61fe10000009b38f839/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
- Read Lock(Shared Locked)
protects read access to an object. The read lock allows other transactions read access but not write access to
the locked area of the table
- Write Lock(exclusive lock)
protects write access to an object. The write lock allows other transactions neither read nor write access to
the locked area of the table.
- Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
Lock objects are use in SAP to avoid the inconsistancy at the time of data is being insert/change into database.
SAP Provide three type of Lock objects.
- Read Lock(Shared Locked)
protects read access to an object. The read lock allows other transactions read access but not write access to
the locked area of the table
- Write Lock(exclusive lock)
protects write access to an object. The write lock allows other transactions neither read nor write access to
the locked area of the table.
- Enhanced write lock (exclusive lock without cumulating)
works like a write lock except that the enhanced write lock also protects from further accesses from the
same transaction.
You can create a lock on a object of SAP thorugh transaction SE11 and enter any meaningful name start with EZ Example EZTEST_LOCK.
Use: you can see in almost all transaction when you are open an object in Change mode SAP could not allow to any other user to open the same object in change mode.
Example: in HR when we are enter a personal number in master data maintainance screen SAP can't allow to any other user to use same personal number for changes.
Technicaly:
When you create a lock object System automatically creat two function module.
1. ENQUEUE_<Lockobject name>. to insert the object in a queue.
2. DEQUEUE_<Lockobject name>. To remove the object is being queued through above FM.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
GO TO SE11
Select the radio button "Lock object"..
Give the name starts with EZ or EY..
Example: EYTEST
Press Create button..
Give the short description..
Example: Lock object for table ZTABLE..
In the tables tab..Give the table name..
Example: ZTABLE
Save and generate..
Your lock object is now created..You can see the LOCK MODULES..
In the menu ..GOTO -> LOCK MODULES..There you can see the ENQUEUE and DEQUEUE function
Lock objects:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21eea5446011d189700000e8322d00/content.htm
Match Code Objects:
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm
http://searchsap.techtarget.com/tip/0,289483,sid21_gci553386,00.html
See this link:
http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm
Lock objects are used to synchronize access to the same data by more than one program.
General information about the lock mechanism.
You can synchronize access by several programs to the same data with a logical lock mechanism. This lock mechanism fulfills two main functions:
A program can tell other programs which data records it is just reading or changing.
A program can prevent itself from reading data that is just being changed by another program.
When accessing data records, the records just being edited by other programs can be identified by the entry in the lock table. Such an entry for the lock must define a number of fully specified key fields, that is either a value is passed for the key field or this field is locked generically.
To set locks, a lock object must be defined in the ABAP Dictionary. When this lock object is activated, two function modules (see Function Modules for Lock Requests) are generated with the names ENQUEUE_<lockobjectname> and DEQUEUE_<lockobjectname>.
If data records are to be locked, you must call function module ENQUEUE_<lockobjectname>. The values of the key fields that specify the records to be locked are passed for all the tables contained in the lock object when the function module is called. There is a generic lock if a value is not passed for all the key fields. The function module writes the appropriate lock entry (see Example for Lock Objects). If another program also requests a lock, it will be accepted or rejected depending on the lock mode (see Lock Collisions). The program can then react to this situation.
Locked data records can be unlocked by calling function module DEQUEUE_<lockobjectname>. The key values and the lock mode used to set the lock must be passed to the function module.
Creating Lock Objects
Procedure
Select object type Lock object in the initial screen of the ABAP Dictionary, enter an object name and choose Create. The name of a lock object should begin with an E (Enqueue).
The maintenance screen for lock objects is displayed.
Enter an explanatory short text in the field Short text.
You can then use the short text to find the lock object at a later time, for example with the R/3 Repository Information System.
Enter the name of the primary table of the lock object.
All other tables in the lock object must be linked with the primary table using foreign keys. There are also some restrictions on the valid foreign key relationships.
Select the lock mode of the primary table in the field below it.
The lock mode is used as the default value for the corresponding parameters of the function modules generated from the lock object.
Choose Add if you want to lock records in more than one table with the lock object.
A list of all the tables linked with the primary table using valid foreign keys is displayed. Select the appropriate table. The lock mode of the primary table is copied as lock mode. You can change this setting as required, for example you can assign the lock mode separately for each table.
Similarly, you can add a table linked with the secondary table just added with foreign keys. To do this, place the cursor on the name of the secondary table and choose Add.
If no lock mode is assigned to a table, no lock is set for the entries in this table when the generated function modules are called. You should not assign a lock mode if a secondary table was only used to define a path between the primary table and another secondary table with foreign keys.
Save your entries.
A dialog box appears in which you have to assign the lock object a development class.
You can (optionally) exclude lock parameters (see lock objects) from the function module generation on the Lock parameter tab page. This makes sense for example if you always want to lock a parameter generically.
To do this, simply deselect the Weight flag for the parameter. The parameter is not taken into consideration in the generated function modules. This parameter is then always locked generically.
The name of a lock parameter is usually the name of the corresponding table field. If two fields with the same name are used as lock parameters in the lock object from different tables, you must choose a new name for one of the fields in field Lock parameter.
You can define whether the function modules generated from the lock object should be RFC-enabled on the Attributes tab page.
If you set the Allow RFC flag, the generated function modules can be called from within another system with Remote Function Call.
If you permit Remote Function Calls for an existing lock object, you must ensure that the generated function modules are called from within an ABAP program with parameters appropriate for the type. You should therefore check all programs that use the associated function modules before activating the lock object with the new option.
Choose .
Result
When you activate the lock object, the two function modules ENQUEUE_<lockobjectname> and DEQUEUE_<lockobjectname> are generated from its definition to set and release locks.
Regards
Vasu

SAP logon failed

Hi Friends,
I have installed SAP 4.7c version in my laptop long back
after long time i tried to logon but could not. tried 3 times , now SAP got locked unable to logon. can you suggest me how to logon. looking for your quick reply.
Thanks,
Purnima.

Try to log on with Default's pass for user SAP* / DDIC, if you don't rember or if you blocked the user's, what you can do is to erase the user SAP* from the table USR02, so now you will be able to log on with default password PASS.
To delete the user just log on into database with your SAP<SID> user an execute the querry
delete from usr02 where bname = 'SAP*' and mandt '<mandt>'
I hope this help.
Take care.

SAP Hana FAQ Frequently Asked Questions

Hi All,
SAP have published a fantastic Knowledge Base Article containing an extremely detailed
SAP Hana FAQ - Frequently Asked Questions
Go and download it now, it's here:
2000003 - FAQ: SAP HANA
And then come back to it from time to time, because not everything in there is released yet.
Best regards,
Andy.

For the sake of completeness, there are now a number of very useful Hana FAQ OSS Notes, here's the list so far:
. OSS 2000003 - FAQ: SAP HANA
. OSS 2000000 - FAQ: SAP HANA Performance Optimization
. OSS 1640741 - FAQ: "DB users for the DBA Cockpit for SAP HANA"
. OSS 2039883 - FAQ: SAP HANA database and storage snapshots
. OSS 2044468 - FAQ: SAP HANA Partitioning
. OSS 2057595 - FAQ: SAP HANA High Availability
. OSS 1999997 - FAQ: SAP HANA Memory
. OSS 1999880 - FAQ: SAP HANA System Replication
. OSS 2044468 - FAQ: SAP HANA Partitioning
. OSS 2000002 - FAQ: SAP HANA SQL Optimization
. OSS 2073112 - FAQ: SAP HANA Studio
. OSS 1999998 - FAQ: SAP HANA Lock Analysis
. OSS 1905137 - FAQ: SAP HANA - Obsolete tables
. OSS 1999930 - FAQ: SAP HANA I/O Analysis
. OSS 1914584 - SAP HANA Live Browser FAQ
. OSS 2057046 - FAQ: SAP HANA Delta Merges
. OSS 1642148 - FAQ: SAP HANA Database Backup & Recovery
. OSS 2104291 - FAQ - SAP HANA multitenant database containers
. OSS 2100009 - FAQ SAP HANA Savepoints
. OSS 2082286 - FAQ: SAP HANA Graph
. OSS 2081591 - FAQ: SAP HANA Table Distribution
. OSS 2053330 - FAQ: Operations Recommendation on SAP HANA Alerts
If you are interested in Hana Basis related OSS Notes, then the longest list of Hana OSS Notes publicly available on the internet is over here.
Best regards,
Andy

SAP* is locked

Similar Messages

Maybe you are looking for