Final step V24 UTF8 Migration workflow SQL statements take hours

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

The "Final" step of the UTF8 migration workflow, running SQL statements manually, takes hours when it's expected to be shorter.

Environment

Source AE version: 21.0.x or earlier

Resolution

After the initial and refresh runs of the workflow, check the uc_migration table on the source database to see what the end_time and ah_idnr_end are.  Compare these with the highest ah_idnr in the source database ah table.  If there is a large gap between these, additional investigations will be needed.

If there is a large gap between the highest ah_idnr_end in the uc_migration table and the highest ah_idnr in the ah table, it could be that there are too many items "active" in Process Monitoring still.  There were older versions of Automic that kept EH data even when a client was deleted, so it may be necessary to check for that.  The following example SQL will give information on what the oldest EH entries are:

select min(eh_aH_idnr), eh_client from eh group by eh_client
select min(eh_rdate), eh_client from eh group by eh_client

If the eh_client shows up as something that is actively used and there is still a large gap between it and the max ah_idnr in ah, then it may be necessary (and is highly encouraged) to deactivate some objects from Process Monitoring in those clients.

Another way to speed up the migration in general is to ensure that your database maintenance - archive (if necessary), reorg, and unload utilities should be run regularly to keep A* and R* tables smaller.