But before this, table analysis is the key:Ĥ.1 Make sure all tables you selected for exclusion have the “Client” field like MANDT, MANDANT and DCLIENT….Ĥ.2 Check those tables using the below select statement if they have the data only with source system Client number, or they also have the data with multiple Client number. Step 4: Delete those tables excluded on DB2 level. Step 3: Run standard SAP Client Deletion program with Step 1 and 2 in background mode. Step 2: Exclude top N huge tables (as many as, in fact) just like Client Copy (no introduction anymore) Step 1: Deletion with parallel processes just like Client Copy (no introduction anymore) Analysis, Execution, Communication, Re-Analysis, Re-Execution and Re-communication……. In fact, we spent 2 months on Client copy and Deletion between DBA and SAP. The Client Deletion is more complicated than Client Copy. Run R3trans with this control file in background mode like:
Step 4: Continue those excluded tables copy on OS level using R3trans.Ĭreate an R3trans control file on DB server like: You can monitor the parallel client copy in SCC3, SM50, SM66… Step 3: run the client copy in background. I don’t explain how to figure out the huge tables name here, actually it is not easy to do this. Step 2: Exclude huge tables for the client copy to be runĪlways exclude huge tables in the standard client copy and leave them for later process. it is recommended to set to 2 processes per DB CPU core. And then set as many as number of processes as screen below. To set the parallel processes, one RFC group in RZ12 needs to be set. Step 1: Client copy with parallel processes.
(please remember never ever to copy a huge Client with SAP_ALL which is always the disaster in any cases, instead to use an alternative way like system copy) The example here is to copy a Client with 10 TB and with SAP_CUST profile. Please be aware of that this instruction is only for the brainstorming not for detail.Įnvironment: SAP ERP 7.0 OS+Database: AIX + DB2 9.7.5 In fact, I never know how much performance we can get when using this instruction because the copy/deletion will never succeed if we don’t do some things…… So here you can get the instruction regarding how to do this and how to optimize performance for handling a huge client. I promise that you will have the opportunity to meet this situation when you perform a project like HR Care-out, and you should never think it is easy to use SAP standard way like SCCL and SCC5. This document is regarding performance issue of Client Copy and Client Deletion.
0 kommentar(er)
