Starting the Migration Tool Dialog
To start the migtool mode of SUM, open a browser window and enter the following internet address in the address bar:
http://<hostname>:1128/lmsl/migtool/<SID>/doc/sluigui
Note:
Replace <SID> with the system-ID
1129 is the https-port of the SAP Host Agent
If the secure socket layer is not configured, use http instead of https:
http://<hostname>:1128/lmsl/migtool/<SID>/doc/sluigui
Use full Commands during SUM with DMO
Temporary database space, which is required for the shadow system and is calculated during the execution of the roadmap step Checks.
To check the used space at different points of time.
Use the command:
<SUM directory>/abap/bin/SAPup dmpspc
To change the number of R3load processes dynamically,
Use the following commands:
cd <SUM directory>/abap/bin
./SAPup set procpar gt=scroll
Performance Optimization with Migration Duration Files
During a migration, SUM creates text files with the extension XML that contain the information about the migration duration for each migrated table.
The files are created in directory SUM\abap\htdoc\ and are called
MIGRATE_UT_DUR.XML for the uptime migration
MIGRATE_DT_DUR.XML for the downtime migration
They can be used for the next DMO run to improve the table splitting. For this, put the files into the download folder so that SUM can consider the files during the next run.
Add to file SAPup_add.par the following line
/clonepar/clonedurations = <absolute_path>/MIGRATE_UT_DUR.LST,<absolute_path>/MIGRATE_DT_DUR.LST
Oracle: Suppressing Long-Running Phases
Update the database using the below command before starting the Update
brconnect -u / -c -f stats -o <schema_owner> -t all -f allsel,collect,space –p 83
Add to file SAPup_add.par the following line:
/ORA/update_spacestat = 0
The file SAPup_add.par is located in the directory <SUM directory>/abap/bin/. If it does not exist yet, create it manually.
Required Keys
Valid migration key for the new target database
Request the migration from the SAP Service Marketplace at https://support.sap.com/migrationkey
Permanent SAP license for your system that will be migrated to the target database
Download the license key from http://support.sap.com/licensekey
Use full log files
Benchmarking
Analyze the log file EUMIGRATERUN.LOG for benchmarking results
Row Store vs Column store
The table type in SAP HANA database (row store vs. column store) is controlled based on the file <SUM directory>/abap/bin/ROWSTORELIST.TXT. (Target Release SAP NW 7.31 only:)
Time estimation
Overall process and for long-running phases is written to the file
<SUM directory>/abap/log/SAPupStat.log
Changing Schema Name
After the extraction of SUM add the following line to the file SAPup_add.par
/migrate/targetschemasid = <VAL>;
<VAL> is the desired identifier to be appended to form the schema name SAP<VAL>.
Using the Migration Repetition Option for Testing
If you have enabled the Migration Repetition option, this dialog displays an additional warning that the SUM will stop after the downtime migration phase and allows you to repeat the phase. Be aware that you must not use this option for a productive run.
if you want to disable the option now, set the following parameter in the file SUM\abap\bin\SAPup_add.par:
/migrate_option/OPTIMIZECLONING = 0
Downloading Files from Maintenance Optimizer
When you select the kernel files using MOpz, consider that you have to select the kernel files of the target software release for both the source database and the target database. The reason is that the system creates the shadow instance for the target software release on the existing source database first and then copies it to the target database.
Upload the following files to a folder on the Primary Application Server (PAS)
The files calculated by MOpz including kernel for the source and target database
stack.xml file
Target database client for the required operating system
SAPCryptoLib (if encryption is used in the source system)
Reset Option
Prerequisites
To carry out the reset, it is required that
anyDB is still available
the SUM directory is not cleaned up
Limitations
Target database client is not deleted from PAS/AAS automatically
BR tools are not restored
User DBACOCKPIT and related roles are not deleted in target database
No Reset possible after Cleanup
After the update and migration procedure comes to an end, the Software Update Managers offers in addition the option Cleanup. Be aware that after a cleanup, a reset is not possible anymore.
Required Migration Specific Passwords
User SYSTEM
User DBACOCKPIT (only if it does not yet exist on the target database and SUM has to create it)
User SAP<SID> (SUM will create it on the target database)
Retired Parameters for SAPup_add.par file
/clonepar/imp/procenv = HDB_MASSIMPORT=YES(default values for current R3load Versions SAP Note 21181195)
/clonepar/indexcreation = after_load(default values for current R3load Versions SAP Note 21181195)