Error during initial data load (DB Utilities) when using MS SQL Server

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Error Message :
U00003592 UCUDB - Status: '42000' Native error: '1757' Msg: 'Column 'UC_MSGT.MSGT_Type' is not of same collation as referencing column 'MSG.MSG_MSGT_Type' in foreign key 'FK_MSG_MSGT'.'

When using MS SQL Server for the Automation Engine (AE) and attempting to load the initial data using the DB Load Utilities, if the following error messages are seen in the logs (Logfile of the DB load utility) it indicates that the collation is not set correctly.  There is a different collation setting between the first initial data load and the following load which causes the error.

This error message appears during the initial data load.
 

20170316/093957.649 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 1419320  DB-HDBC: 18354ce0
20170316/093957.649 - U00003591 UCUDB - DB error info: OPC: 'SQLExecDirect' Return code: 'ERROR'
20170316/093957.649 - U00003592 UCUDB - Status: '42000' Native error: '1757' Msg: 'Column 'UC_MSGT.MSGT_Type' is not of same collation as referencing column 'MSG.MSG_MSGT_Type' in foreign key 'FK_MSG_MSGT'.'
20170316/093957.649 - U00003592 UCUDB - Status: '42000' Native error: '1750' Msg: 'Could not create constraint or index. See previous errors.'
20170316/093957.649 - U00003594 UCUDB Ret: '3590' opcode: 'EXEC' SQL Stmnt: '
...

Environment

OS Version: N/A

Cause

Cause type:
Configuration
Root Cause: Invalid collation setting on MS SQL Server.

Resolution

As this is not a defect or a faulty design in Automic's products and is caused within the scope and perimeter of the MS SQL Server product settings, the issue needs to be addressed by the MS SQL Server Database Administrator.

Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
N/A