on 02-02-2010 2:48 AM
Hi, I use tcode SCC9 to implement remote client copy 2 days ago.
The job finished with statu 'COMPLETE WITH ERROR', and i check the log:
The copy of more than 30 tables met errors:
**********************
Table Name Component Package
AGR_1250 BC-SEC-USR-PFC RFC Error
AGR_1251 BC-SEC-USR-PFC RFC Error
KEKO CO-PC-PCP RFC Error
KEKO_CC CO-PC-PCP RFC Error
KEPH CO-PC-PCP RFC Error
KFM_CATEGORY CA-GTF-SGF-KFM RFC Error
KNB1 FI RFC Error
KNB4 FI RFC Error
LTDX BC-SRV-ALV RFC Error
LTDXD BC-SRV-ALV RFC Error
MARC LO-MD-MM RFC Error
MARD LO-MD-MM RFC Error
.....
*********************
log file: (example)
R/3 logon fail
RFC error. System: PRDCLNT800 Table: MARC RC: 10
CPIC-CALL: 'ThSAPCMRCV' : cmRc=17 thRc=672
R/3 logon fail
RFC error. System: PRDCLNT800 Table: MARC RC: 10
CPIC-CALL: 'ThSAPCMRCV' : cmRc=17 thRc=672
Issue seems RFC related(might be because of connectivity issue)
*SAP always recommends to make a client export and import for large DATABASES instead of doing a remote client copy.
Regards,
Nick Loy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marcychen,
I suggest you to check the prerequisites first. We should not miss basic things in remote client copy like kernel patch and support packs should be in same level, checking rfc connections etc,
Thanks & Regards,
Nagendra.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
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.