Abstract error when converting RDS MySQL 5.7.44 to MySQL 8

0

Hello! I'm converting an RDS MySQL 5.7.44 instance to MySQL 8, however, I receive a single error in the log that doesn't say much. I've been looking for answers in the community and in the MySQL manual. But with the incomplete information provided by the log I can't find anything.

Can anybody help me? The contents of the log files follow.

PrePatchCompatibility.log As you can see in the PrePatchCompatibility log, my server is compatible.

Executing Compatibility Checks for the MySQL server at /tmp%2Fmysql.sock.
 Source Version: 5.7.44-log - Please upgrade to 8.0 or opt-in to the paid RDS Extended Support service before 5.7 reaches end of standard support on 29 February, 2024: https://a.co/hQqiIn0, Target Version: 8.0.28.

1) Usage of old temporal type
	No issues found.

2) Usage of db objects with names conflicting with new reserved keywords
	No issues found.

3) Usage of utf8mb3 charset
	The following objects use the utf8mb3 character set. It is recommended to convert them to use utf8mb4 instead, for improved Unicode support.
	More Information:
		https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8mb3.html

mysql - schema's default character set: utf8


4) Table names in the mysql schema conflicting with new tables in 8.0
	No issues found.

5) Partitioned tables using engines with non native partitioning
	No issues found.

6) Foreign key constraint names longer than 64 characters
	No issues found.

7) Usage of obsolete MAXDB sql_mode flag
	No issues found.

8) Usage of obsolete sql_mode flags
	No issues found.

9) ENUM/SET column definitions containing elements longer than 255 characters
	No issues found.

10) Usage of partitioned tables in shared tablespaces
	No issues found.

11) Circular directory references in tablespace data file paths
	No issues found.

12) Usage of removed functions
	No issues found.

13) Usage of removed GROUP BY ASC/DESC syntax
	No issues found.

14) Removed system variables for error logging to the system log configuration
	No issues found.

15) Removed system variables
	No issues found.

16) System variables with new default values
	No issues found.

17) Schema inconsistencies resulting from file removal or corruption
	No issues found.

18) Issues reported by 'check table x for upgrade' command
	No issues found.

19) The definer column for mysql.events cannot be null or blank.
	No issues found.

20) Tables with dangling FULLTEXT index reference
	No issues found.

21) Routines with deprecated keywords in definition
	No issues found.

22) MySQL preupgrade check to catch users created with MYSQL_NATIVE_PASSWORD plugin
	No issues found.

23) Creating indexes larger than 767 bytes on tables with redundant row format might cause the tables to be inaccessible.
	No issues found.

24) The tables with redundant row format can't have an index larger than 767 bytes.
	No issues found.

25) Column definition mismatch between InnoDB Data Dictionary and actual table definition.
	No issues found.


Errors: 0
Warnings: 0
Database Objects Affected: 0

upgradeFailure.log In the upgradeFailure log, only 2 errors are reported, but without any clarity. So I have no idea what to do to convert.

2024-01-14T02:57:10.389976Z 0 [ERROR] [MY-010022] [Server] Failed to Populate DD tables.

2024-01-14T02:57:10.390220Z 0 [ERROR] [MY-010119] [Server] Aborting

