Upgraded gateway from 9.1 to 9.2 - failed to start

book

Article ID: 129925

calendar_today

Updated On:

Products

STARTER PACK-7 CA Rapid App Security CA API Gateway

Issue/Introduction

Upgraded gateway from 9.1 to 9.2 - failed to start

We tried to upgrade it from ssgmenu but we got the below error.

Function SP_Change_master does not exist”

SSG Log:
**** Unable to start the server: The version mismatch between the database (version 9.1.00) and Gateway (version 9.2.00) is too great.The database version must be within two major versions of the Gateway and cannot be lower.To resolve, either upgrade the database or the Gateway.

 

Cause

The function outlined sp_change_master is not a known stored procedure look in the /opt/SecureSpan/Gateway/config/etc/sql/ change files, or reviewing a standard build of our gateway. 

Update of the SSG database failed because of custom stored procedures.  Custom stored procedure need to be backup, deleted, then restored after ssg database is updated 

 

Environment

Gateway 9.2

Resolution

All custom store and procedure need to be backed up, then deleted before you update the ssg database

sp_change_master
sp_create _database
sp_drop_database
sp_show_databases
sp_show_master_status
sp_show_slave_status
sp_show_vars
sp_start_slave
sp_stop_slave

Enter the following commands for each custom SP:
mysql> delete from mysql.proc where name='sp_change_master'; 
mysql> delete from mysql.proc where name='sp_drop_database';
.
.
.

Additional Information

To take backup of only Stored Procedures and Triggers (Exclude table and data ) use the following command.
# mysqldump --routines --no-create-info --no-data --no-create-db --skip-opt ssg > ssg.sql

To restore stored procedures in the database simply use the following command, But make sure you have taken backup properly before restoring it to avoid any data loss.
# mysql -u root -p ssg < ssg.sql