Details:
SAP OS/DB Migration - II
Solution:
Different System Copy Methods
SAP System Copy or Migration Tools for ABAP
SAPINST:
SAP system installer controlling the system copy process.
R3LDCTL:
Create database independent table and index structure files (*.STR).
Create view structure file (SAPVIEW.STR).
Create database specific DDL command tempelate (DDL<DBS>.TPL or DDL<DBS>_LRG.TPL).
R3SZCHK:
Computes the size of ABAP tables/indexes and stores them in extent file (*.EXT).
Limit Calulation of object extent size to 1700 MB.
Create target database size file (DBSIZE.XML)
R3LOAD:
Unloads or loads ABAP table data from or into the DB.
Write platform independent data dump format.
Supports table splitting.
Character set conversion to unicode are implemented in R3LOAD.
Control the restart of object if R3load fails by using task file (*.TSK).
SMIGR_CREATE_DDL (ABAP Report):
Generates DB-specific DDL statements for nonstandard DB objects of the ABAP Dictionary, mainly SAP Business Warehouse (BW) objects.
Generate <TABART>.SQL files
RS_BW_POST_MIGRATION (ABAP Report):
Posts system copy activities for nonstandard DB objects in the ABAP Dictionary.
Mandatory for all SAP BW and SAP SCM systems.
MIGMON:
Migration Monitor is a tool provided by SAP for managing and monitoring the migration process during an SAP system migration. It is designed to assist in executing, controlling, and tracking the various steps involved in a system migration.
No comments:
Post a Comment