Please take into account, that the number of rows on ABAP cluster tables will di ffer between source

and target system in case of a Unicode Conversion because of their compressed content. For comparable results use a SQL statement like this: SELECT COUNT (*) FROM CDCLS WHERE PAGENO='0' Factors affecting data export from the source database??This depends on I/O perf ormance, database parameters, and export process balancing Import data into the target database ??This depends on I/O performance, database parameters, and export process balancing During R3load export/import with -Socket option method, there is no dump file an d *.TOC files were created: The same files are used, as in standard R3LOAD scenarios, but no dump or *.TOC f iles are created. The R3LOAD control files must be accessible as usual, on the s ource and target system. The JAVA-based Migration Checker was developed to check that there is a log file f or each package file (option: -checkPackages). This is an indicator that R3LOAD did run for them. The second check is to verify that each action in the task fil e is completed successfully (option: -checkObjects). Unsuccessful tasks are list ed in an output file. The two features are used by SAPINST for NetWeaver 04S and later, to check the import completeness. Database and table depending exceptions are handled automatically. ?? The Table Checker feature is used to check the number of table rows. It can be use d to make sure, that tables are containing the right number of rows after import . As this is a long running task, it can be started manually only. MIGMON: Data transfer configuration variants FTP: File transfer via FTP between source and target system Network: Export directory is shared between source and target system Socket: R3LOAD will use sockets (requires R3LOAD 6.40 or higher). It can be comb ined with ftp to copy R3LOAD control files to the target system. Stand-alone: MIGMON runs stand-alone, i.e. the export will be provided on a tran sportable media only (possibly no fast network connection to source system avail able). The MIGMON server mode for pre-NetWeaver 04 SR1 versions can only be used if SAPI NST has been forced to stop, i.e. by implementing an intended error situation. R3LDCTL generates DDL<DBS>_LRG.TPL files to simplify unsorted exports since NetW eaver 04 CAUTION: When doing a system copy with the change of the code page (non-Unicode to Unicode; 4102 to 4103; 4103 to 4102), make sure not to use a WHERE condition with the PAGENO column included for cluster tables (i.e. CDCLS, RFBLG, ). ?? The resulting *.WHR files will be written into subdirectory DATA of the specified export directory. Table splitting will take place if the specified export direct

ory is the same like for the R3LOAD export later on. The whr.txt file contains the name of the splitted tables. It can be used as an input file for the package sp litter to make sure that each splitted table has it own *.STR file. ?? It depends on the SAPINST release whether a database type can be selected or not . SAPINST 7.02 can make use of the Oracle PL/SQL splitter if the database type O racle was selected. Radio buttons allow to choose between the R3TA and the PL/SQ L table splitter. Before starting the import, R3LOAD compares the WHERE condition between the and *.TSK files. R3LOAD stops on error in case of a mismatch. *.TOC