Hope every SAP basis consultants / users do well. May i’m still beginner in SAP Basis world, but i think it is very good to share our knowledge between us. Note: if you get bored of reading long articles, kindly forgive me. One of my big issue i faced in our SAP system in copy clients, some tables not completely copied. SAP BASIS This one is for ECC 6.0 on SQL 2005 in Windows Server 2003 This document describes how to perform a homogeneous system copy of an MS SQL Server database by using the backup/restore method, or the detach/attach method in an SAP environment. The SAPinst installation tool supports both methods. Stop the target SAP system with the SAP Management Console 3. Make a copy of all the files in the QAS SYS profile directory 4. Create a new backup of the source SAP system database 5. Restore the target SAP system database from the backup created in step 4. Depending on database size this can take several minutes or several hours. SAP Basis - Copy Client on Remote System Watch More Videos at: Lecture By: Mr. Sumit Agarwal, Tutoria. Step by Step procedure to take System copy in SAP system. I am going to take SAP ERP 6.0 EHP5 System follow the below steps. Choose System Copy - Source System Export - Database instance Export.
1. What takes place during a homogeneous system copy?
2. What takes place during a heterogeneous system copy (migration)?
- Preparation steps on the source system
- Export of the source system data into database-independent format
- Transfer of the exported files to the target host
- New system installation together with data import
- Post-processing steps within the target system
3. Which tools are used during a migration on source and target systems?
4. What is the purpose of the files that are used during a migration?
- DDL<db_type>.TPL is used for creation of table/index definition in database-specific syntax and contains negative list of tables, views and indexes, assignment of TABARTs to storeage unit and next extent size of table/index. TABART stands for a data class. For more information, see SAP Note 46272 (SMP login required).
- SAP<TABART<.STR contain table/index definitions from the ABAP Dictionary.
- SAP<TABART.CMD contain definitions of path and names for corresponding STR, TOC, EXT files,DDL<db_type>.TPL, export directory, block and file sizes.
- SAP<TABART>.<nnn> (<nnn> = 001, 002, ...), so called dump files, contain the data of all tables of a tabart in a non-platform-specific file format. These are binary files and they should never been changed/edited!
- SAP<TABART>.EXT contain initial sizes for tables and indexes. Not applicable to some databases (such as for Microsoft SQL Server).
- SAP<TABART>.TOC contain position of table data within the corresponded dump file, name of the dump file, time stamp of unload, and table rows number. TOC files must never be changed without approval of SAP support.
- SAP<TABART>.log contain log file information in case of errors and for restarting.
- SAP<TABART>.TSK are files used by R3load - for more information, see SAP Note 455195 (SMP login required).
5. What interdependencies to kernel versions have to be considered?
- Tools used at the export on the source system must have the same version as on the target system.
- Tools used must all have the same kernel version (do not mix up kernel tools of different releases, as otherwise, different versions of the called programs - such as R3load - might be used for export and import).
- Tools must have the same kernel release as the system that is migrated.