# Unable to do keyring migration and returns the error When we run the command to keyring migration, we are getting the following errors "unknown variable 'innodb\_file\_per\_table=1'" **URL:** \ **Category:** MySQL & MariaDB\ **Created:** [October 19, 2023, 6:10pm UTC](https://forums.percona.com/t/unable-to-do-keyring-migration-and-returns-the-error-when-we-run-the-command-to-keyring-migration-we-are-getting-the-following-errors-unknown-variable-innodb-file-per-table-1/26047 "2023-10-19T18:10:04Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Ramasamy](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ramasamy/32/16466_2.png) [@Ramasamy](https://forums.percona.com/u/Ramasamy)\ **Post date:** [October 19, 2023, 6:10pm UTC](https://forums.percona.com/t/unable-to-do-keyring-migration-and-returns-the-error-when-we-run-the-command-to-keyring-migration-we-are-getting-the-following-errors-unknown-variable-innodb-file-per-table-1/26047/1 "2023-10-19T18:10:04Z")
When we run the command to keyring migration, we are getting the following errors “unknown variable ‘innodb\_file\_per\_table=1’” [root@e04bmm-mytst07 plugin]# mysqld --defaults-file=/etc/my.cnf --keyring-migration-source=keyring\_file.so --keyring-migration-destination=component\_keyring\_file.so --keyring-migration-to-component --user=mysql 2023-10-19T11:59:57.182810-05:00 0 [Warning] [MY-011068] [Server] The syntax ‘master\_verify\_checksum’ is deprecated and will be removed in a future release. Please use source\_verify\_checksum instead. 2023-10-19T11:59:57.182834-05:00 0 [Warning] [MY-011070] [Server] ‘Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it’ is deprecated and will be removed in a future release. 2023-10-19T11:59:57.182843-05:00 0 [Warning] [MY-011070] [Server] ‘Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it’ is deprecated and will be removed in a future release. 2023-10-19T11:59:57.182913-05:00 0 [Warning] [MY-011069] [Server] The syntax ‘–ssl=on’ is deprecated and will be removed in a future release. 2023-10-19T11:59:57.182931-05:00 0 [Warning] [MY-011068] [Server] The syntax ‘expire-logs-days’ is deprecated and will be removed in a future release. Please use binlog\_expire\_logs\_seconds instead. 2023-10-19T11:59:57.182976-05:00 0 [Warning] [MY-010915] [Server] ‘NO\_ZERO\_DATE’, ‘NO\_ZERO\_IN\_DATE’ and ‘ERROR\_FOR\_DIVISION\_BY\_ZERO’ sql modes should be used with strict mode. They will be merged with strict mode in a future release. 2023-10-19T11:59:57.184269-05:00 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-log-path: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path. 2023-10-19T11:59:57.184354-05:00 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.34-26) starting as process 24848 2023-10-19T11:59:57.189275-05:00 0 [Warning] [MY-013360] [Server] Plugin keyring\_file reported: ‘‘keyring\_file plugin’ is deprecated and will be removed in a future release. Please use component\_keyring\_file instead’ 2023-10-19T11:59:57.192707-05:00 0 [ERROR] [MY-000067] [Server] unknown variable ‘innodb\_file\_per\_table=1’. 2023-10-19T11:59:57.192716-05:00 0 [ERROR] [MY-011084] [Server] Keyring migration failed. 2023-10-19T11:59:57.193555-05:00 0 [ERROR] [MY-010119] [Server] Aborting 2023-10-19T11:59:57.194728-05:00 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.34-26) Percona Server (GPL), Release 26, Revision 0fe62c85. [root@e04bmm-mytst07 plugin]# ---
**Author:** ![Abhinav\_Gupta](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/abhinav_gupta/32/6262_2.png) [@Abhinav\_Gupta](https://forums.percona.com/u/Abhinav_Gupta)\ **Post date:** [November 6, 2023, 12:06pm UTC](https://forums.percona.com/t/unable-to-do-keyring-migration-and-returns-the-error-when-we-run-the-command-to-keyring-migration-we-are-getting-the-following-errors-unknown-variable-innodb-file-per-table-1/26047/2 "2023-11-06T12:06:17Z")
> [@Ramasamy](#): > > keyring-migration Try **NOT** to define the default my.cnf file under the **–defaults-file** instead create a dedicated **my-migration.cnf** file and specify only the minimal parameters inside this cnf that are **required** for this migration only. From MySQL Reference Manual : [https://dev.mysql.com/doc/refman/8.0/en/keyring-key-migration.html](https://dev.mysql.com/doc/refman/8.0/en/keyring-key-migration.html) > - Other server options might be required, such as configuration parameters for the two keyring plugins. For example, if `keyring_file` is the source or destination, you must set the [`keyring_file_data`](https://dev.mysql.com/doc/refman/8.0/en/keyring-system-variables.html#sysvar_keyring_file_data) system variable if the keyring data file location is not the default location. Other non-keyring options may be required as well. One way to specify these options is by using [`--defaults-file`](https://dev.mysql.com/doc/refman/8.0/en/option-file-options.html#option_general_defaults-file) to name an option file **that contains the required options.**