-
Notifications
You must be signed in to change notification settings - Fork 2
Database Troubleshooting
John Holt edited this page Oct 25, 2017
·
33 revisions
Look for mysqld.exe task running in task manager or for the service MQSQLXX (currently 57) running. If it is not running log files are in ...var\mysql\Data\XXX.err. To start it as an admin start the services from the start menu then start the MYSQLXX service.
Database disc space is taken up by tables stored in C:\Instrument\Var\mysql\data the space can be regained by truncating the table. This could lose the data and will certainly remove it from the database so be careful. At various stages you will be prompted for the database password it is on the passwords page.
First create a sql dump of the two largest schemas:
"c:\Program Files\MySQL\MySQL Server 5.7\bin\mysqldump.exe" -u root -p msg_log > "c:\old\data\old\ibex_backup_YYYY_MM_DD\msg_log.sql"
"c:\Program Files\MySQL\MySQL Server 5.7\bin\mysqldump.exe" -u root -p archive > "c:\old\data\old\ibex_backup_YYYY_MM_DD\archive.sql"
Check the files look right and move them to long term storage. Then from a command prompt:
"c:\Program Files\MySQL\MySQL Server 5.7\bin\mysql.exe" -u root -p
Truncate the message log tables with:
truncate table msg_log.message;
truncate table archive.sample;