SAP Note 22514 - CC-INFO: Error analysis for client copy

Component : Client Copy (For ByD issues select BC-TLM-CP) -

Solution : https://service.sap.com/sap/support/notes/22514 (SAP Service marketplace login required)

Summary :
A client copy process in SAP systems (using transactions such as SCC0, SCC1, SCC9, etc.) terminates unexpectedly and does not complete table copying. This SAP Note advises users on steps necessary for error analysis and outlines guidance on resolving the issue through a sequence of specific checks related to client copy types, copy profiles, and error logs (transaction SCC3 logs, system logs via SM21, and ST22 for dumps). It emphasizes using naming schemes for sourcing relevant Notes, such as CC-RELEASE, CC-TOPIC, CC-INFO, and CC-ERROR for targeted assistance. The Note also highlights using support files and logging procedures detailed in transactions like SE11 and SE14 to ensure database consistency and troubleshooting.

Key words :
check job management smx/sm37, additional key words scc0, run-time environment point, selection   ccseltab-status <> 'p', client copy tools follow, spool sp02/sp01, r3 rfc destination, compare table contents, copy larger protocols, executed exit program

Related Notes :

634620CC-TOPIC: Error in the client transport as of WAS 6.10
613872Oracle traces with ORADEBUG
572139CC-INFO: Client copy hangs with a certain table
557132CC-TOPIC: Remote client copy
552711FAQ: Client copy
495911
491923CC RELEASE: Client copy errors in Release 6.20
489690CC INFO: Copying large production clients
446485CC-ADMIN: Special copying options
446294CC INFO: Logical system name and client copy
442415Inconsistent table BDCP --> client-specific change pointer
432152CC-RELEASE: Error in client copy in Release 6.10
390317VA02: Double/incorrect planned revenues after client copy
365304CC-ADMIN: Reports for deleting tables
355713CC-TOPIC: User masters during client copy
350189CC-TOPIC: Error messages, client copy terminations
350101CC-TOPIC: Client copy and addresses up to 4.6D
339932Termination with invalid BCD number in developer trace
338578CC-TOPIC: Error in client transport as of 4.5
304605SAP query: Queries missing after client copy
211492Inconsistency between ABAP Dictionary <-> database
206523CC-RELEASE: Client copy errors in 4.6C and 4.6D
192494CC-TOPIC: Copy logs (SCC3)
191660
180949CC-INFO: Change documents for a client copy
161495CC-RELEASE: Error in client copy in 4.6A and 4.6B
147537CC RELEASE: Error in client copy in Release 4.5B
139418
130540CC-TOPIC: Client copy and addresses in 4.0B
126619CC RELEASE: Error in client copy in Release 4.0B
125032Search for corrupted texts in cluster table STXL
118823CC-ADMIN: Size of a client
116787CC-TOPIC: Remote client copy
99502CC-RELEASE: SCC1 in Release 4.0B
96296CC-ERROR: Database problem in client copy
91980Missing output of RFC short dump after login error
91096Table Compare: Info about Cust. Cross System Check
89384Checking cluster tables with R3check
85193Invalid name for TemSe object/syslog message F3T
83819DB6: Collecting support data
73779AS/400: Problems during client transport R3trans
70547CC-TOPIC: Client transport
70290CC-INFO: Excluding tables with 'RSCCEXPT'
69556CC-TOPIC: Missing tables and data
69444CC-TOPIC: Error messages/terminations up to 4.0B
68048
67205CC-INFO: Copying large and productive clients
49023AS/400: Client Copy
48400Reorganization of TemSe and Spool
47502CC-REMOTE: Messages of the Remote Clientcopy
42870CC-ADMIN: Periodic scheduling does not work
41839CC-TOPIC: User masters and client copies until 4.0
37104Error analysis: Background processing system
33873What do the semaphores mean?
24853CC-INFO: Client copy, functionality
19574CC-ADMIN: Controlling data selection during client copy
15374Checklist: Performance analysis
6975Validierung/Substitution/rules - utility reports
2857What table delivery classes are there? What is their signifi