Ensure that you consider mart size, model count, and associated versions while upgrading a mart from an earlier version to the latest version. The following table provides sample data of the upgrade process. You can use this information as a guideline.
|
Mart Database |
Machine Configuration |
Time Taken (Upgrade from lower version to erwin Mart 2021 R1 and above) |
|---|---|---|
|
Oracle 12c R2 (1221 Models , 42108498 million rows present M9Object Table) |
8 GB RAM 1 CPU |
50 minutes |
|
SQL Server 2017 (1277 Models, 44294824 million rows present in M9Object Table) |
8 GB RAM 1 CPU |
142 minutes |
|
Postgresql 9.6.15 (1020 Models, 33594468 million rows present in M9Object Table) |
16 GB RAM 4 CPUs |
15 minutes |
|
Oracle 12c R1 (10784 Models, 505178719 million rows present in M9Object Table) |
32 GB RAM AWS Machine |
15 hours |
|
Oracle 12c R1 (11980 Models, 520732699 million rows present in M9Object Table) |
32 GB RAM 4 CPU |
20 hours 40 minutes |
Following are a few tips to ensure a smooth upgrade:
- Before upgrading, ensure that you double the number of data files in tablespaces for MMDATA and MMINDEX in an Oracle mart.
- Check the Report Upgrade status in the MartServerUpgrade.log file.
- If the M9Object Table has high volume of data and models over 100 MB, run the upgrade on a machine that has 64 GB or more RAM.
- In case of failures in upgrade, before you rerun the upgrade, ensure that you select the following check boxes on the Advanced tab on the erwin Mart Configuration dialog:
- Rerun Count Upgrade
- Rerun Report Upgrade
- Rerun Report Upgrade For All Models
For more information, refer to the Configuring erwin Mart Portal topic.
|
Copyright © 2025 Quest Software, Inc. |