There is already an object named 'PLAN_' in the DB sync issues while upgrading a sandbox environment to 10.0.26 or or moving DB from tier1 to tier2

An issue occurred while upgrading a sandbox environment to 10.0.26 or upgrading from tier1 to tier2 we are getting DB sync issues in logs with the 'PLAN_' issue

Resolution:

1. Against the environment run the following script on AxDB

DECLARE @flightName NVARCHAR(100) = 'DbSyncGetSingleTableDefinitionAfterProperCheckKS';

IF NOT EXISTS (SELECT TOP 1 1 FROM SysFlighting WHERE flightName = @flightName)

     INSERT INTO SysFlighting (flightName, enabled, flightServiceId) VALUES (@flightName, 1, 12719367);

ELSE

     UPDATE SysFlighting SET enabled = 1, flightServiceId = 12719367 WHERE flightName = @flightName;