Requirements for migrating the MES database to the current release

Make a backup of the existing database prior to upgrading it in case any issues occur during the upgrade process.

Make sure that you have enough disk space available on your computer before you start to migrate the MES database to the latest version. The amount of disk space should be at least equal to the size of your MES database or 30 GB, whichever amount is larger. Also, in the case of large databases, reduce the size of the database and the transaction log file before you perform the upgrade. Then reduce the size of the transaction log after the upgrade is complete.

If the existing MES database has custom indices and keys that reference core MES tables, they must be dropped before migrating the database to the current release. If they are not dropped, the database migration will fail. They can be added back after the migration is complete.

Migration of MES databases from version 4.0 and later is supported. If you are migrating from versions earlier than version 4.0, it is recommended to first migrate the database to version 4.0.

Another option is to record the contents of the Factelligence.cfg file prior to the upgrade and then use that information to configure the new database in the post-install Configurator application (the database connection information will not be automatically populated in Configurator). You can see the settings to record by running the MES Database Connection String Editor on the old MES version.

Custom modifications to any version of the MES database might not be supported by the post‑install Configurator and might prevent migration. For more information on migrating an existing MES database, see the procedure in Update an existing MES database.

If you are migrating an MES database from version 5.3 or earlier, the migration of the utilization table structure to the new structure can take a long time. A rough estimate is provided prior to migrating it. As a precaution, all the original data remains in the database in tables labeled tablename_deprecated. Once you are satisfied that the migration was successful, these tables can be deleted.

Shut down all MES middleware and close all database connections against the MES database, including any scripts running against the MES database. Verify whether existing connections are active using the Operations Control Management Console (OCMC) Log Viewer.

If you are migrating an MES Cloud integration install, the MES-hybrid tables from the MES Cloud integration staging database are migrated to the corresponding tables in the MES database. During migration, the metadata table settings are cleared as well as the frequency settings from the type_config table as the curation is changed to on-demand to limit latency. The original <MESDB>_Staging_database remains and may be manually deleted once migration is successful.

Note: Use the Events to CONNECT agent in History Only mode to populate historical data from the MES database to CONNECT. This works with the On-Demand (default) configuration of the MES Curation service. For more information, see Configure the data ingress history recovery settings.