2024-01-14T02:49:32.992141Z 0 [Warning] [MY-011068] [Server] The syntax 'log_slave_updates' is deprecated and will be removed in a future release. Please use log_replica_updates instead.
2024-01-14T02:49:32.992153Z 0 [Warning] [MY-011069] [Server] The syntax '--master-info-repository' is deprecated and will be removed in a future release.
2024-01-14T02:49:32.992163Z 0 [Warning] [MY-011069] [Server] The syntax '--master-info-repository' is deprecated and will be removed in a future release.
2024-01-14T02:49:32.992212Z 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-file' is deprecated and will be removed in a future release.
2024-01-14T02:49:32.992218Z 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-repository' is deprecated and will be removed in a future release.
2024-01-14T02:49:32.992244Z 0 [Warning] [MY-011068] [Server] The syntax 'skip_slave_start' is deprecated and will be removed in a future release. Please use skip_replica_start instead.
2024-01-14T02:49:32.992250Z 0 [Warning] [MY-011068] [Server] The syntax 'slave_exec_mode' is deprecated and will be removed in a future release. Please use replica_exec_mode instead.
2024-01-14T02:49:32.992257Z 0 [Warning] [MY-011068] [Server] The syntax 'slave_load_tmpdir' is deprecated and will be removed in a future release. Please use replica_load_tmpdir instead.
2024-01-14T02:49:32.992344Z 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.
2024-01-14T02:49:32.992467Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead.
2024-01-14T02:49:32.992470Z 0 [Note] [MY-010949] [Server] Basedir set to /rdsdbbin/mysql-8.0.28.R4/.
2024-01-14T02:49:32.992480Z 0 [System] [MY-010116] [Server] /rdsdbbin/mysql/bin/mysqld (mysqld 8.0.28) starting as process 777
2024-01-14T02:49:32.994772Z 0 [Warning] [MY-010161] [Server] You need to use --log-bin to make --log-replica-updates work.
2024-01-14T02:49:32.994865Z 0 [Warning] [MY-010161] [Server] You need to use --log-bin to make --binlog-format work.
2024-01-14T02:49:32.997691Z 0 [Note] [MY-012366] [InnoDB] Using Linux native AIO
2024-01-14T02:49:32.997882Z 0 [Note] [MY-010747] [Server] Plugin 'FEDERATED' is disabled.
2024-01-14T02:49:32.999074Z 1 [System] [MY-011012] [Server] Starting upgrade of data directory.
2024-01-14T02:49:32.999104Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-01-14T02:49:32.999114Z 1 [Note] [MY-013546] [InnoDB] Atomic write enabled
2024-01-14T02:49:32.999144Z 1 [Note] [MY-012932] [InnoDB] PUNCH HOLE support available
2024-01-14T02:49:32.999163Z 1 [Note] [MY-012944] [InnoDB] Uses event mutexes
2024-01-14T02:49:32.999179Z 1 [Note] [MY-012945] [InnoDB] GCC builtin __atomic_thread_fence() is used for memory barrier
2024-01-14T02:49:32.999213Z 1 [Note] [MY-012948] [InnoDB] Compressed tables use zlib 1.2.11
2024-01-14T02:49:33.004617Z 1 [Note] [MY-013251] [InnoDB] Number of pools: 1
2024-01-14T02:49:33.004714Z 1 [Note] [MY-012951] [InnoDB] Using hardware accelerated crc32 and polynomial multiplication.
2024-01-14T02:49:33.005159Z 1 [Warning] [MY-012191] [InnoDB] Scan path '/rdsdbdata/db/innodb' is ignored because it is a sub-directory of '/rdsdbdata/db/
2024-01-14T02:49:33.005172Z 1 [Note] [MY-012203] [InnoDB] Directories to scan './'
2024-01-14T02:49:33.005204Z 1 [Note] [MY-012204] [InnoDB] Scanning './'
2024-01-14T02:49:33.147317Z 1 [Note] [MY-012208] [InnoDB] Completed space ID check of 26 files.
2024-01-14T02:49:33.148610Z 1 [Note] [MY-012955] [InnoDB] Initializing buffer pool, total size = 4.000000G, instances = 8, chunk size =128.000000M 
2024-01-14T02:49:33.281899Z 1 [Note] [MY-012957] [InnoDB] Completed initialization of buffer pool
2024-01-14T02:49:33.303610Z 0 [Note] [MY-011952] [InnoDB] If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2024-01-14T02:49:33.304765Z 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_0.dblwr' for doublewrite
2024-01-14T02:49:33.315211Z 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_1.dblwr' for doublewrite
2024-01-14T02:49:33.373285Z 1 [Note] [MY-013566] [InnoDB] Double write buffer files: 2
2024-01-14T02:49:33.373316Z 1 [Note] [MY-013565] [InnoDB] Double write buffer pages per instance: 32
2024-01-14T02:49:33.373340Z 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_0.dblwr' for doublewrite
2024-01-14T02:49:33.373361Z 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_1.dblwr' for doublewrite
2024-01-14T02:49:33.375910Z 1 [Note] [MY-012529] [InnoDB] Redo log format is v1. The redo log was created before MySQL 8.0.3.
2024-01-14T02:49:33.375934Z 1 [Note] [MY-012557] [InnoDB] Redo log is from an earlier version, v1.
2024-01-14T02:49:33.390451Z 1 [Note] [MY-013083] [InnoDB] Log background threads are being started...
2024-01-14T02:49:33.390739Z 1 [Note] [MY-012532] [InnoDB] Applying a batch of 0 redo log records ...
2024-01-14T02:49:33.390757Z 1 [Note] [MY-012535] [InnoDB] Apply batch completed!
2024-01-14T02:49:33.391779Z 1 [Note] [MY-013041] [InnoDB] Upgrading redo log: 2*134217728 bytes, LSN=76741654181
2024-01-14T02:49:33.391969Z 1 [Note] [MY-013084] [InnoDB] Log background threads are being closed...
2024-01-14T02:49:33.399251Z 1 [Note] [MY-012968] [InnoDB] Starting to delete and rewrite log files.
2024-01-14T02:49:33.435577Z 1 [Note] [MY-013575] [InnoDB] Creating log file /rdsdbdata/log/innodb/ib_logfile101
2024-01-14T02:49:33.438955Z 1 [Note] [MY-013575] [InnoDB] Creating log file /rdsdbdata/log/innodb/ib_logfile1
2024-01-14T02:49:33.469344Z 1 [Note] [MY-012892] [InnoDB] Renaming log file /rdsdbdata/log/innodb/ib_logfile101 to /rdsdbdata/log/innodb/ib_logfile0
2024-01-14T02:49:33.469396Z 1 [Note] [MY-012893] [InnoDB] New log files created, LSN=76741654540
2024-01-14T02:49:33.469411Z 1 [Note] [MY-013083] [InnoDB] Log background threads are being started...
2024-01-14T02:49:33.469835Z 1 [Note] [MY-013040] [InnoDB] Will create 2 new undo tablespaces.
2024-01-14T02:49:33.471710Z 1 [Note] [MY-012896] [InnoDB] Creating UNDO Tablespace ./undo_001
2024-01-14T02:49:33.471724Z 1 [Note] [MY-012897] [InnoDB] Setting file ./undo_001 size to 16 MB
2024-01-14T02:49:33.471736Z 1 [Note] [MY-012898] [InnoDB] Physically writing the file full
2024-01-14T02:49:33.500284Z 1 [Note] [MY-012896] [InnoDB] Creating UNDO Tablespace ./undo_002
2024-01-14T02:49:33.500303Z 1 [Note] [MY-012897] [InnoDB] Setting file ./undo_002 size to 16 MB
2024-01-14T02:49:33.500314Z 1 [Note] [MY-012898] [InnoDB] Physically writing the file full
2024-01-14T02:49:33.525947Z 1 [Note] [MY-012915] [InnoDB] Created 2 undo tablespaces.
2024-01-14T02:49:33.526127Z 1 [Note] [MY-011980] [InnoDB] GTID recovery trx_no: 0
2024-01-14T02:49:33.558100Z 1 [Note] [MY-013776] [InnoDB] Parallel initialization of rseg complete
2024-01-14T02:49:33.558127Z 1 [Note] [MY-013777] [InnoDB] Time taken to initialize rseg using 4 thread: 32005 ms.
2024-01-14T02:49:33.558169Z 1 [Note] [MY-012923] [InnoDB] Creating shared tablespace for temporary tables
2024-01-14T02:49:33.558214Z 1 [Note] [MY-012265] [InnoDB] Setting file '/rdsdbdata/db/innodb/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-01-14T02:49:33.578634Z 1 [Note] [MY-012266] [InnoDB] File '/rdsdbdata/db/innodb/ibtmp1' size is now 12 MB.
2024-01-14T02:49:33.578720Z 1 [Note] [MY-013627] [InnoDB] Scanning temp tablespace dir:'./#innodb_temp/'
2024-01-14T02:49:33.599593Z 1 [Note] [MY-013018] [InnoDB] Created 128 and tracked 128 new rollback segment(s) in the temporary tablespace. 128 are now active.
2024-01-14T02:49:33.603949Z 1 [Note] [MY-013018] [InnoDB] Created 128 and tracked 128 new rollback segment(s) in undo tablespace number 1. 128 are now active.
2024-01-14T02:49:33.609602Z 1 [Note] [MY-013018] [InnoDB] Created 128 and tracked 128 new rollback segment(s) in undo tablespace number 2. 128 are now active.
2024-01-14T02:49:33.646187Z 1 [Note] [MY-012976] [InnoDB] 8.0.28 started; log sequence number 76744013270
2024-01-14T02:49:33.758397Z 1 [Note] [MY-012922] [InnoDB] Waiting for purge to start
2024-01-14T02:49:33.813941Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-01-14T02:49:33.815138Z 1 [Note] [MY-011088] [Server] Data dictionary initializing version '80023'.
2024-01-14T02:49:34.219961Z 1 [Note] [MY-010337] [Server] Created Data Dictionary for upgrade
2024-01-14T02:49:34.244061Z 0 [Note] [MY-011332] [Server] Plugin mysqlx reported: 'IPv6 is available'
2024-01-14T02:49:34.246445Z 0 [Note] [MY-011323] [Server] Plugin mysqlx reported: 'X Plugin ready for connections. bind-address: '::' port: 33060'
2024-01-14T02:49:34.246466Z 0 [Note] [MY-011323] [Server] Plugin mysqlx reported: 'X Plugin ready for connections. socket: '/tmp/mysqlx.sock''
2024-01-14T02:53:23.212189Z 2 [Warning] [MY-010772] [Server] db.opt file not found for innodb database. Using default Character set.
2024-01-14T02:56:38.583991Z 2 [Warning] [MY-010772] [Server] db.opt file not found for tmp database. Using default Character set.
2024-01-14T02:57:10.389976Z 0 [ERROR] [MY-010022] [Server] Failed to Populate DD tables.
2024-01-14T02:57:10.390220Z 0 [ERROR] [MY-010119] [Server] Aborting
2024-01-14T02:57:10.390285Z 0 [Note] [MY-012330] [InnoDB] FTS optimize thread exiting.
2024-01-14T02:57:12.301270Z 0 [Note] [MY-010120] [Server] Binlog end
2024-01-14T02:57:12.302518Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'auth_socket'
2024-01-14T02:57:12.302539Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'RDS_EVENTS_THREADS_WAITS_CURRENT'
2024-01-14T02:57:12.302548Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'RDS_PROCESSLIST'
2024-01-14T02:57:12.302557Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'mysqlx'
2024-01-14T02:57:12.302908Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'mysqlx_cache_cleaner'
2024-01-14T02:57:12.302924Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'ngram'
2024-01-14T02:57:12.302931Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'BLACKHOLE'
2024-01-14T02:57:12.302940Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'ARCHIVE'
2024-01-14T02:57:12.302949Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'TempTable'
2024-01-14T02:57:12.302957Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'PERFORMANCE_SCHEMA'
2024-01-14T02:57:12.303000Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'MRG_MYISAM'
2024-01-14T02:57:12.303008Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'MyISAM'
2024-01-14T02:57:12.303018Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_SESSION_TEMP_TABLESPACES'
2024-01-14T02:57:12.303025Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_CACHED_INDEXES'
2024-01-14T02:57:12.303033Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_VIRTUAL'
2024-01-14T02:57:12.303041Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_COLUMNS'
2024-01-14T02:57:12.303048Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_TABLESPACES'
2024-01-14T02:57:12.303055Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_INDEXES'
2024-01-14T02:57:12.303062Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_TABLESTATS'
2024-01-14T02:57:12.303069Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_TABLES'
2024-01-14T02:57:12.303077Z 0 [Note] [MY-010733] [Server] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2024-01-14T02:57:12.303084Z 0 [Note] [MY-010733] [Server] Shutting down plugin '
asked 4 months ago585 views
2 Answers
0
Accepted Answer

