Preprocessing

In this roadmap step, SUM creates the shadow system.

The shadow system is then used for various update activities while you can still use the original system in production operation. The SUM builds up the shadow system by cloning parts of the original system. All tables of the SAP NetWeaver Application Server are needed as shadow tables to operate the shadow system.

The shadow system is used to perform the modification adjustment of the ABAP Dictionary objects and the activation of new ABAP Dictionary objects that are part of the update. Finally, the Software Update Manager performs the shadow import and writes directly into the shadow tables.

Modifications to the contents of the original tables are indicated by triggers. These tables are copied and imported during downtime.

The following actions are carried out:

Checks for locked objects
ABAP Workbench locking

Note

In contrast to the standard upgrade procedure, the Software Update Manager offers during the release upgrade with DMO a second phase LOCKEU_PRE to lock the ABAP Workbench. Thus, you can lock it either in phase LOCKEU_PRE or in phase REPACHK2, in which you have to perform the step at the latest.
If you confirm the lock already in phase LOCKEU_PRE, the Software Update Manager does not stop in the REPACHK2 phase to allow you to confirm the lock on the ABAP Workbench. This increases the time in which the Software Update Manager does not need user input after the last request for a mount directory.
Furthermore, you may not perform any more transports into or out of the SAP system.
Running the shadow system for preparation of new release (ACT_UPG, PARDIST, SGEN)
(and subsequent to the following DMO-specific actions:) Transition to the downtime (system isolation)

DMO-specific actions:

Uptime migration: Repository
Execution of SMIGR_CREATE_DDL
Execution of phases related to SAP Business Warehouse
In phase REQ_DB6_UPDATE_DB SUM, the Software Update Manager stops and prompts you to run the script db6_update_db on the target database IBM Db2 for Linux, Unix, and Windows (DB6) as instance owner.

Follow the instructions on the screen and execute the script with the option -dmo. The script performs necessary configurations that cannot be performed by the Software Update Manager.
Note

The execution of this script on the DB6 target database server is mandatory.

Further features:

Temporary database space, which is required for the shadow system and is calculated during the execution of the roadmap step Checks, is too generous.

You can use the command <SUM directory>/abap/bin/SAPup dmpspc to check the used space at different points of time.