################## 5.7.43
rm -rf 112067/
bin/mysqld --no-defaults --initialize-insecure --basedir=$PWD --datadir=$PWD/112067 --log-error-verbosity=3
bin/mysqld_safe --no-defaults --basedir=$PWD --datadir=$PWD/112067 --core-file --socket=/tmp/mysql.sock  --port=3306 --log-error=$PWD/112067/log.err --log-error-verbosity=3  --secure-file-priv="" --local-infile=1 2>&1 &

 bin/mysql -uroot -S /tmp/mysql.sock
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 5
Server version: 5.7.43 MySQL Community Server (GPL)

Copyright (c) 2000, 2023, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> SHOW GLOBAL VARIABLES LIKE 'rewriter_enabled';
+------------------+-------+
| Variable_name    | Value |
+------------------+-------+
| rewriter_enabled | ON    |
+------------------+-------+
1 row in set (0.00 sec)



##
-- tried with "Upgrade Checker Utility" before upgrade and it rightly pointed out potential issues

bin/mysqlsh -- util checkForServerUpgrade root@localhost:3306 --target-version=8.0.34
Please provide the password for 'root@localhost:3306':
Save password for 'root@localhost:3306'? [Y]es/[N]o/Ne[v]er (default No):
The MySQL server at localhost:3306, version 5.7.43 - MySQL Community Server
(GPL), will now be checked for compatibility issues for upgrade to MySQL
8.0.34...

1) Usage of old temporal type
  No issues found

2) MySQL 8.0 syntax check for routine-like objects
  The following objects did not pass a syntax check with the latest MySQL 8.0
    grammar. A common reason is that they reference names that conflict with new
    reserved keywords. You must update these routine definitions and `quote` any
    such references before upgrading.
  More information:
    https://dev.mysql.com/doc/refman/en/keywords.html

  query_rewrite.flush_rewrite_rules - at line 5,8: unexpected token 'QUERY'

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

4) Usage of utf8mb3 charset
  Warning: 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

  query_rewrite.rewrite_rules.pattern - column's default character set: utf8
  query_rewrite.rewrite_rules.pattern_database - column's default character
    set: utf8
  query_rewrite.rewrite_rules.replacement - column's default character set: utf8
  query_rewrite.rewrite_rules.enabled - column's default character set: utf8
  query_rewrite.rewrite_rules.message - column's default character set: utf8
  query_rewrite.rewrite_rules.pattern_digest - column's default character set:
    utf8
  query_rewrite.rewrite_rules.normalized_pattern - column's default character
    set: utf8

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

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

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

8) Usage of obsolete MAXDB sql_mode flag
  No issues found

9) Usage of obsolete sql_mode flags
  Notice: The following DB objects have obsolete options persisted for
    sql_mode, which will be cleared during upgrade to 8.0.
  More information:
    https://dev.mysql.com/doc/refman/8.0/en/mysql-nutshell.html#mysql-nutshell-removals

  query_rewrite.flush_rewrite_rules - PROCEDURE uses obsolete
    NO_AUTO_CREATE_USER sql_mode
  global system variable sql_mode - defined using obsolete NO_AUTO_CREATE_USER
    option

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

11) Usage of partitioned tables in shared tablespaces
  No issues found

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

13) Usage of removed functions
  No issues found

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

15) Removed system variables for error logging to the system log configuration
  To run this check requires full path to MySQL server configuration file to be specified at 'configPath' key of options dictionary
  More information:
    https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-13.html#mysqld-8-0-13-logging

16) Removed system variables
  To run this check requires full path to MySQL server configuration file to be specified at 'configPath' key of options dictionary
  More information:
    https://dev.mysql.com/doc/refman/8.0/en/added-deprecated-removed.html#optvars-removed

17) System variables with new default values
  To run this check requires full path to MySQL server configuration file to be specified at 'configPath' key of options dictionary
  More information:
    https://mysqlserverteam.com/new-defaults-in-mysql-8-0/

