Gateway v 11.1 upgrade - DB update issue

Products

• CA API Gateway

Issue/Introduction

The following error occurs when we upgrade from v. 10.1 to 11.1. The prerequisites with respect to the MySQL external DB from here:

Connect the Container GW to an Existing MySQL Database

The gateways are not booting up and we see this error:

---
2024-05-21T14:39:02.754841322Z ##  Get certified courses at learn.liquibase.com  ## 
2024-05-21T14:39:02.754845254Z ##  Free schema change activity reports at        ##
2024-05-21T14:39:02.754849595Z ##      https://hub.liquibase.com                 ##
2024-05-21T14:39:02.754859554Z ##                                                ##
2024-05-21T14:39:02.754864041Z ####################################################
2024-05-21T14:39:02.754868364Z Starting Liquibase at 14:39:02 (version 4.5.0 #52 built at 2021-09-27 16:19+0000)
2024-05-21T14:39:14.192387572Z Unexpected error running Liquibase: Migration failed for change set ssg-base.xml::add_pk_ID_AUTHOR_FILENAME::gateway:
2024-05-21T14:39:14.192412294Z      Reason: liquibase.exception.DatabaseException: Multiple primary key defined [Failed SQL: (1068) ALTER TABLE ssg.DATABASECHANGELOG ADD PRIMARY KEY (ID, AUTHOR, FILENAME)]
2024-05-21T14:39:14.192419916Z For more information, please use the --logLevel flag
2024-05-21T14:39:14.211127591Z ERROR - Failed to create or update the Gateway's database

Environment

Release: 10.1, 11.1

Resolution

- When creating or importing backups of installations where GIPKs are in use, it is possible to exclude/skip the generated invisible primary key columns and values.

- The --skip-generated-invisible-primary-key option for mysqldump causes GIPK information to be excluded in the program's output.

- If you are importing a mysqldump file that contains generated invisible primary keys and values, you can also use --skip-generated-invisible-primary-key with mysqlpump to make them to be suppressed (and thus not imported).