How do I delete a client?
As of Release 3.0 the transactions of the tool Client copy are used for this (SCC5 as of Release 3.0D). The method via R3trans is not complete.
Up to Release 2.2C you need to reset the target client completely before copying a client, if the target client had already been created.
In Release 3.0A, problems occur when you try to delete a client from the system using Transaction SCC1.
In Release 3.0B, it is somewhat difficult to press the 'Delete' button.
Release 3.0C:
- a) The message 'W: Source client does not exist' appears.
- b) More than & tables were not copied or were copied incorrectly.
In Releases 3.0C to 3.0E, sometimes only the user masters are deleted during a deletion in the background.
Release 3.0x:
- a) The deletion terminates in phase NG? with an authorization problem (for example OPEN_DATASET_NO_AUTHORITY).
- b) The client entry was not deleted from T000, although the option was marked.
- c) In rare cases, the log shows that the run terminated although it is still processing and also the number of the processed tables increases when you refresh.
- d) The deletion terminates in table USR12 with an authorization error.
RSCLICOP, client reset, client remove, SCC1, SCC5
A client that is not used any more should be deleted or has to be initialized for a client copy.
Release 3.0B:
Warnings are issued when deleting a client; the warnings can create confusion and should be ignored.
In some circumstances, a generator will execute additional authorization checks after the table has been deleted and the client completely deleted.
Release 3.0c:
- a) Ignore the warning 'Source client does not exist'.
- b) Message 'More than & tables were not copied or were copied incorrectly': When trying to delete table contents, the database reports an error for more than 50 tables.
Releases 3.0c and 3.0e
For systems coming from Release 3.0C, the profile DELETE is defined without Customizing and without master and transaction data. This results in the fact that only user masters are deleted when you delete in the background.
Release 3.0x:
- a) In rare cases, authorization checks are still executed in phase 'N'. However, as the client was deleted beforehand, the authorizations no longer exist, and a termination occurs.
- b) The deletion of the entry from table T000 is sometimes not carried out.
- c) The lock set by the active process was deleted. Thus, the log display cannot recognize that the run is still active.
- d) For Release 3.0E, a new authorization check was implemented to write operating system files. Since the authorization tables are also deleted during the entire deletion, no authorizations exist for further deletion access or for writing log entries as of the time these tables are deleted. As a consequence, the deletion job terminates during the next deletion or logging attempt.
Resetting a client during a client copy (RSCLICOP or Transaction SCC0) is initialized with the new parameter:
"Initialize and create",
All tables are automatically reset for this client. This does not include the tables of the user administration.
As of Release 3.0, this function is provided under 'Tools' in the administration menu (<=3.0C: SCC1, >=3.0D: SCC5).
You can also delete a client explicitely via R3trans. With this method, however, only those parts of the client are deleted which are in the tables of the client as the first key field.
Example for resetting the client 010 with R3trans:
In /usr/sap/trans/bin, create a command file with the following contents (for example remove.010):
clientremove
client=010
select *
Set the environment variables for the SAP System containing the client you want to delete. You can display the correct values by calling ./tp go
in the above directory.
Then start /usr/sap/
-w /usr/sap/trans/tmp/remove.010_SID -u 1
/usr/sap/trans/bin/remove.010
The call tail -f /usr/sap/trans/tmp/remove.010_SID
provides information on the progress of the delete operation.
If you have problems when resetting spool and batch input data, refer to Note 13620.
For Release 3.0B (SCC1), simply make any entry in the fields 'transport request' and 'source client' and press the pushbutton to delete the client.
The termination caused by the authorization check can be ignored: all data will be deleted consistently.
Release 3.0C:
- a) The warning 'Source client does not exist' can be ignored.
- b) The message 'More than & tables were not copied or were copied incorrectly' is generated by a database inconsistency. Rebooting the database often helps here.
Check for the following error in the system log: SQL Error 55 during table access: ORA-00055 max. number of
dml-locks exceeded.
In this case, parameter "dml_locks" in file "init
Save and start the following program: Report YDBSWTCH.
tables ccdbcheck.
delete from ccdbcheck where dbsys = 'ORACLE'.
Releases 3.0C to 3.0D
Occasionally, only the user data USR* are deleted when the job is executed in the background. In this case, start the job in the foreground or use R3trans.
Release 3.0x
- c) The job to delete a client terminates due to an authorization problem. When deleting clients, a new authorization check in the kernel terminates the process after the user profile is deleted. At this point, there are still about 1600 tables to be deleted. Delete the user SAP* and delete the client with the initial user SAP*, password PASS. This deletes the entire client.
- d) If the option 'Also delete from T000' was checked, the entry is not deleted from T000 if a termination occurs. Delete the entry from table T000 using Transaction SM30.
- e) The lock that was set by the active process was deleted. Thus, the log display cannot recognize that the run is still active. Use Transaction SM37 to check whether the job is still active. The missing lock does not affect the deletion.
No comments:
Post a Comment