Note 557132 - CC-TOPIC: Remote client copy
Note Language: English Version: 16 Validity: Valid from 30.03.2005
Summary
Symptom
The prerequisites and use of the Remote Client Copy are described. This
note supplements the online documentation (application help) and replaces
note 116787 as of WAS 6.10.
A Remote Client Copy can be used to transfer Customizing, user and
application data between two systems. The target client is completely reset
for this (exception: SAP_USER copy profile, see also notes 19574 and
24853).
However, a repository (programs, table definitions, system variants and
so on) is NOT transferred.
In fact, a prerequisite for this is that the systems have the same
development status. This means that all software components must have the
same release and the same Support Package version in both the
source and target system. This particularly applies to the SAP_BASIS
component.
The Solution section under point 1 discusses the options that exist if you
cannot install an add-on, for example, in the target system.
Advance corrections concerning the client copy must be performed in both
the source and target system.
Caution! Data loss can occur in Release WAS 6.10 and WAS 6.20
before Support Packages SAPKB62039 or SAPKB61039 or note 718799.
Make sure that the corrections have been implemented in the target
system before the copy is started.
However, a homogeneous system landscape is not required. The existing data
in the source client must only be converted into the character table (code
page) used in the target system. If required, this happens automatically
but it requires a great deal of processor time on the application servers
used in the target system.
The Solution section deals with typical problems.
More Terms
SCC9
Cause and Prerequisites
You are using transaction SCC9 to start a Remote Client Copy in the target
client. (As a result, the target system is also called the local system in
the following and the source system is called an RFC system.)
Here you must specify the copy profile (for more information, see the
online documentation as well as note 24853) and the RFC destination.
The RFC destination must have been created beforehand using transaction
19.03.2008 Page 1 of 7
Note 557132 - CC-TOPIC: Remote client copy
SM59 (which can be accessed via the F4 input help). With this destination,
you must be able to access the source client data in the background (that
is, without a logon screen). There are two options for this:
o Set up a Trusted System connection. For more detailed information
on Trusted System connections, see note 128447, for example.
o If you do not want to set up a Trusted System connection, the RFC
destination must be created using both a user and its password in
the source client. For security reasons, you should use a user with
the user type "communication" in the source client.
If necessary, set up parallel processes (note 541311).
Depending on the status and size of the source database, you should
increase the "rdisp/max_wprun_time" TIME-OUT parameter on the
application servers of the source system. This may also be done temporarily
using transaction RZ11. Display the parameter. You can change it
afterwards. You do not have to restart the system for this.
You should also refer to note 489690, which contains information on copying
large clients. In particular, it is recommended that you carry out a test
run in advance (select the simulation type), to eliminate problems with
PSAPTEMP or TIME_OUT in the source system, for example.
You can now start the client copy (we recommend that you schedule this in
the background).
The process for the Remote Client Copy:
A Remote Client Copy works as follows:
a) Create a list of tables to be copied. The process here is the same
as for a local copy (once in the source clients and once in the
target clients in each case). For more information on selecting
data, see notes 19574 and 24853.
b) Test the dictionary compatibility between the system.
The structure of all tables to be copied is examined. If only some
of the data can be copied because, for example, tables are missing
in the target system or fields are missing in the tables, the copy
process is cancelled after the DDIC comparison. All table
differences are recorded in the log. The Solution section deals
with possible messages.
c) The data is now copied to the tables. For this, existing entries in
the target system are deleted first and the data in the source
system is then transferred in blocks to the target system.
d) Finally, corrections, local adjustments and generations are started
automatically (reports and other objects are generated which,
according to the Customizing, are required at runtime).
Solution
The client copy log notes errors and problems that occur (transaction
SCC3).
19.03.2008 Page 2 of 7
Note 557132 - CC-TOPIC: Remote client copy
The file log for the copy contains details that you can display from the
log display. It is usually enough to open the log up to level 3 to analyze
errors and warnings. Alternatively, you can expand the log completely and
search for the name of the affected tables. You should also consider
messages that immediately follow or precede as these often contain
additional information.
For additional notes on analyzing problems with a client copy, see note
22514. However, note that important information is often only available in
the SysLog (transaction SM21) of the source system.
1. Status "Cancel, Dictionary Differences."
The copy was cancelled due to different table definitions that result
in only some of the data from the source system being transferred to
the target client. Message TA 251 or TA 254 is displayed in the log:
TA251 & tables cannot be converted
TA254 Critical differences: Missing tables: &
The following messages appear in the file log (these caused the above
message):
TA281 Length change
TA283 Table & is convertible to the RFC system, field missing
locally
TA284 Table & is incompatible, the fields are incompatible
TA285 Table & is incompatible, fields are missing in both systems
TA287 Table & is only convertible from the local system to the RFC
system
TA308 Table definition & missing in the target system
Clarify the cause of the differences between the systems. For this,
the version management (transaction SE11) of the tables in the
corresponding systems is the first indicator. From there, you can also
compare the table structures with other systems via an RFC
destination.
Upgrade the systems to the same development status.
It only makes sense in exceptional cases to exclude tables from the
copy because changes to the table definitions are frequently linked to
incompatible program changes. In each case, the customer always
assumes responsibility for the consistency of the affected data. SAP
cannot provide support for this, especially if it is a modified
enhancement (ADD-ON), for example:
o Individual tables may be excluded (note 70290 - with message TA308
in the source system, otherwise in the target system).
o If many tables are affected, for example, because an add-on cannot
be installed in the target system, the RSCC_PACKAGE report is
available as of Basis Support Package SAPKB61026 or SAPKB62013. You
can use this report to include complete development packages
(formerly development classes) in an exception list in the source
system. If a table is missing from these packages in the target
19.03.2008 Page 3 of 7
Note 557132 - CC-TOPIC: Remote client copy
system, this merely generates a message in the log and no longer
causes a termination.
o As a last option you also have the parameter NO_RFCCHK (see note
446485). This will always prevent termination and easily causes
problems not to be identified. This parameter should therefore only
be used as a last resort and only after an incoming check of all
DDIC differences.
Tables, for example, for which a field was added in the source
system is not copied but rather initialized in the target client.
If the table definition cannot be adjusted, the data in these
tables must be copied, if required, to the target system (using
another path). To do this, you can, for example, use the Transport
Organizer (transaction SE01) to create a "Transport of copies" in
the source client with an "R3TR TABU <table name>" entry and
transport this when the client copy is finished.
o With the option IGNORE_CON (see note 446485), the tool ignores data
loss caused by conversion errors. This affects both conversion
problems due to alternative code pages and those due to different
table structures. In connection with the NO_RFCCHK option, copies
are therefore also possible between different systems with minimal
data loss. This is the customers responsibility as well. You will
find further information in the specified note.
2. The file log contains message TA 250:
TA250 There are & non-critical differences in the table structures
The following messages appear in the file log (these caused the above
message):
TA280 Table & only exists locally
TA282 Table & is convertible to the local system, field missing in
RFC
TA288 Table & is only convertible from the RFC system to the local
system
TA319 Type of Table & is not Identical
TA262 Table has convertible differences: &
These messages are only used for information and do not impact
negatively on the copy because all of the relevant data can be copied.
However, you should always clarify which causes exist for the
differences and if required, upgrade the systems to the same
development level.
3. Status "Ended with errors". One of the following entries exists for
one or more tables in the log overview:
RFC Error
Read or Conversion Error
Codepage Conversion Error
The following messages appear in the file log (these caused the above
message):
TA231 RFC error. & Table: & RC: &
19.03.2008 Page 4 of 7
Note 557132 - CC-TOPIC: Remote client copy
Text explaining the problem in more detail usually appears in
the file log immediately after this message. If required, check
the SysLog (transaction SM21) in the source system. There is
usually a TIME-OUT or a problem with the source database.
TA 340 Codepage conversion error for table &
You want to copy entries from the source system that cannot be
converted into the local character set table (code page) of the
target system. The process of copying this table was cancelled
as a result.
Check whether this is any point in having a copy between
systems with different code pages. The best solution is to
change the target system to UNICODE where necessary.
If you have eliminated the problems, you can use the 'Copy errors'
function in the target client to copy the missing data from the log
display. The same applies if there were write errors in the local
system.
Header Data
Release Status: Released for Customer
Released on: 30.03.2005 10:24:53
Priority: Recommendations/additional info
Category: Consulting
Main Component BC-CTS-CCO Client Copy
Additional Components:
CO-PA Profitability Analysis
EC-EIS Executive Information System
EC-EIS-DCM Data Collection
FI-SL-SL Basic Functions
Valid Releases
Software Component Release From To Release and Following
Release
SAP_BASIS 60 610 640 X
Support Packages
19.03.2008 Page 5 of 7
Note 557132 - CC-TOPIC: Remote client copy
Support Packages Release Package Name
SAP_BASIS 610 SAPKB61026
SAP_BASIS 610 SAPKB61030
SAP_BASIS 620 SAPKB62013
SAP_BASIS 620 SAPKB62018
Related Notes
Number Short Text
898228 CC-Error: Remote copy with active option IGNORE_CONV aborts
860720 CC-ERROR: Table definition XXXX missing in the target
769783 SYSTEM_FORMAT function module is obsolete
718799 CC ERROR: Loss of data during remote copy
701336 CC ERROR: Write error Internal error in remote copy
692660 CC-ERROR: USRACLEXT not copied with user master
691937 FINB_TR(CC): Error message /EACC/DR028 in FINB_TR_EXEC_AI
677933 CC-ERROR: Remote copy with SAP_USER loses addresses
647495 RFC for Unicode ./. non-Unicode Connections
612883 System time zone after cross-system client copy
589886 CC-ERROR: Performance with the remote SAPscript copying
562628 CC-ADMIN: Protecting the source from a second copy
560552 CC-INFO: Restart and "Copy error"
552711 FAQ: Client copy
550894 CC-ADMIN: Setting up a new client
545177 FAQ: Preliminary steps in analyzing RFC connections
545136 FAQ: Test tools for RFC connections
541311 CC-INFO: Parallel processes FAQ
500235 Network Diagnosis with NIPING
491923 CC RELEASE: Client copy errors in Release 6.20
489690 CC INFO: Copying large production clients
446485 CC-ADMIN: Special copying options
446279 Syntax errors or terminations after client copy
445195 CC ADMIN: Remote copy with cross-client Customizing
432152 CC-RELEASE: Error in client copy in Release 6.10
144015 CC-INFO: client copy and CO-PA/EC-EIS
128447 Trusted/Trusting Systems
89384 Checking cluster tables with R3check
79991 Multi-Language and Unicode support of SAP applications
70290 CC-INFO: Excluding tables with 'RSCCEXPT'
63347 List: CPIC error codes
31557 The Multiple-Client concept of mySAP.com Solutions - Short O
31496 CC-INFO: Client deleted by mistake
24853 CC-INFO: Client copy, functionality
22514 CC-INFO: Error analysis for client copy
Attributes
19.03.2008 Page 6 of 7
Note 557132 - CC-TOPIC: Remote client copy
Attribute Value
Transaction codes SCC9
weitere Komponenten CO-PA
weitere Komponenten EC-EIS
weitere Komponenten EC-EIS-DCM
weitere Komponenten FI-SL-SL
Transaktionscodes - manuell SCC9
19.03.2008 Page 7 of 7
