Roadmap Steps with Downtime-Optimized Conversion Features
This part of the guide provides information about the update and conversion procedure using Software Update Manager.
In the following, we describe the main steps and phases of the downtime-optimized conversion procedure. The first section deals with the downtime-optimized conversion for source systems running on a database that is not SAP HANA.
The subsequent section regards the downtime-optimized conversion for source systems that run on an SAP HANA database.
Downtime-Optimized Conversion for Source Systemss on non-HANA Database
-
You start the downtime-optimized conversion procedure in the Software Update Manager.
-
At the beginning of the Preprocessing roadmap step, the shadow repository is created.
-
Asset accounting lock to obtain a transactional consistent state of Asset Accounting before cloning.
-
Initial transfer of tables starts.
-
Revert transfer to revert snapshot triggers.
-
Conversion of relevant tables starts.
-
Delta migration of relevant tables.
-
In the Execution roadmap step, the remaining delta of relevant tables is migrated.
-
Conversion of remaining delta of relevant tables.
-
Migration of remaining tables.
-
Final activities of the downtime phase such as kernel switch and remaining update.
Downtime-Optimized Conversion for Source Systems on SAP HANA Database
A. You start the downtime-optimized conversion procedure in the Software Update Manager.
B. At the beginning of the Preprocessing roadmap step, the shadow repository is created.
C. Asset Accounting lock to obtain a transactional consistent state of Asset Accounting before cloning.
D. Copy tables to shadow.
E. Revert transfer to revert snapshot triggers.
F. Conversion of relevant tables starts.
G. Delta transfer of relevant tables.
H. In the Execution roadmap step, the final delta transfer is performed.
I. Conversion of remaining delta of relevant tables.
J. Final activities of the downtime phase such as kernel switch and remaining update
