Client copy log.

[Former Member]

Hi,

I have done a local client copy and it got cancelled. Below I have attached log information.

It looks like all files are copied and I have checked the file (/usr/sap/trans/log/CC09CUGU.CT1) for any error but I cant find not even a single error message.

Can you suggest where can i find the reason for client copy cancellation?

Any suggestion will be of great help.

-

---

Target Client 495

Source Client (incl. Auth.) 400

Source Client User Master 400

Copy Type Local Copy

Profile SAP_ALL

Status Cancelled

User copyuser

Start on 08.01.2012 / 00:00:56

Last Entry on 08.01.2012 / 01:59:44

Last Action: Post Processing Component

- Last Exit Program RBDLSMAP BC-MID-ALE

Statistics for this Run

- No. of Tables 60101 of 60101

- Deleted Lines 20026392

- Copied Lines 20028039

Check System Log (SM21)

-

---

Last entry from /usr/sap/trans/log/CC09CUGU.CT1

Analysis/Generation/Deletion of condition objects during client copy

/SAPCND/CC_GROUP_WS_NG executed 0( 0) entries copied

Runtime 0 seconds

Exit program /SAPCND/CC_GROUP_WS_NG successfully executed 01:59:37

/SCMB/DF_GENERATE_CLIENT_COPY executed 0( 0) entries copied

Runtime 0 seconds

Exit program /SCMB/DF_GENERATE_CLIENT_COPY successfully executed 01:59:39

Runtime 0 seconds

Exit program BUS_SCR_CONTAINER_CLIENT_COPY successfully executed 01:59:40

EFG_FORM_CC_EXIT_AFTER executed 0( 0) entries copied

Runtime 0 seconds

Exit program EFG_FORM_CC_EXIT_AFTER successfully executed 01:59:42

Automatic postprocessing of client 495 was successful -> long text

FINB_TR_CC_EXIT_TARGET executed 0( 0) entries copied

Runtime 0 seconds

Exit program FINB_TR_CC_EXIT_TARGET successfully executed 01:59:44

[Former Member · Accepted solution]

Thanks for all the reply.

Two solution to this problem as far as our experience.

1. You need to click "FINB_TR_CC_EXIT_TARGET" in the error screen. Which in trun will take to a post processing screen.

2. Please continue the client copy in dialogue mode, this will take you to BDLS screen and from there you can fix the issue.

[Former Member]

Hi

we have same problem with local copy or client transport in posting process(SCC7)

and note 2267684 has fix the problem now.

share to all.

[Former Member]

Hello All,

For resolving issue,  please implement the corrections from

following notes to your system:

1754066 client copy hangs in RBDLSMAP.

1683841 client copy kept failing at RBDLSMAP

1392537 Client copy terminates with RBDLSMAP

Please check, that also the corrections from following notes are

already implemented in your system:

1542673 client copy stops at RBDLSMAP

1424654 Client copy cancels at exit RBDLSMAP

Afterwards, restart please the client copy!

Regards,

Amit

[Former Member]

Hello Amit,

thank you very much. It solved the problem.

Regards,

Michael

[yogesh-garg]

HI Michael,

Can you please share how you resolved the issue.

I am facing exactly same issue.

Regards

Yogesh Garg

[former_member661805]

Work fine

[Former Member]

Hello Easwar,

Did you restart the client copy and if so, did it ever complete successfully?

Can you give us an update?

[Former Member]

Hello Michel,

I was waiting for this weeks CC to get completed. Here is my observation. Actually we schedule it as a job and it gets failed with last step and when we restarted it finished with no problem in no time.

Any idea why its behaving like this.

[Former Member]

Hi Easwar,

When the CC got cancelled without any error, have you resumed the CC job to run in Dialog mode to get complete? If your answer is yes, then you had issue previously due to missing authorization on last run program.

Best Regards,

Vasanth G

[Former Member]

Did you resolve this? We're seeing the same problem. We have looked at 1424654 and have support pack 10 for 702 sap-basis.

What did you do to fix or get past?

Thanks,

Daniel

[Former Member]

HI Daniel,

What does SCC3 log says

Also with wihich user you are running Client Copy ,if you are running with a Dialog user make sure that it has sufficient authorisation to run Client Copy ,otherwise simply assgin SAP_ALL profile to this user and remove once copy was done.

Regards,

Srini Chapa.

[Former Member]

Hello Daniel,

No clue about the problem, but if I restart the client copy its getting finished successfully. I am using a user with SAP_ALL authorization. Lets see.

If I find anything will update you soon.

[Former Member]

Hi

You can check in SCC3 > Exports > All clients and select the export log.

or else. you can find the log in /usr/sap/trans/log, with file <SID>ET<TRnumber>.<SID>.

~Rajesh

[Former Member]

Hello Rajesh,

I can't find any file of type.

<SID>ET<TRnumber>.<SID>.

Warm regards,

Easwar.

[former_member204080]

Hi,

Can u mention with which user u are doing client copy

[Former Member]

I am using normal dialog user, no SAP* or DDIC.

Regards,

Easwar.

[Former Member]

Hello Easwar,

Try the correction note suggested by venkatesh,and then try to redo the client copy.

Also before starting client copy check in

SM12 that nothing is locked and I will suggest to logoff every users from source client before start of copy.

and check through SE06 that system is modfiable globally and client is open through SCC4.

Regards,

Amit Barnawal

[Former Member]

HI,

To check the logs you can goto either /usr/sap/trans/log (or
<host>\sapmnt\trans\log\CC<>.SID) and check client copy logs over there or

SCC3-->Click on "All Clients" >Select the specific entry>You get many options there such as Details/File Log/Main Import Log/Main export log.Explore in all these to get desired log.

Regards,

Ashutosh

[Former Member]

Hello Easwar,

Do you see any error messages reported in SCC3?

Do you see any dumps in ST22 or errors in SM21?

Thanks,

Siva Kumar

[Former Member]

Thanks for the reply.

That is the problem, no error message in sm21 and st22 or scc3 neither.

[Former Member]

Hi Easwar,

Could you please have a look at the following note.

Note 1424654 - Client copy cancels at exit RBDLSMAP

Br,

Venky

[Former Member]

Hello Venky,

I shall check the same and get back to you on this.

Warm regards,

Easwar.