18) Zero Date, Datetime, and Timestamp values
  No issues found

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

20) Tables recognized by InnoDB that belong to a different engine
  No issues found

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

22) New default authentication plugin considerations
  Warning: The new default authentication plugin 'caching_sha2_password' offers
    more secure password hashing than previously used 'mysql_native_password'
    (and consequent improved client connection authentication). However, it also
    has compatibility implications that may affect existing MySQL installations.
    If your MySQL installation must serve pre-8.0 clients and you encounter
    compatibility issues after upgrading, the simplest way to address those
    issues is to reconfigure the server to revert to the previous default
    authentication plugin (mysql_native_password). For example, use these lines
    in the server option file:

    [mysqld]
    default_authentication_plugin=mysql_native_password

    However, the setting should be viewed as temporary, not as a long term or
    permanent solution, because it causes new accounts created with the setting
    in effect to forego the improved authentication security.
    If you are using replication please take time to understand how the
    authentication plugin changes may impact you.
  More information:
    https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password-compatibility-issues
    https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password-replication

23) Columns which cannot have default values
  No issues found

24) Check for invalid table names and schema names used in 5.7
  No issues found

25) Check for orphaned routines in 5.7
  No issues found

26) Check for deprecated usage of single dollar signs in object names
  No issues found

27) Check for indexes that are too large to work on higher versions of MySQL
Server than 5.7
  No issues found

28) Check for deprecated '.<table>' syntax used in routines.
  No issues found

Errors:   1
Warnings: 8
Notices:  2



################## In place upgrade to 8.0.34

bin/mysqld_safe --no-defaults --mysqld-version='' --basedir=$PWD --datadir=/export/home/tmp/ushastry/mysql-5.7.43/112067 --core-file --socket=/tmp/mysql.sock  --port=3306 --log-error=/export/home/tmp/ushastry/mysql-5.7.43/112067/log.err --mysqlx-port=33330 --mysqlx-socket=/tmp/mysql_x_ushastry.sock --log-error-verbosity=3  --secure-file-priv="" --local-infile=1  2>&1 &


--extract from error log


