Get Roadmap

1. After you have chosen to work without a stack configuration file and selected the option Benchmarking Tool, choose the benchmarking mode Benchmark export (discarding data) and click Next.
2. Dialog Migration Parameters
   1. Table Selection: Select if the migration benchmark shall relate to all tables, that is, to the whole database, or to selected tables only.

      • If you choose All tables, you can specify additionally whether the benchmarking shall be performed for the whole database or on a sampling basis. Enter for this a value from 1 to 100 in percentage, where 100% means the whole database.

        If you enter a lower value, the system determines internally the size of all tables, sorts them according to the size, and selects the tables based on a sequence until the given size of the database is reached.

        In addition, you specify in percentage the maximum size of the largest table in the sample based on the database size.

      • If you choose Selected tables, enter the name and the path of the txt-file that includes the table names. The txt-file contains each table in one line.

   2. Declustering during Migration: Activate the option Target database declustered, if you already know that the database will be declustered during the actual update and migration procedure, for example if you plan to update to SAP Kernel 7.40 or higher.

      This option allows you to receive the best possible simulation result.

   3. Migration Repetition Option: Activate the option Enable migration repetition option to stop the benchmarking tool after the downtime migration phase and to enable a simple repetition of the latter to optimize the procedure by adjusting the parameters (such as R3load processes).

      You must not use this option for a productive run. For more information, see Using the Migration Repetition Option for Testing.

Roadmap Step Configuration

3. Dialog Download Directory
   1. Download Directory: Specify the download directory that contains, for example, the required kernel files so that the Software Update Manager can update the kernel automatically.

      • Note that the folder for the duration files must be existing, but not filled.

      • You can skip this step when only customer transports are imported.

   2. Archive Verification: Activate the option Check the authenticity of SAP archives if you want to check the authenticity of all the archives in the download directory.

      For more information, see the chapter "Verifying SAP Archives" in section " Running the Software Update Manager" of the SUM guide.

4. Dialog Parameters for Procedure: Configure the number of parallel SQL and R3load processes.
5. Dialog Required System Passwords: Database-specific password. Provide the password of the user System of the source database.

   Moreover, the Software Update Manager can ask for the name and the password of the SAP HANA database security user. However, this dialog appears only if the database user SYSTEM is deactivated. In this case, the Software Update Manager asks for a security user that has the system privilege USER ADMIN. It uses this security user to activate the user SYSTEM if necessary. Then, the user SYSTEM is used for a short time and deactivated again afterwards.

Roadmap Step Execution

6. During the roadmap step Execution, the benchmarking is executed.

Roadmap Step Postprocessing

7. Dialog Benchmarking completed: The procedure is finished. Analyze the utility DMO Migration Post Analysis in the SUM Utilities.

   To access the SUM Utilities, open the More menu in the upper-right corner on the menu bar. For more information, see also SUM Utilities for DMO (Extended UI).

8. Fill in the evaluation form that SUM displays after the update and migration procedure is finished.
9. Optional: Save migration duration files for performance optimization, as described in chapter Performance Optimization with Migration Duration File.
10. Clean up the procedure at the end, so that you can the next time from the beginning.