Bypassing the email requirement for UTF-8 Migration workflow
Article ID: 380298
Updated On:
Products
Issue/Introduction
When scheduling the final phase of the migration workflow, the server needed the ability to send email in order to continue. Is there way to bypass the email step in favor of a text output?
Environment
AE: 12.3 or 21.X
Upgrading to: 24.X
Resolution
There is a way to bypass the email requirement. This is described in the documentation steps in the Migrating the AE DB to UTF-8 -> Recommendations -> Step 12:
Final: The Workflow finishes and sends an email to the defined address, provided that SMTP is correctly configured and works. This email contains the DB SQL statements of this last run. The DB SQL statements are also stored in the PCK.AUTOMIC_UTF-8.EMAIL.CONTENT.FINAL.STEPS VARA object that is provided in the SOURCE - MOVE.NON-UTF8.DB.TO.UTF8 - EMAIL folder in case sending the email is not possible for any reason.
Important! If the email cannot be sent successfully in this final step, and the corresponding task fails with an error status, you can ignore this task and resume the whole Workflow.
In the client where the migration workflow is run, you should be able to search for the object PCK.AUTOMIC_UTF-8.EMAIL.CONTENT.FINAL.STEPS and there will be a step 1 and perhaps a step 2. The statements here are sent in the email.
You should be able to open the lines in value 1:
and copy/paste those into something like SQL Server Management Studio (in the case of SQL Server database) to run them.
Feedback