2023-08-16T10:37:08.152752Z mysqld_safe Logging to '/export/home/tmp/ushastry/mysql-5.7.43/112067/log.err'.
2023-08-16T10:37:08.170535Z mysqld_safe Starting mysqld daemon with databases from /export/home/tmp/ushastry/mysql-5.7.43/112067
2023-08-16T10:37:08.367015Z 0 [Warning] [MY-010097] [Server] Insecure configuration for --secure-file-priv: Current value does not restrict location of generated files. Consider setting it to a valid, non-empty path.
2023-08-16T10:37:08.367062Z 0 [Note] [MY-013932] [Server] BuildID[sha1]=28f3310e13fa6957a8b1f0a224430684bf64ba8d
2023-08-16T10:37:08.367066Z 0 [Note] [MY-010949] [Server] Basedir set to /export/home/tmp/ushastry/mysql-8.0.34/.
2023-08-16T10:37:08.367071Z 0 [System] [MY-010116] [Server] /export/home/tmp/ushastry/mysql-8.0.34/bin/mysqld (mysqld 8.0.34) starting as process 14566
2023-08-16T10:37:08.373146Z 0 [Note] [MY-012366] [InnoDB] Using Linux native AIO
2023-08-16T10:37:08.373335Z 0 [Note] [MY-010747] [Server] Plugin 'FEDERATED' is disabled.
2023-08-16T10:37:08.373384Z 0 [Note] [MY-010747] [Server] Plugin 'ndbcluster' is disabled.
2023-08-16T10:37:08.373400Z 0 [Note] [MY-010747] [Server] Plugin 'ndbinfo' is disabled.
2023-08-16T10:37:08.373407Z 0 [Note] [MY-010747] [Server] Plugin 'ndb_transid_mysql_connection_map' is disabled.
2023-08-16T10:37:08.374726Z 1 [System] [MY-011012] [Server] Starting upgrade of data directory.
2023-08-16T10:37:08.374751Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2023-08-16T10:37:08.374767Z 1 [Note] [MY-013546] [InnoDB] Atomic write enabled
2023-08-16T10:37:08.374784Z 1 [Note] [MY-012932] [InnoDB] PUNCH HOLE support available
2023-08-16T10:37:08.374795Z 1 [Note] [MY-012944] [InnoDB] Uses event mutexes
2023-08-16T10:37:08.374801Z 1 [Note] [MY-012945] [InnoDB] GCC builtin __atomic_thread_fence() is used for memory barrier
2023-08-16T10:37:08.374806Z 1 [Note] [MY-012948] [InnoDB] Compressed tables use zlib 1.2.13
2023-08-16T10:37:08.376004Z 1 [Note] [MY-012951] [InnoDB] Using hardware accelerated crc32 and polynomial multiplication.
2023-08-16T10:37:08.376324Z 1 [Note] [MY-012203] [InnoDB] Directories to scan './'
2023-08-16T10:37:08.376364Z 1 [Note] [MY-012204] [InnoDB] Scanning './'
2023-08-16T10:37:08.377542Z 1 [Note] [MY-012208] [InnoDB] Completed space ID check of 21 files.
2023-08-16T10:37:08.378002Z 1 [Note] [MY-012955] [InnoDB] Initializing buffer pool, total size = 128.000000M, instances = 1, chunk size =128.000000M
2023-08-16T10:37:08.383545Z 1 [Note] [MY-012957] [InnoDB] Completed initialization of buffer pool
2023-08-16T10:37:08.385510Z 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().
2023-08-16T10:37:08.385996Z 1 [Note] [MY-013566] [InnoDB] Double write buffer files: 2
2023-08-16T10:37:08.386014Z 1 [Note] [MY-013565] [InnoDB] Double write buffer pages per instance: 4
2023-08-16T10:37:08.386054Z 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_0.dblwr' for doublewrite
2023-08-16T10:37:08.386193Z 1 [Note] [MY-013532] [InnoDB] Using './#ib_16384_1.dblwr' for doublewrite
2023-08-16T10:37:08.405117Z 1 [Note] [MY-012529] [InnoDB] Redo log format is v1. The redo log was created before MySQL 8.0.30.
2023-08-16T10:37:08.405437Z 1 [Note] [MY-012557] [InnoDB] Redo log is from an earlier version, v1.
2023-08-16T10:37:08.405473Z 1 [Note] [MY-013888] [InnoDB] Upgrading redo log: 0M, LSN=2772161.
2023-08-16T10:37:08.405480Z 1 [Note] [MY-012968] [InnoDB] Starting to delete and rewrite redo log files.
2023-08-16T10:37:08.435206Z 1 [Note] [MY-012893] [InnoDB] New redo log files created, LSN=2772492
2023-08-16T10:37:08.435288Z 1 [Note] [MY-013883] [InnoDB] The latest found checkpoint is at lsn = 2772492 in redo log file ./#innodb_redo/#ib_redo0.
2023-08-16T10:37:08.435354Z 1 [Note] [MY-013086] [InnoDB] Starting to parse redo log at lsn = 2772492, whereas checkpoint_lsn = 2772492 and start_lsn = 2772480
2023-08-16T10:37:08.437000Z 1 [Note] [MY-013083] [InnoDB] Log background threads are being started...
2023-08-16T10:37:08.437473Z 1 [Note] [MY-012532] [InnoDB] Applying a batch of 0 redo log records ...
2023-08-16T10:37:08.437537Z 1 [Note] [MY-012535] [InnoDB] Apply batch completed!
2023-08-16T10:37:08.437952Z 1 [Note] [MY-013040] [InnoDB] Will create 2 new undo tablespaces.
2023-08-16T10:37:08.439710Z 1 [Note] [MY-012896] [InnoDB] Creating UNDO Tablespace ./undo_001
2023-08-16T10:37:08.439727Z 1 [Note] [MY-012897] [InnoDB] Setting file ./undo_001 size to 16 MB
2023-08-16T10:37:08.439732Z 1 [Note] [MY-012898] [InnoDB] Physically writing the file full
2023-08-16T10:37:08.482817Z 1 [Note] [MY-012896] [InnoDB] Creating UNDO Tablespace ./undo_002
2023-08-16T10:37:08.482838Z 1 [Note] [MY-012897] [InnoDB] Setting file ./undo_002 size to 16 MB
2023-08-16T10:37:08.482844Z 1 [Note] [MY-012898] [InnoDB] Physically writing the file full
2023-08-16T10:37:08.522199Z 1 [Note] [MY-012915] [InnoDB] Created 2 undo tablespaces.
2023-08-16T10:37:08.522309Z 1 [Note] [MY-011980] [InnoDB] GTID recovery trx_no: 0
2023-08-16T10:37:08.523365Z 1 [Note] [MY-013776] [InnoDB] Parallel initialization of rseg complete
2023-08-16T10:37:08.523398Z 1 [Note] [MY-013777] [InnoDB] Time taken to initialize rseg using 4 thread: 1085 ms.
2023-08-16T10:37:08.523429Z 1 [Note] [MY-012923] [InnoDB] Creating shared tablespace for temporary tables
2023-08-16T10:37:08.523468Z 1 [Note] [MY-012265] [InnoDB] Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-08-16T10:37:08.556530Z 1 [Note] [MY-012266] [InnoDB] File './ibtmp1' size is now 12 MB.
2023-08-16T10:37:08.556667Z 1 [Note] [MY-013627] [InnoDB] Scanning temp tablespace dir:'./#innodb_temp/'
2023-08-16T10:37:08.578264Z 1 [Note] [MY-013018] [InnoDB] Created 128 and tracked 128 new rollback segment(s) in the temporary tablespace. 128 are now active.
2023-08-16T10:37:08.581159Z 1 [Note] [MY-013018] [InnoDB] Created 128 and tracked 128 new rollback segment(s) in undo tablespace number 1. 128 are now active.
2023-08-16T10:37:08.584081Z 1 [Note] [MY-013018] [InnoDB] Created 128 and tracked 128 new rollback segment(s) in undo tablespace number 2. 128 are now active.
2023-08-16T10:37:08.742760Z 1 [Note] [MY-012976] [InnoDB] 8.0.34 started; log sequence number 5131222
2023-08-16T10:37:08.749756Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2023-08-16T10:37:08.752612Z 1 [Note] [MY-011088] [Server] Data dictionary initializing version '80023'.
2023-08-16T10:37:09.178482Z 1 [Note] [MY-010337] [Server] Created Data Dictionary for upgrade
2023-08-16T10:37:09.198341Z 0 [Note] [MY-011332] [Server] Plugin mysqlx reported: 'IPv6 is available'
2023-08-16T10:37:09.199942Z 0 [Note] [MY-011323] [Server] Plugin mysqlx reported: 'X Plugin ready for connections. bind-address: '::' port: 33330'
2023-08-16T10:37:09.199964Z 0 [Note] [MY-011323] [Server] Plugin mysqlx reported: 'X Plugin ready for connections. socket: '/tmp/mysql_x_ushastry.sock''
2023-08-16T10:37:09.748727Z 2 [ERROR] [MY-013235] [Server] Error in parsing Routine 'query_rewrite'.'flush_rewrite_rules' during upgrade. You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'QUERY CACHE;   IF NOT message_text IS NULL THEN     SIGNAL SQLSTATE '45000' SET ' at line 6
2023-08-16T10:37:10.104411Z 0 [ERROR] [MY-010022] [Server] Failed to Populate DD tables.
2023-08-16T10:37:10.104440Z 0 [ERROR] [MY-010119] [Server] Aborting
2023-08-16T10:37:10.104503Z 0 [Note] [MY-012330] [InnoDB] FTS optimize thread exiting.