This action might not be possible to undo. Are you sure you want to continue?
This document lists several methods that can be used to optimize the standard system copy procedure. • • • • • • • Database Tuning Sorted vs. Unsorted Unload Package Splitting Table Splitting R3load Options Migration Monitor Defining Unload/Load Order
This is just a list of database parameters which could help you to tune the database. This list is not meant to give you detailed recommendations about the parameter settings!
DATABASE TUNING MEASURES - DB2/OS390:
• Create indexes deferred
DATABASE TUNING MEASURES - DB2 UDB FOR UNIX, WINDOWS
• SAP Note 454173 (R3load migration accelerated through CLI LOAD API)
DATABASE TUNING MEASURES - INFORMIX:
• Usage of PDQPRIORITY
DATABASE TUNING MEASURES - ORACLE:
• Links to information about tuning measures on external pages: o Oracle Tips on Quest Pipelines Homepage o Oracle Tips on Database Specialists Homepage o Oracle Newsletter on Quest Pipelines Homepage SAP Note 936441 (Oracle settings for R3load based system copy) Enlarge number and size of redo logs experiences from other pilot projects: add 4 additional redo logs of 100 MB each Enlarge number of db writers Enlarge temporary tablespace PSAPTEMP (~20-30 GB) Increase sort_area_size or use pga_* parameters Increase PSAPROLL (~20 GB)
• • • • • •
DATABASE TUNING MEASURES - SAP DB / MAXDB
• General documentation about tuning measures of MaxDB version 7.5: MaxDB Performance
The default setting is sorted. splitting the files manually. this script is replaced by a Java-based. Add the unused main memory of non-running Application Server components to the database cache. As of SAP NetWeaver 2004 SR1. the data export can be done sorted or unsorted. PSAPTEMP) DISADVANTAGES: • • • • • Import (index creation) is slower Data is created more distributed/less reorganized in the database STR files have to be splitted in a certain way (special STR files for unsorted unload/load) No improvements for database performance May influence the behaviour of (badly written) customer programs RECOMMENDATION: Although there is one big advantage when you export the data unsorted – if possible – you have to consider the disadvantages as well.com/swdc Download Support Packages and Patches Entry by Application 2 . see SAP Note 954268. PACKAGE SPLITTING The package splitting option is available and integrated into the system copy tools R3SETUP and SAPinst since SAP R/3 4. The consultant should discuss the pros and cons together with the customer and should only unload unsorted if the runtime of a sorted unload exceeds the downtime limits of the project. Increase the parameter MAXCPU to the maximum available number of processors to which the database system can distribute user tasks. For more information about influencing factors and about how to use an unsorted export earlier than NW 2007.SAR can be downloaded from SAP Service Marketplace at http://service. depends on several factors. Therefore we prefer to offer the unsorted export option only to experienced consultants. unload as few tables as possible unsorted. If the unsorted unload is used in a way different from this description. The Java-based tool can be used with the older releases as well.User's Guide which is part of the tool archive. code page conversion. For more information.PL.• Increase the parameter CACHE_SIZE to the maximum available size of main memory.0B SR1. If a table can be exported unsorted.sap. The splitting was done by a Perl script called SPLITSTR. much more powerful tool. If the export can be done without sorting the table data before exporting them depends on a lot of factors: ADVANTAGES: • • Export is faster No necessity to extremly enlarge tablespace for sorting (for example. then the consultant takes over the responsibility for supporting the resulting problems. • UNSORTED UNLOAD During a system copy. In general. see the Package Splitter . The archive SPLIT. like target database. table type.
.Group Additional Components SYSTEM COPY TOOLS SYSTEM COPY TOOLS <release> SYSTEM COPY TOOLS <release> #OS independent SPLIT_<ID>. The export and import of one table can be performed in parallel by starting several R3load processes to work on some packages in parallel. • ATTENTION: • • 3 . you cannot claim for support or an immediate fix of the problem. you therefore have to delete all data from this table and reload them all again! It may happen that the R3ta cores when processing a table. ADVANTAGES: • Large tables are processed in many small packages. we welcome any feedback which helps us to improve the tools. but if you run into problems. table locking.) • KNOWN PROBLEMS: • The sorting order may be different on non-Unicode source system and Unicode target system. If the export or import of a table aborts with an error. Depending on the database. As the usage of WHERE conditions requires a lot of experience and many manual steps and because there are still some problems not yet solved. The reason is still under investigation and there is no solution yet.. Under certain conditions it is recommended to create additional temporary indexes on the column used in the WHERE condition. only the processing of the package with the error has to be repeated instead of (un)loading the complete table once again. Using WHERE conditions may not be optimal for every database management system and therefore has to be considered carefully. the tool R3ta has been developed to automatically generate WHERE conditions.. You may use the feature ‘WHERE conditions’ and the tool R3ta and in many cases it will work without problems. we cannot release this feature generally. with which a subset of table data can be accessed. this may not be feasible during productive operation (time consuming. • DISADVANTAGES: • • If the parallel processing is not optimal or if the single packages are processed serial. Nevertheless. If the import of one package aborted with an error. AVAILABILITY: Table splitting can be used for ABAP systems with SAP kernel 6. These WHERE conditions are integrated into the R3load TSK files. The creation and evaluation of WHERE conditions is an iterating process which requires some experience and some detailed database knowledge. TABLE SPLITTING For copying large tables. Many manual steps have to be performed. the complete processing time for one table may increase when using WHERE conditions.SAR.40 or above. This may lead to problems when deleting parts of table data during restart.
In addition. CAUTION: This may not be possible on databases that need exclusive access on the table when creating an index (for example. If the ‘WHERE conditions’ are used in a way different from this description. run the tool again with different row-count parameters. you must be aware of the fact.• • • The generated WHERE conditions should not cover more than one column. 4 . If you decide to create WHERE conditions manually (without the R3ta tool). then the consultant takes over the responsibility for supporting the resulting problems. Informix). the consultant takes over the responsibility for the completeness of the data! You can often reduce the export time of a table which is processed with WHERE conditions if you create a (temporary) additional index on the column used within the WHERE condition. If R3ta calculated conditions with more columns. that a badly chosen WHERE condition can increase the total table processing time a lot.
The Migration Monitor has a property orderBy to specify the order of processing packages.sap. DEFINING UNLOAD/LOAD ORDER R3SETUP will process the packages according to the modification date of the STR files. the Migration Monitor is integrated into the SAPinst system copy tool.40 for .SAR can be downloaded from SAP Service Marketplace at http://service.Oracle Direct Path Load Support in R3load) R3load socket option: You can use the socket option. only for import). • In custom order. if your R3load has at least patch level 73 (compile date: 12. then move the STR files from the <export dump>/DATA directory to a different one and copy them back to the DATA directory in the order they should be processed. SAPinst presents a dialog on which you can choose how to process the packages: • In alphabetical order. but it is also possible to use the monitor for copying older releases by starting it manually. see SAP Note 784118 (System Copy Java Tools) and the Migration Monitor User's Guide which is part of the tool archive.R3LOAD OPTIONS R3load option '-fast' (<= 4.Oracle (see SAP Note 1045847 . • According to their size (largest first. The Migration Monitor will: • Create R3load command files • Create R3load task files if required • Start the R3load processes to unload the data • Transfer packages from the source to the target host if required • Start the R3load processes to load the data as soon as a package is available • Inform the person performing the system copy in case of errors For more information. If you have certain requirements regarding the export and/or import. As of SAP NetWeaver 2004 SR1.MSSQL • from SAP kernel release 6. 5 .0B for . The archive MIGMON.2008) MIGRATION MONITOR The Migration Monitor is a tool which helps you to perform and control the unload and load process during the system copy procedure.SAR.01.DB2/UDB .com/swdc Download Support Packages and Patches Entry by Application Group Additional Components SYSTEM COPY TOOLS SYSTEM COPY TOOLS <release> SYSTEM COPY TOOLS <release> #OS independent MIGMON_<ID>.DB2/UDB .MSSQL .6D) or '-loadprocedure fast': These options are available • from SAP kernel release 4.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.