Solution : https://service.sap.com/sap/support/notes/67205 (SAP Service marketplace login required)
Summary :
This SAP Note discusses best practices and methodologies for copying productive SAP clients and addresses associated challenges and limitations. It advises against using productive client copies for production purposes due to incomplete data transfer like change documents and incorrect ALE distribution scenarios, recommending a database copy instead. The note highlights the massive data load involved in such operations which may impact system performance severely. For large clients, a parallel copy technique can reduce copy durations. Technical considerations like database reorganization, increasing parameter limits, and using appropriate tools for data deletion and transport are also discussed. It's important to consult SAP Services for expert analysis on customizing requirements via the component XX-SER-CS.
Key words :
sapkh45b31 sapkb46b17 sapkb46c08 sapkb46d03with regard, separate 'installation guides' cd, component xx-ser-cs, separately purchased migration service, sap consulting offers services, specific text copy tools, heterogeneous system copy guide, /3 homogeneous system copy' guide, production systemusing client copy, parallel client copy program
Related Notes :
| 601196 | Client copy: Problems with report RCTXTCPY |
| 552209 | Maximum memory utilization for processes on NT/Win2000 |
| 550226 | CC-ADMIN: Copying the Customizing takes a long time |
| 489690 | CC INFO: Copying large production clients |
| 446485 | CC-ADMIN: Special copying options |
| 446294 | CC INFO: Logical system name and client copy |
| 436980 | Database error with client copy |
| 397094 | DB error in client copy for too many addresses |
| 365304 | CC-ADMIN: Reports for deleting tables |
| 212727 | CC-INFO: FAQs for parallel processes up to Release 4.6D |
| 210919 | Collective note: Logical system names |
| 208919 | CC-INFO: Performance as of Release 4.6 |
| 191960 | Logical system and object links |
| 185822 | ora-1555 - cause and action |
| 180949 | CC-INFO: Change documents for a client copy |
| 180541 | CC-INFO: Performance problem when copying text |
| 159316 | Reorganizing tables on SQL Server |
| 159171 | Recompilation of Stored Procedures |
| 155413 | Analysis of slow SQL statements |
| 143998 | DB2/390: Pre-deleting Client Data for Large tables |
| 118823 | CC-ADMIN: Size of a client |
| 113008 | DB2/390: Maintaining Catalog Statistics |
| 103747 | Performance: Parameter recommendations as of Release 4.0 |
| 102034 | R3trans: Control of the COMMIT intervals |
| 96732 | CC-INFO: DB2/390 - client copy is very slow |
| 96296 | CC-ERROR: Database problem in client copy |
| 89384 | Checking cluster tables with R3check |
| 89188 | R/3 System copy |
| 86535 | tp/R3trans: Splitting large exports |
| 70643 | CC-TOPIC: Client Deletion (SCC5) |
| 70547 | CC-TOPIC: Client transport |
| 70290 | CC-INFO: Excluding tables with 'RSCCEXPT' |
| 69444 | CC-TOPIC: Error messages/terminations up to 4.0B |
| 65594 | CC-INFO: Client copy for cluster table is slow |
| 60233 | Oracle rollback segments, more information. |
| 48400 | Reorganization of TemSe and Spool |
| 47502 | CC-REMOTE: Messages of the Remote Clientcopy |
| 43487 | Collective note: SAPDBA - Reorgnztn/Space/Structure |
| 40904 | Performance during availability check |
| 37626 | SAP tool R3chop |
| 36862 | iSeries: Copying an R/3 System |
| 31557 | The Multiple-Client concept of mySAP.com Solutions - Short O |
| 31496 | CC-INFO: Client deleted by mistake |
| 24853 | CC-INFO: Client copy, functionality |
| 22514 | CC-INFO: Error analysis for client copy |
| 20497 | CC-INFO: Long texts with a client copy |
| 19574 | CC-ADMIN: Controlling data selection during client copy |
| 18236 | R3trans: Export to tape / Splitting the export |
| 15374 | Checklist: Performance analysis |
| 12621 | SAPDBA: speeding up a reorganization |
| 6588 | R3trans: Memory allocation failed |
| 3807 | Error messages regarding rollback and undo segments |
| 3155 | Termination due to tablespace overflow |