cancel
Showing results for 
Search instead for 
Did you mean: 

****CRITICAL Issue on client copy taking long time****

Former Member
0 Kudos

Hi Friends,

On a recently installed ECC6.0 i have started a local client copy with SAP_CUST as profile and 001 as source client.The job is runing for more then 30 hours with out any errors in the SCC3, i have done a client copy on the same server before 1month it took me 6 hours to complete. Now the messages in SM21are:

1)For every 10 minutes there is TIME_OUT dump then i have increased the rdisp/max_wprun_time to 1200 from 600 and tried again still same dumps.

2)The short dump "070115 131438" is generated.

3)System time zone can not be determined, Enter using STZAC.

i have changed if from CET to MST(currect time zone) and restated, still it shows same message in SM21

4)R6 perform rollback

5)Buffer TABL/TABLP reset

Please let me know other log files required to solve this issue.

System Information:

RAM: 6 GB, HP-UX IA 64, swap is 12 GB (Pesently 0% of the swap space is used), wp Dia=10, wp bg=5, v1=2,v2=2.

For every useful answer i will reward with points.

Thanks

Naren

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

so far the measure you have taken are right.

just for confeemation are you runnning the job in dialog mode?

if so change to back ground

if you are already doing in backgroun check the work process devtrace.

and also status in SM50/SM66 wether is actually doing or not

also check the available disk space.

Samrat

Former Member
0 Kudos

Hi,

Thanks for your reply, i have experience of client copy and performing the same in the background only, i have checked in sm50 the back ground process is running.

In SCC3 it shows the client copy as in progress,

i have checked the usr/sap/RD1/SYS/trans/log/CC00005.log also it does shows that copy is in progress.

PLEASE ASK ME FOR MORE INPUTS to reolve this long pending issue and Your help will be greatly appreciated.

Thanks

Naren

Former Member
0 Kudos

Hi,

As you said you are using the Parallel processing,It works this way

The job itself runs in a background process, the parallel processing tasks that it starts run in dialog work processes. That is the reason why you are getting Time outs and we got confused.

Check the following things if you want to use parallel processing,

1) RFC server group created in transaction RZ12.

2)Use 2 workprocess for parallel processing for Local client copy for each CPU

3)increase the max_wprun_time to 3600

cancel the existing copy in SCC3 and then terminate the relavant processes from SM50

Hope this helps

Regards,

Phani

Former Member
0 Kudos

Hi,

Thanks for the information provided.

Can i run the local client copy 001 --> 200 client when users are working on only 100 client ?? is this ok ??

Thanks

Naren

Former Member
0 Kudos

Not a problem, you can make a new copy to a new client 200, the data will not be affected. The only issue you should take in count is the processor, maybe users working in client 100 experiment a little delay executing their transactions. If is Production I would suggest you to make it in low-peak use hours.

Hope it helps you,

Jessica.

Former Member
0 Kudos

Hi,

In the process of Local client copy 001-->200, SCC3 is showing me below

warning's are these ok??

Warning and Errors in SCC3 :

Table Name Component Package

AGR_TCODES BC-SEC-USR-PFC Program Cancel (See SM21)

CEFORMS CO-PA Program Cancel (See SM21)

CEPRINT CO-PA Program Cancel (See SM21)

DSYS_PHHYPE_ECD2 PY-XX Program Cancel (See SM21)

DSYS_PHHYPE_E_CD PY-XX Program Cancel (See SM21)

P01T_AGS PY-DE Program Cancel (See SM21)

SETHEADER FI-SL-SL-MD-SE Program Cancel (See SM21)

SPERS_OBJ BC-SEC-USR Program Cancel (See SM21)

SWD_NODES BC-BMT-WFM Program Cancel (See SM21)

T156X MM-IM Program Cancel (See SM21)

TA21L1 FI-TV-PL Program Cancel (See SM21)

TA22RSS FI-TV-PL Program Cancel (See SM21)

TA23HOTELS FI-TV-PL Program Cancel (See SM21)

TCMS_PCN_A_MSG FS-CMS Program Cancel (See SM21)

TKUNDEBUKRS LO-MD-BP-CM DDIC Error (See SE14)

TLTYP BC-FES-GRA DDIC Error (See SE14)

Thanks

Naren

Former Member
0 Kudos

Can you check the SM21 and SE14 logs they tell you and see what is the message error there?

Former Member
0 Kudos

Hi Friends,

The issue has been solved, the solution is the server has only CPU and there was lot of cpuwait time so client copy took many hours, adding one more CPU solved the problem.

Answers (2)

Answers (2)

0 Kudos

Yes, five processes are too much for one CPU. The recommendation is two per CPU or in case of remote client copies three per target database CPUs.

But I have another issue with your message. You should not use client 001 as the source of your customizing. I know that there was an error in the ECC documentation but they should have fixed that in the mean time.

Client 001 is an ordinary customer client and is not supplied with any update after the initial make of the release.

As off Netweaver04s new installations file the JAVA users in client 001. Thus it could be that you need the users of 001. But the rest of the client is still nothing else than an outdated playground from the day on you applied the first Support Package, Add-On, Industry Solution, Language Package etc.

Former Member
0 Kudos

HI

Are you running the Job in foreground, if so try running it out in Background.

Regards,

Phani

Former Member
0 Kudos

No, i am runing thr job in the backend only.

In SCCL i have selected parllel processing and gave the number as 5.

Thanks

Naren