Database Reference
In-Depth Information
Copying this dynamic link library to the SUM installation directory will help to avoid er-
rors during the R3load process later in the migration. When you have completed install-
ation and configuration of the HANA client, launch SUM for DMO in order to make the
HANA database client available to SUM.
6.1.9
BI housekeeping tasks
After the configuration phase of the DMO process has completed, SUM will move on to
the checks phase. As part of the checks phase, you will have the option to configure some
BI housekeeping tasks.
You can choose to delete bookmarks, traces, and statistical data older than a certain number
of days, which will decrease the overall volume of data in the migration and will require
less system downtime. Be careful when specifying which data you would like to delete, as
any data deleted during this part of the process cannot be restored.
You may also be notified of errors in the check process caused by inactive data structures.
In general, you can ignore these errors and continue with the DMO process as long as the
errors state that they CAN BE IGNORED FOR UPGRADE .
You may also receive an error message during this phase of the process if you have parti-
tioned data storage objects (DSOs) at the database level. In this case, the PSA may have a
large number of records which have been deleted logically from the PSA without having
been physically removed. If you encounter this problem, you can use the program found in
SAP Note 1299635 in transaction code SE38 to remove the orphaned records.
Transport requests
After configuring the BI housekeeping tasks as desired, make sure
you check table RSADMINA. In this table, confirm that BEX
REQUEST has been removed. You should also make sure that the
TPBWMANDTRFC field is populated. TPBWMANDTRFC is the
destination field for RFC calls, so this needs to be populated before
you can finish the checks phase of the SUM for DMO process.
Search WWH ::




Custom Search