An error then occurred when trying to populate the data dictionary (DD) tables during startup. The DD tables store metadata about databases, tables, columns and other objects. On-premisem, you could check that the DD tables exist in the data directory and have the correct structure. also you could try populating the DD tables manually using a query after restart. If restarting doesn't resolve it, the DD tables may be corrupted. You may need to repair them using mysqld --initialize. But this is RDS, Why don't you open a support case to request engineers to investigate internal issues seems like a reasonable approach? If you have any question regarding this, please feel free to ask.

AWS
Regina
answered 4 months ago
  • Hello! Yes, it is RDS. I'm working on converting my MySQL 5.7 servers to MySQL 8. I do not currently have a support plan contracted.

    What's not clear to me is how to find out exactly which table has the problem.

0

It could be happend by the reserved keywords used in the Database Objects. Try to remove all those Database Objects with the reserved keywords. Please refer to 8.0 keyworkd page: https://dev.mysql.com/doc/mysqld-version-reference/en/keywords-8-0.html#keywords-new-in-8-0

AWS
Regina
answered 4 months ago
  • Thanks for the response Regina. But when you stop at all the objects, do you talk about the names of tables, functions, triggers, procedures and views or the names of columns too? I ask because I already validated the table names and deleted all triggers, procedures, functions and views from my database to try to import.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions