Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
SQL disk space requirements prevented the upgrade due to the upgrade process wanting double the history DB size as free space. We had provisioned to have enough space for the DB to be duplicated:
Current history DB = 190GB Space made available = 210GB
Update failed because the upgrade process is asking for almost 400GB free space.
해결 방안
The reason why 2x size of disk space is required while importing MH DB(Management History database) is because the upgrade process creates temporary tables while Active Roles performs import operations, this itself requires almost the size of the source MH DB then destination MH DB will increase to almost the size of the source DB post completion of operations. So 2x of space of source DB is required.
Temporary tables are created to process and identify records to be migrated to destination DB. Temporary tables will be deleted post import of MH DB operations.