When using the Alternative SQL Schema, the MQCP tables are not properly created.

book

Article ID: 132402

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

When attempting an install utilizing the Alternative SQL Schema, the MQCP tables are not properly created. This can cause either the tables to not be created entirely, or the indexes on the newly created tables to be corrupted.

Cause

This was coused by a potential issue in a substring routine within the mqdb_sql.ddl. Additionally, the prmary key was created without the nonclustered keyword, which had the potential to cause unexpected behavior.

Environment

Release:
Component: AAUTEN

Resolution

The issue was found and fixed with:

Automation.Engine 12.1.5 in Initialdata, Utility released 05-20-2019
Automation.Engine 12.2.3 in Initialdata, Utility pending release

Hotfix-Description: Alternative SQL Schema is created on MSSQL with wrong indexes

A problem has been fixed where the Alternative SQL Schema was created on MSSQL with wrong indexes. The primary key was created without the Nonclustered keyword for the MQ Database.