UTF-8 DB Migration Action Pack (V1.0.8) - SQL commands generated after final step

[Gerry_Grimm_9064]

Greetings,

My team is preparing to upgrade from V21.0.9 to V24.4. We are using an MSSQL database (2019) for Automic and the Alternative DB Scheme. We successfully ran the UTF-8 DB Migration Action Pack job objects in modes 0 (initial), 1 (refresh), and 2 (final), all on the same day. However, we encountered issues executing the SQL statements generated after the FINAL step. These errors pertain to the Alternative DB Scheme.

Has anyone encountered this type of issue?

[Jared Kessans]

We have also run into issues with the alternative schema on the MSSQL database, though I don't recall seeing that specific error.  

We have two errors that we encountered with the Step 1 of the finalization queries.  

Currently we are working on the process in a sandbox environment to test the process.  We received the below error and with assistance from the support team we ended up skipping the steps to turn on the IDENTITY_INSERT.

IDENTITY_INSERT is already ON for table 'UC4SANDBU.dbo.MQ1CP001_ucorig'. Cannot perform SET operation for table 'MQ2CP001_ucorig'.

We also had to modify the line below and its twin MQ1QWP table:

insert into [MQ2QWP] select * from UC4SANDB_MQ.dbo.[MQ2QWP];

to:

insert into [MQ2QWP] (MQQWP_PK, MQQWP_System, MQQWP_CAddr, MQQWP_CSRName, MQQWP_CAcv, MQQWP_BAddr, MQQWP_BSRName, MQQWP_BAcv, MQQWP_FAddr, MQQWP_LogAddr, MQQWP_PhysAddr, MQQWP_BTable, MQQWP_SchedTime, MQQWP_Status, MQQWP_Priority, MQQWP_DRole, MQQWP_LAddr, MQQWP_QState, MQQWP_Alarm, MQQWP_RetryCnt, MQQWP_MsgInfo, MQQWP_CrashInfo, MQQWP_SentAlarm, MQQWP_Len, MQQWP_Msg) 
   select MQQWP_PK, MQQWP_System, MQQWP_CAddr, MQQWP_CSRName, MQQWP_CAcv, MQQWP_BAddr, MQQWP_BSRName, MQQWP_BAcv, MQQWP_FAddr, MQQWP_LogAddr, MQQWP_PhysAddr, MQQWP_BTable, MQQWP_SchedTime, MQQWP_Status, MQQWP_Priority, MQQWP_DRole, MQQWP_LAddr, MQQWP_QState, MQQWP_Alarm, MQQWP_RetryCnt, MQQWP_MsgInfo, MQQWP_CrashInfo, MQQWP_SentAlarm, MQQWP_Len, MQQWP_Msg from UC4SANDB_MQ.dbo.[MQ2QWP];

While we ran into these errors, we pushed through them and so far the system is up and running.  Currently still have the case open with Broadcom and looking for a complete solution before we start it on the next environment as I currently do not have any confidence in the process yet.