MSSQL UTF-8 Migration pack fails if db name starts with integer
search cancel

MSSQL UTF-8 Migration pack fails if db name starts with integer

book

Article ID: 392694

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

The UTF8 Migration pack fails against Microsoft SQL Server Database (MSSQL) if the database name starts with an integer, for example if the database name is 21AUTOMIC.  The PCK.AUTOMIC_UTF-8.MIG-STEP05.COPY.INIT.DATA.NOILM.DST will show something like:

U02012014 JDBC Driver Version: {version number}
             update 21AUTOMIC.dbo.uc_migration set transfered='Y' where mig_run=1 and transfered='N'
             Incorrect syntax near '21'.

Environment

UTF8 Migration Pack 1.0.6 and lower

Resolution

This is defect that is planned to be fixed in a future release of the Migration workflow.