A migration of SRM from 9.1 to 9.2 can fail with errors in the import_remote_reporting_data results.
Solution:
Parameters:
======================
MYSQL_ROOT_DIR: d:/win32app/Spectrum/mysql
MYSQL_EXEC_PATH: d:/win32app/Spectrum/mysql/bin/mysql
MYSQLDUMP_EXEC_PATH: d:/win32app/Spectrum/mysql/bin/mysqldump
SOURCE_DB_HOSTNAME: oneclick2
SOURCE_DB_PASSWORD: HIDDEN
LOCAL_DB_PASSWORD:HIDDEN
Beginning data migration process.
Creating 'reporting' database locally (if necessary)...
'reporting' database created successfully.
exporting reporting data from : oneclick2
source alarminfo table is already compatible with MySQL 5.0.
mysqldump of source data failed with status: 512
You may also see in the import_remote_reporting_data.results:
$retval = system("$MYSQLDUMP_EXEC_PATH -h$SOURCE_DB_HOSTNAME --opt
--routines --ignore-table=reporting.v_active_user_model
--ignore-table=reporting.v_alarm_activity
--ignore-table=reporting.v_ncm_config_diff
--ignore-table=reporting.v_security_string_accessibility_by_landscape
--ignore-table=reporting.v_user_report_security --compress -uroot
-p$SOURCE_DB_PASSWORD --databases reporting > $dump_log");
These error messages can be seen when there is already database corruption in the SRM database that needs to be addressed before attempting the migration.
The following mysql repair can be run before attempting the migration again:
mysqlcheck --auto-repair -A