Conversion to SAP S/4HANA using SUM: ABAP Systems on UNIX and Linux

Database-Specific Aspects

In the following, the most important database-specific aspects are described that might have an impact on your overall planning.

Database Archiving and Backup

If you chose to deactivate the archiving option at the beginning of roadmap step Execution, the Software Update Manager switches the database log mode to OVERWRITE. However, you must first confirm that a complete backup (data and configuration files) has been created successfully.

After the mode has been switched, the contents of the log are lost permanently. You are then able to recover the database to the state it has at this point in time.

Perform a complete backup after the update. How you back up the database depends on whether archiving was switched on or off.

For further information, see in the section A.4 Administration of the SUM Guide the chapter Changing the SAP HANA DB Database Recovery Mode.

Partitioning

Before the conversion, the partitioning for existing tables is kept as it is. New tables (such as table ACDOCA) are created during the uptime of the conversion procedure.

You can use the SAP HANA database utilities to partition these new tables. The Software Update Manager stops for it in a dialog during the downtime, that is, when the Preprocessing roadmap step is finished and before you choose Next to proceed the procedure.

For details on how to change the partitioning on HANA directly, see the SAP HANA Administration Guide for your SAP HANA platform (core) on the SAP Help Portal at:http://help.sap.com/hana_platform, Start of the navigation pathSystem Administration  Next navigation step  SAP HANA Administration Guide  Next navigation step  Partitioning OperationsEnd of the navigation path.