Bug #98694 MySQL8.0 won't start
Submitted: 20 Feb 2020 16:03 Modified: 20 Feb 2020 17:26
Reporter: Lara Hawchar Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:8.0.19 OS:Windows
Assigned to: CPU Architecture:Any

[20 Feb 2020 16:03] Lara Hawchar
I had to load data from a file that is not in:
C:\ProgramData\MySQL\MySQL Server 8.0\Uploads
Therefore, in my.ini file, I had to set --secure-file-priv=""
I was trying to run a python code (with connection to MySQL) that reads several .csv files (~1000 files with a total size of ~80GB) and save them in on table in an existing schema in MySQL. However, the data I was trying to load was to be save in a table that is not created in C:\ProgramData\MySQL\MySQL Server 8.0\Data, but in a folder in a different drive (not on C:).
While running the python code, an error (in Spyder for Python) was generated saying that the connection in MySQL was lost!!
I tried to figure out why this happened and how to fix it but i couldn't.
When I was trying to restart MySQL8.0 in "Services", I had an error message in the error file, as below (part of the message):

InnoDB: Progress in percents: 12020-02-20T15:44:08.160766Z 1 [Warning] [MY-010005] [Server] Skip re-populating collations and character sets tables in InnoDB read-only mode.
2020-02-20T15:44:08.166266Z 2 [Warning] [MY-011018] [Server] Skip updating information_schema metadata in InnoDB read-only mode.
2020-02-20T15:44:08.167920Z 0 [ERROR] [MY-011853] [InnoDB] Corruption of an index tree: table `ehs_schema`.`avl_event_largedata` index `PRIMARY`, father ptr page no 65331, child page no 65332
PHYSICAL RECORD: n_fields 18; compact format; info bits 0
 0:2020-02-20T15:44:08.168680Z 0 [Warning] [MY-010970] [Server] Skipped updating resource group metadata in InnoDB read only mode.

How to repeat:
[20 Feb 2020 17:26] MySQL Verification Team
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.  

Thank you for your interest in MySQL.