After following the upgrade steps from the tech doc and applying the instructions for
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/11-1/release-notes/known-issues.html
Two MySQL Configuration Files Exist After Applying Gateway Application Patch
Issue: After installing the Gateway Application patch during in-place upgrade, two distinct MySQL configuration files are available instead of the expected single file. (DE595721)
Workaround: Should you identify variations in specific entries between the configuration files (my.cnf.ssg and my.cnf), carefully integrate them into a single file.
Mysql server fails to start
2025-05-27T07:03:30.227801Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2025-05-27T07:03:30.334246Z 1 [ERROR] [MY-012263] [InnoDB] The Auto-extending innodb_system data file './ibdata' is of a different size 6400 pages (rounded down to MB) than specified in the .cnf file: initial 655360 pages, max 2865600 (relevant if non-zero) pages!
2025-05-27T07:03:30.334297Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2025-05-27T07:03:30.834599Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
gateway 11.1
After the upgrade to 11.1.2, a new file named my.cnf.ssg is created, which includes the following setting:
innodb_data_file_path=ibdata:10240M:autoextend:max:44775M
Prior to the upgrade, the corresponding value in our original my.cnf file was set to for example:
innodb_data_file_path=ibdata:100M:autoextend:max:16657M
Do not merge this line from the my.cnf.ssg into the my.cnf .