Re: Can't run MySQL Server 5.7
Posted by: Saïdou Niang
Date: October 19, 2017 12:53AM

Yes I tried that:

Quote

C:\Program Files\MySQL\MySQL Server 5.7\bin>mysqld --initialize2017-10-19T06:32:36.401011Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2017-10-19T06:32:36.416646Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
2017-10-19T06:32:36.432296Z 0 [ERROR] Aborting

Even when emptying/deleting the Data directory I get the same output.

Using "--explicit_defaults_for_timestamp=1" still gives errors:

Quote

C:\Program Files\MySQL\MySQL Server 5.7\bin>mysqld --initialize --explicit_defaults_for_timestamp=1
2017-10-19T06:39:34.955507Z 0 [ERROR] --initialize specified but the data directory has files in it. Aborting.
2017-10-19T06:39:34.955507Z 0 [ERROR] Aborting

On the MySQL Help & Support it says:

If a data directory exists and is not empty (that is, it contains files or subdirectories), the server exits after producing an error message:

Quote

[ERROR] --initialize specified but the data directory exists. Aborting.
In this case, remove or rename the data directory and try again.


However, the Data directory ("C:\ProgramData\MySQL\MySQL Server 5.7\Data") is empty and renamed...

I'm just starting with MySQL, so I'm still a dummy :)

Options: ReplyQuote


Subject
Views
Written By
Posted
282
October 18, 2017 08:43AM
180
October 18, 2017 11:27AM
169
October 18, 2017 12:21PM
94
October 18, 2017 02:56PM
Re: Can't run MySQL Server 5.7
78
October 19, 2017 12:53AM
81
October 19, 2017 01:06AM
88
October 18, 2017 12:26PM
90
October 19, 2017 10:00AM


Sorry, only registered users may post in this forum.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.