ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
When using the Alternative SQL Schema, the MQCP tables are not properly created.
Article ID: 132402
CA Automic Workload Automation - Automation Engine
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.
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.
Release: Component: AAUTEN
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.