Here is the right procedure - All explanations are give above .. SAP replied in response to our OSS message . I have added a procedure for more clarity
1. Check the last entry in table CCCFLOW - for the destination client . ( For example MANDT value = 362 when CCopy is run from 100 to 362 client )
2. Make sure the TSTAMP corresponds to the time when the last Client Copy was started .
3. Make Sure NO Client copy is running - Stop / Cancel the Current client . For example if it was run in 10 parallel and 8 have already gotten this dump - the last 2 will also get this dump - so no point in wasting time to let them fail also eventually.
4. Change the value of NBRINS from 2,147,483,469 to 1 in table CCCFLOW for the last entry ( as above )
5. If SE16 is locked for change in the destination client - Do it on DB2 directly - something like this
update sapr3.cccflow set nbrins = 1 where mandt = '362' and tstamp = '20130812213848'
6. Restart the Client Copy and it will work Fine
7. This will result in loss of statistics in the Client Copy output - But when u r copying more than 2 billion lines of data - that is really not important ..
Hope this helps everyone