Symptom
-
It is not possible to change the partitioning information for the table on the source DB so that the partitioning information can be used during the migration process.
-
During a heterogeneous system copy from Oracle to SAP HANA a default partitioning is applied to large tables that meet certain size conditions. The default partitioning - HASH N on the semantic key of the table is not optimal and does not match the recommendation provided by SAP for the tables in question.
-
Re-partitioning the tables from the default setting to the SAP recommended partitioning on the target HANA system after the migration is very time consuming.
Read more...
Environment
SAP HANA Database.
Product
SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0
Keywords
R3Load; software provisioning manager; SWPM; SQL files; DFACT.SQL; SMIGR_CREATE_DDL; Database Migration Option; software update manager; DMO; SUM; uptime; downtime; Preprocessing;, KBA , HAN-DB , SAP HANA Database , BC-UPG-TLS-TLA , Upgrade tools for ABAP , BC-INS-MIG-TLA , R3load, R3ldctl, R3szchk , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.