Solution : https://service.sap.com/sap/support/notes/541311 (SAP Service marketplace login required)
Summary :
This SAP Note discusses best practices for utilizing parallel processing during client copy tasks in SAP systems. It covers the configuration and usage of parallel processes via RFC server groups, enhancing performance through appropriate process allocation per database CPU, and troubleshooting common issues such as inactive or non-displaying processes in transaction SM50 or SM66. The note emphasizes the serialization of copies from the same source client to avoid conflicts and outlines the termination processes of parallel copies. Additionally, it highlights that settings for parallel processes in client copy do not apply to client exports.
Key words :
asynchronous rfc -> define rfc groups, tp/r3trans transport programs, application server increases considerably, computing center management system, existing rfc server group, rfc server group maintenance, sap web application server, systemwide work process overview, global work process overview, -> background processing -> parallel processing
Related Notes :
| 857973 | Deleting clients efficiently using Oracle |
| 806554 | FAQ: I/O-intensive database operations |
| 557132 | CC-TOPIC: Remote client copy |
| 552711 | FAQ: Client copy |
| 550226 | CC-ADMIN: Copying the Customizing takes a long time |
| 540158 | iSeries: Error -901 in client copy |
| 517589 | iSeries: Client copy performance |
| 489690 | CC INFO: Copying large production clients |
| 142419 | Resource distribution for RFC and tRFC/qRFC configuration |
| 103523 | RFC load distribution |
| 99284 | RFC exception: RESOURCE_FAILURE |
| 74141 | Resource Management for tRFC and aRFC |