Updating SAP ABAP Systems on UNIX and Linux: SAP MaxDB

Making Entries for Scenarios Without Configuration File

This section is relevant when you have specified a scenario category without stack.xml configuration file.

Context

If you opt to use no configuration file, a dialog with a list of possible scenarios appears. Select one option from the list.

Depending on your selection, further dialogs may appear, or the current dialog is enhanced to maintain further parameters and values.

Procedure

  1. Select the scenario to start
    The following options are available:

    • DMO without System Update

      Relevant for DMO with target database SAP HANA: You can run a DMO procedure for migration purpose only without updating the SAP system.

    • Customer Transport Integration only

      You want to import your customer transport requests only without performing a standard update procedure. See also Integration of Customer Transports.

      Note that DMO with Customer Transport Integration is only supported for target database SAP HANA.

    • Benchmarking Tool

      Relevant for DMO: With this migration tool, you can simulate the export and import processes or the export process only to estimate their speed.

    • Check Cluster Data

      You want to check the consistency of all pooled tables or cluster tables in the system. See Checking Cluster Data for more information.

    • Table Comparison Check Tool

      With this stand-alone migration tool, you can compare export and import table checksums for your database. The check can, for example, be relevant for the system copy procedure with the Software Provisioning Manager.

  2. Specify the Scenario Strategy and Additional Parameters
    If you selected in the dialog for selecting the start scenario the option

    • Customer Transport Integration only or

    • DMO without System Update

    a dialog appears in which you can specify the scenario strategy. The following options are available:

    • Standard (standard configuration)

      This option is the standard configuration for the most scenarios.

    • Downtime-optimized (high configuration)

      Here, you can choose a further option:
      Scenario Additional Option Use
      DMO without System Update Uptime Migration (downtime-optimized DMO) If you want to migrate selected large application tables partly in uptime.
      Customer Transport Integration only Near-Zero Downtime Maintenance (nZDM) If you want to move table structure adaptations and import of new table content partly to uptime processing for a system update or upgrade.

    For more information on the scenario strategy options, see Initial Dialogs for the Scenario Specification (Get Roadmap) and Making Entries for Scenarios with Configuration File.

    Afterwards, more dialogs appear, where you can first switch on the expert mode. Then you enter the required system passwords, after that you can specify the download directory and switch on the archive verification.

    In case of DMO without System Update, the dialog about the migration parameters appears in addition. In the following, you find more information about it.

  3. Configure the Tools
    If you selected in the dialog for selecting the start scenario one of the options

    • Benchmarking Tool or

    • Check Cluster Data

    • Table Comparison Check Tool

    the initial dialog is enhanced to select the wanted option for the execution of the tools. Afterwards, further dialogs appear as described in the DMO Guide.
  4. Decide on Migration Parameters
    You can

    • decide on the table selection, if you want to perform a table comparison

    • enter the migration key, if necessary

    • enable the migration repetition option for testing purposes

    Note that this dialog does not appear if you have selected Customer Transport Integration only.