on 12-11-2008 4:41 PM
Hello,
we've made a remote client copy that lasted 9 hours!
normally it takes 2 hours
in the log we can see :
3 ETA108 "FINB_TR_CC_EXIT" executed " 0"(" 0") entries copied
4 ETA114 Runtime " 21,286" seconds
3 ETA072 Exit program "FINB_TR_CC_EXIT" successfully executed "07:01:17"
could someone tell me what's happens in FINB_TR_CC_EXIT ?
how to know what took so long to complete?
thanks in advance
best regards
hello,
thanks to all for your response.
finally, restarting my target system solved the problem!
best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
The following may be the areas of concern in such a situation
1. Tablespaces may be full or may not have much space.
However transaction SLG1 you can analyse the application log.
2. Another possible solution for a case when the client copy failed could be wth the RFC destinations in SM59.
Try out this method:
Add an RFC destination that looks like this:
Name: FINBTR@<SID>CLNT< xxx>
Type: 3
Desc: RFC Destination for System <SID> Client <xxx>
Target Host: <host name>
System Number: <system number>
Client: xxx
User: <RFC user>
Password: <RFC User password>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With RFC client copies, you will want to lock users out of the system so they won't lock tables by entering data. Did you have a chance to check SM12 to see if a FI table was getting locked?
J. Haynes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.