Database Migration Option: Target Database SAP ASE

Table Comparison

This section covers the built-in Table Comparison tool.

After the migration of tables in both the uptime and the downtime, SUM compares with the function Table Comparison with SUM based on calculated checksums the content of target database tables with the table contents on the source database. In a dialog in roadmap step Extraction, SUM offers the following options:

  • Do not compare table contents

  • Compare the content of all tables

  • Compare only the content of selected tables

The last option offers the possibility to check and compare the table contents of certain tables only. If you choose this option, you are prompted afterwards to enter the location of the file that includes the table names to be checked.

The comparison of the tables run in parallel processes. The number of the processes is defined by the number of R3load processes that you set in the configuration dialog in phase PREP_CONFIGURATION/INITSUBST.

The function Table Comparison with SUM calculates after the migration the checksum for an entire table on both the target database and the source database and compares the values. If the values are not equal, SUM displays an error message depending on uptime or downtime

  • either in the Preprocessing roadmap step in phase MAIN_SHDIMP/SUBMOD_MIG_UPTIME_RUN/EU_CLONE_MIG_UT_CRC_RUN

  • or during the Execution roadmap step in phase MAIN_SWITCH/SUBMOD_MIG_SWITCH/EU_CLONE_MIG_DT_CRC_RUN

In parallel, the system generates an LST-file, which informs you about the affected tables, the possible fixing or ignoring options and their consequences during the Repeat phase. The location of the file is displayed in the dialog, which accompanies the error message.

In case of errors, SUM offers you the following options:

  1. Exit the program.

  2. Fix the errors in the affected tables on the target database. You can fix

    • all errors

    • the severe errors only and accept the non-severe errors

    Afterwards, you repeat the phase so that the table comparison runs again and the phase continues at the point it stopped.

  3. Fix the errors in the affected tables on the source database. Afterwards, you initialize the phase to restart it from the beginning. The tables will be migrated and checked again.