Hi Martin,
On 4/12/2016 07:23, Martin Mueller wrote:
I abandoned a MySQL 5.22 database that quite suddenly andthat I wasn’t able to
start up again. The data directory consists of a mix of ISAM and Inno tables.
I was able to copy the ISAM tables into a new 5.6 version, and they work.
Hi Martin
On 4/12/2016 07:23, Martin Mueller wrote:
I abandoned a MySQL 5.22 database that quite suddenly andthat I wasn’t able to
start up again. The data directory consists of a mix of ISAM and Inno tables.
I was able to copy the ISAM tables into a new 5.6 version, and they work.
I
Well, the command
sudo /usr/local/mysql/support-files/mysql.server stop
generates the error message:
ERROR! MySQL server PID file could not be found!
On the other hand,
sudo launchctl unload -F
/Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
stops the server and
sudo
On 12/3/2016 14:23, Martin Mueller wrote:
I abandoned a MySQL 5.22 database
There's been 5.0m 5,1, 5,4 (briefly), 5.5, 5.6 and now 5.7. No 5,.2.
that quite suddenly andthat I wasn’t able to start up again. The data
directory consists of a mix of ISAM and Inno tables.
You mean MyISAM?
On 12/3/2016 13:58, Martin Mueller wrote:
I was able to install a version of MySQL 5.6 on OS Sierra. It appears that the
“launchdaemon’ method works while the mysql.server start/stop method does not
work. In retrospect I should have seen that, but I also think that the
official documentation
Am 03.12.2016 um 21:23 schrieb Martin Mueller:
In my case, I can reproduce Time machine backups of data directories at varying
times. At one point I was able to replace the non-working installation with an
earlier installation, but then it failed unpredictably.
Are the Inno tables on Time
I abandoned a MySQL 5.22 database that quite suddenly andthat I wasn’t able to
start up again. The data directory consists of a mix of ISAM and Inno tables.
I was able to copy the ISAM tables into a new 5.6 version, and they work.
I understand that INNO tables are different because different
On 12/2/2016 17:58, Martin Mueller wrote:
Alas, running the stop and start commands under sudo makes zero difference.
?! The cited page recommends more than sudo starts and stops, eg ...
|unset TMPDIR mysql_install_db |
Did you try that? Did you check the pid setting in my.cnf, eg
2016/12/02 18:58 ... Martin Mueller:
Alas, running the stop and start commands under sudo makes zero difference.
This is a very frustrating problem, and I hope somebody in the MySQl
documentation department will take a look at it. It’s cleary a problem that
has been around for years because
