The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-15. For the latest, interactive version please visit https://mariadb.com/kb/.

Unable to upgrade from 10.1.x to 10.3.x with Out place migration

Out-of-place migration: Out-of-place migration refers to migration to a new release of AMS on a server which is different from the server where the earlier AMS release is installed.

1 The new release of the AMS is installed and activated on a new server. 2 Data files of the earlier AMS release are saved to a backup file. 3. This backup file is transferred from the server of the earlier AMS release to the server containing the current active release. 4 The data from the backup file is then copied to the current active release directory.

Console log:

[amssys@host-11-1-0-69 ]$ ams_copy_datafiles Data files already exist for the active AMS release. Do you want to overwrite the existing data files [yes | no (default)]? yes

Enter the absolute filename of the AMS backup file: /backupDB/db_temp4_donothing.tar

Do you want to proceed: [yes | no (default)]? yes Removing old data... OK Collecting information from backup file /backupDB/db_temp4_donothing.tar ................................................................................................................................................................................................OK Extracting emlplatform to /AMS/ams/database/ams-9.7.10-443378/emlplatform... OK Extracting ibdatadir to /AMS/ams/database/ams-9.7.10-443378/ibdatadir... OK Extracting iblogs to /AMS/ams/database/ams-9.7.10-443378/iblogs... OK Extracting mysql to /AMS/ams/database/ams-9.7.10-443378/mysql... OK Extracting AMS_SHAREDDATA_HOME to /var/opt/ams/shared/ams-9.7.10-443378... OK Extracting AMS_SHAREDDATA_NEBACKUP_DIR to /var/opt/ams/shared/common... OK Upgrading database... /AMS/ams/database/ams-9.7.10-443378/amsdbmysqlserver: line 265: kill: (1451098) - No such process Can not start database. Upgrade failed. Clean up... OK [amssys@host-11-1-0-69 ]$

MYSQL Log:

221101 12:32:39 server_audit: STOPPED 221101 12:32:39 mysqld_safe mysqld from pid file /var/run/ams/mysql.pid ended 221101 12:37:56 mysqld_safe Starting mysqld daemon with databases from /AMS/ams/database/ams-9.7.10-443378 2022-11-01 12:37:56 0 [Note] /opt/ams/software/ams-9.7.10-443378/server/mysql/mariadb-10.3.31-13-redhat-x86_64/bin/mysqld (mysqld 10.3.31-13-MariaDB-enterprise-log) starting as process 1451377 ... 2022-11-01 12:37:56 0 [Warning] Could not increase number of max_open_files to more than 65000 (request: 164039) 2022-11-01 12:37:56 0 [Note] InnoDB: Using Linux native AIO 2022-11-01 12:37:56 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-11-01 12:37:56 0 [Note] InnoDB: Uses event mutexes 2022-11-01 12:37:56 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2022-11-01 12:37:56 0 [Note] InnoDB: Number of pools: 1 2022-11-01 12:37:56 0 [Note] InnoDB: Using SSE2 crc32 instructions 2022-11-01 12:37:56 0 [Note] InnoDB: Initializing buffer pool, total size = 2G, instances = 8, chunk size = 128M 2022-11-01 12:37:56 0 [Note] InnoDB: Completed initialization of buffer pool 2022-11-01 12:37:56 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2022-11-01 12:37:56 0 [ERROR] InnoDB: Upgrade after a crash is not supported. This redo log was created before MariaDB 10.2.2. 2022-11-01 12:37:56 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error 2022-11-01 12:37:57 0 [Note] InnoDB: Starting shutdown... 2022-11-01 12:37:57 0 [ERROR] Plugin 'InnoDB' init function returned error. 2022-11-01 12:37:57 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2022-11-01 12:37:57 0 [Note] Plugin 'FEEDBACK' is disabled. 221101 12:37:57 server_audit: MariaDB Audit Plugin version 1.4.13 STARTED. 221101 12:37:57 server_audit: Could not create file '/var/opt/ams/local/ams-9.7.10-443378/traces/debug/.database_access.log'. 2022-11-01 12:37:57 0 [Warning] mysqld: SERVER AUDIT plugin can't create file '/var/opt/ams/local/ams-9.7.10-443378/traces/debug/.database_access.log'. 2022-11-01 12:37:57 0 [ERROR] Unknown/unsupported storage engine: InnoDB 2022-11-01 12:37:57 0 [ERROR] Aborting

221101 12:37:57 server_audit: STOPPED 221101 12:37:57 mysqld_safe mysqld from pid file /var/run/ams/mysql.pid ended

Answer Answered by Daniel Black in this comment.

Was ams_copy_datafiles taken while the server was stopped? It should be.

The solution to your situation is to:

  • start a 10.1.x server on your data
  • let it cleanly shutdown, and then
  • migrate to 10.3 (or later)
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.