Database Reference
In-Depth Information
6.2
Post-migration tasks
Now that you have finished the DMO process in SUM, you still have some work to do be-
fore the system is ready for use. The essential steps that you need to perform after the mi-
gration are included in this section.
Keep reading!
Please be aware that this section is not intended to be a comprehens-
ive list of every post-migration task that must be completed. While
every effort has been made to provide a comprehensive explanation of
the post-migration tasks, there are simply too many steps to allow an
in-depth analysis of every step. The complete DMO task list is con-
tained in
Section 6.3
, so use the detailed list provided in that section as the basis for a
comprehensive list of tasks that are necessary in a DMO migration.
6.2.1
Installation check
After completing the DMO process, use transaction code SICK to run a database consistency
check on the SAP BW on HANA database. The consistency check will determine whether
the SAP kernel matches the version specified in the database. SICK is also used to determine
whether the character set specified in the kernel matches the character set in the database.
Finally, SICK will check whether the SYST, T100, TSTC, TDCT and TFDIR structures in
the Data Dictionary match those that are defined in the kernel.
6.2.2
Memory management
SAP kernel 7.40 made some essential changes in memory management within the SAP sys-
tem. First, Zero Administration Memory Management now uses formulas to derive paramet-
ers for memory management from a calculation based on the physical RAM in a system.
Prior to kernel 7.40, this feature was only available in BW servers on the Windows platform,
but support for UNIX and Linux were added to the latest kernel.
