2020-08-23 17:22:36 5688 [Note] Plugin 'FEDERATED' is disabled. 2020-08-23 17:22:36 5688 [Note] InnoDB: Using atomics to ref count buffer pool pages 2020-08-23 17:22:36 5688 [Note] InnoDB: The InnoDB memory heap is disabled 2020-08-23 17:22:36 5688 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2020-08-23 17:22:36 5688 [Note] InnoDB: Memory barrier is not used 2020-08-23 17:22:36 5688 [Note] InnoDB: Compressed tables use zlib 1.2.3 2020-08-23 17:22:36 5688 [Note] InnoDB: Not using CPU crc32 instructions 2020-08-23 17:22:36 5688 [Note] InnoDB: Initializing buffer pool, size = 32.0M 2020-08-23 17:22:36 5688 [Note] InnoDB: Completed initialization of buffer pool 2020-08-23 17:22:37 5688 [Note] InnoDB: Highest supported file format is Barracuda. 2020-08-23 17:22:37 5688 [Note] InnoDB: The log sequence numbers 1771332 and 1771332 in ibdata files do not match the log sequence number 24084333 in the ib_logfiles! 2020-08-23 17:22:37 5688 [Note] InnoDB: Database was not shutdown normally! 2020-08-23 17:22:37 5688 [Note] InnoDB: Starting crash recovery. 2020-08-23 17:22:37 5688 [Note] InnoDB: Reading tablespace information from the .ibd files... 2020-08-23 17:22:38 1640 InnoDB: Operating system error number 5 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. It may also be you have created a subdirectory InnoDB: of the same name as a data file. InnoDB: Error: could not open single-table tablespace file table_a.ibd InnoDB: We do not continue the crash recovery, because the table may become InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it. InnoDB: To fix the problem and start mysqld: InnoDB: 1) If there is a permission problem in the file and mysqld cannot InnoDB: open the file, you should modify the permissions. InnoDB: 2) If the table is not needed, or you can restore it from a backup, InnoDB: then you can remove the .ibd file, and InnoDB will do a normal InnoDB: crash recovery and ignore that table. InnoDB: 3) If the file system or the disk is broken, and you cannot remove InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf InnoDB: and force InnoDB to continue crash recovery here. I'm using VM and OS is Windows Server 2016 and Uniform Server. If I set innodb_force_recovery > 0, nothing gets updated in db. I have started mysql and apache as admin, also I have tried deleting ib_logfile* and still nothing works. In the other case, even if both mysql and apache are running, the web page shows like request can't be handled and these errors will be in mysql error log. How can this be resolved?

Previously I am using **wampserver2** with "**mysql5.6.17**" version.I have many database in that version. I uninstall the wampserver and install new latest version **wampserver3.1.0_x64**. Before uninstalling my old wamp i copied all files to another drive. so i have some safe backup. Now i want all database from old wampserver. Is there any ways to do that..

Can someone tell me how to change my default storage engine to InnoDB using wamp? Currently it is MyISAM.

I have been trying to install the keyring_file.dll of MySQL 5.7.26 plugin from WAMP 3.1.9 without success. It keeps me telling in the CMD Prompt: > ERROR 1123 (HY000): Can't initialize function 'keyring_file'; Plugin initialization function failed. ...and the MySQL log states: > [ERROR] Plugin keyring_file reported: 'File 'C:/Program Files/MySQL/MySQL Server 5.7/keyring\keyring' not found (Errcode: 2 - No such file or directory)' Could somebody help me figure out what the root cause is?

I'm new in web development. I'm requesting help from all of you. My problem is: I installed WAMP server in my desktop computer. My desktop computer has a static LAN IP (192.168.0.101). I'm able to access WAMP server homepage from my other computers connected to the same network by using the LAN IP (192.168.0.101). But while I was trying to access phpMyAdmin from other computer it says: > Forbidden. You don't have permission to access/phpmyadmin/ on this server. Apache/2.4.9(Win64) PHP/5.5.12 Server at 192.168.0.101 Port 80. I also tried to connect to the MySQL database running on my desktop computer using cmd in other computer by the following code, mysql -h 192.168.0.101 -u root -p (there is no password for root user). Please help me how could I be able to access phpMyAdmin and MySQL database from other computer connected to the same network.

I installed wamp server on my PC and by default wamp server is connected to MariaDB as showed below How can i switch to MySQL? Thank you in advance for your help.

i want to create a table that have 3 column : 1. visit_times : have a unique id for every specific visitor 2. visitor_ID 3. Date i tryed to create the table as showing this code >CREATE TABLE test.table ( visit_times INT NOT NULL AUTO_INCREMENT , visitor_ID INT NOT NULL , Date VARCHAR NOT NULL , UNIQUE Unique column (visit_times, visitor_ID)) ENGINE = MyISAM; but when i store this data into the table

INSERT INTO tab(visitor_ID, date) VALUES ("1", "15/05/2021");
INSERT INTO tab(visitor_ID, date) VALUES ("1", "20/07/2021");
INSERT INTO tab(visitor_ID, date) VALUES ("2", "02/09/2021");
INSERT INTO tab(visitor_ID, date) VALUES ("3", "24/08/2021");

the result it will be like this | visit_times | visitor_ID | date | |-------------|-------------|------------| | 1 | 1 | 15/05/2021 | | 2 | 1 | 20/07/2021 | | 3 | 2 | 02/09/2021 | | 4 | 3 | 24/08/2021 | and what i actually want as result | visit_times | visitor_ID | date | |-------------|-------------|------------| | 1 | 1 | 15/05/2021 | | 2 | 1 | 20/07/2021 | | 1 | 2 | 02/09/2021 | | 1 | 3 | 24/08/2021 | Server version: 8.0.21 - MySQL Community Server - GPL I use Wampserver version 3.2.3 - 64bit Apache Version : 2.4.46

We have a Drupal site with nearly 2000 pages running on [WAMP server](http://www.wampserver.com/en/) . The pages also contain images, and flash videos embedded into them. So, they are taking some time to load under normal settings. Nearly 200-300 users are expected to use the system concurrently (the number is expected to grow later). The dev server (on our company intranet) has 16 GB RAM, and runs Windows7 - 64 bit OS. I can see that in wamp/bin/mysql/mysql5.5.16/ has files 1. my.ini 2. my-huge.ini 3. my-innodb-heavy-4G.ini I had a look into both of them, and I am not sure what is the purpose of each one of them and which one is used by my the WAMP server currently. Also, I needed to know the difference in using my-huge.ini and my-innodb-heavy-4G.ini. I have also configured Apache SOLR for indexing the search (I don't know if this is relevant). P.S : Drupal stores pages (along with the link to images and videos) into the database and images and other media are stored in folder under the site root.

2020-08-28 16:46:02 d64 InnoDB: Error: page 1 log sequence number 23113680 InnoDB: is in the future! Current system log sequence number 3181581. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. I'm using VM and OS is Windows Server 2016 and Uniform Server. MySQL stops upon this error and doesn't work until it is restarted. After restarting, it runs for some hours and stops again. How to overcome this?

I am running a Windows 10 Machine with WAMP installed. I have also a Git Bash Installed. I was trying to backup all my databases in each separate file using the code below. for DB in $(mysql -uroot -proot -e 'show databases'); do mysqldump -uroot -proot --complete-insert $DB > "$DB".sql; done; The Problem is I am **only getting incomplete dump files** for all databases **except the last one. The last dump is complete.** I have tried gzip the sql file by the following command for DB in $(mysql -uroot -proot -e 'show databases'); do mysqldump -uroot -proot --complete-insert $DB > "$DB".sql; [[ $? -eq 0 ]] && gzip "$DB".sql; done; Got the same result. Only the last database is getting dumped and gzipped completely. Note: It seems the next iteration happens before the previous finishes. I have tried using wait and sleep inside but nothing works. I have also tried using mysqldump options --single-transaction, --force, --quick but none seem to work.

I have installed wamp initailly. But now we have moved to xamp. So, I have 2 mysql folders, C:\xampp\mysql C:\wamp\bin\mysql\mysql\data Now my localhost is pointing to C:\xampp\mysql. I just wanna move everything from C:\wamp\bin\mysql\mysql to C:\xampp\mysql. When I move it I get some errors. I just need to import one database with the same permisions

I am a Python developer, working with 3 databases, configured in Master -> slave,slave style. Each slave has their own application associated with it. I am not too familiar with database administration as it relates to replication, but I do have a working scenario between the Master, and **one of the slaves** The first slave stays in synch at all times properly at this time. The second slave however, **fails on the first insert** Table creation queries, user creaiton all replicates fine, but when I input any values, **the first slave gets the record, while the second slave** does not. I tried importing the master DB to the second slave, updates to records will replicate, but new records will not. My research leads me to believe this is an issue with **autoincrement** but I have not been able to use this to fix the issue. As opposed to a hack and slash method which is not working I figured id ask here. If there is any more info I can provide, please let me know. I am on Windows. Using WAMP Server 2.5 (MySQL 5.6.17) Thanks for reading EDIT: I am using binlog_format=mixed

My WAMP MySQL has crashed 2 times the last week and I really wonder why! Once I restart the server everything works fine! Below I attach the error log of MySQL and the my.ini file! Can anyone suggest anything?? MySQL Error LOG: 2018-02-23 21:45:52 2000 [Note] Plugin 'FEDERATED' is disabled. 2018-02-23 21:45:52 2000 [Note] InnoDB: The InnoDB memory heap is disabled 2018-02-23 21:45:52 2000 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2018-02-23 21:45:52 2000 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-02-23 21:45:52 2000 [Note] InnoDB: Not using CPU crc32 instructions 2018-02-23 21:45:53 2000 [Note] InnoDB: Initializing buffer pool, size = 67.0G 2018-02-23 21:45:55 2000 [Note] InnoDB: Completed initialization of buffer pool 2018-02-23 21:45:55 2000 [Note] InnoDB: Highest supported file format is Barracuda. 2018-02-23 21:47:37 2000 [Note] InnoDB: 128 rollback segment(s) are active. 2018-02-23 21:47:37 2000 [Note] InnoDB: Waiting for purge to start 2018-02-23 21:47:38 2000 [Note] InnoDB: 5.6.12 started; log sequence number 321531472808 2018-02-23 21:48:16 2000 [Note] Server hostname (bind-address): '*'; port: 3306 2018-02-23 21:48:16 2000 [Note] IPv6 is available. 2018-02-23 21:48:16 2000 [Note] - '::' resolves to '::'; 2018-02-23 21:48:16 2000 [Note] Server socket created on IP: '::'. 2018-02-23 21:48:18 2000 [Note] Event Scheduler: Loaded 0 events 2018-02-23 21:48:18 2000 [Note] wampmysqld: ready for connections. Version: '5.6.12-log' socket: '' port: 3306 MySQL Community Server (GPL) My.ini Configuration File: [wampmysqld] port = 3306 socket = /tmp/mysql.sock key_buffer = 64M max_allowed_packet = 1000M sort_buffer_size = 512K net_buffer_length = 8K read_buffer_size = 256K read_rnd_buffer_size = 512K myisam_sort_buffer_size = 8M basedir=c:/wamp/bin/mysql/mysql5.6.12 log-error=c:/wamp/logs/mysql.log datadir=c:/wamp/bin/mysql/mysql5.6.12/data #innodb_thread_concurrency = 8 innodb_read_io_threads = 12 innodb_buffer_pool_size = 67G max_connections = 4000 max_user_connections = 0 # Disable Federated by default skip-federated [mysqldump] quick max_allowed_packet = 1000M [mysql] no-auto-rehash [isamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 4M write_buffer = 4M [myisamchk] key_buffer = 20M sort_buffer_size = 20M read_buffer = 4M write_buffer = 4M [mysqlhotcopy] interactive-timeout [mysqld] port=3306 table_definition_cache = 800 My Server Details: > RAM: 128GB RAM CPU: Intel XEON 3,5GHZ HD: 2TB HDD Any recommendation??

I am having trouble loggin on to my Wamp phpMyAdmin. Those are other questions on this site at the moment. Is there any way to make a backup of my databases through the MySQL Console? wampmanager -> MySQL -> MySQL Console **EDIT:** After looking at the info I tried (where abc is my temporary password and mystuff is my database just below root): C:\wamp64\bin\mysql\mysql5.7.9\bin>mysqldump -u root -pabc mystuff > C:\Users\Jon\Desktop\TEMP\allgames.sql It gave the following (note I am localhost:8080 and not just localhost - could that make a difference? mysqldump: [Warning] Using a password on the command line interface can be insecure. mysqldump: Got error: 2003: Can't connect to MySQL server on 'localhost' (10061) when trying to connect Looking at mysqldump --help in the command line I get the following: mysqldump Ver 10.13 Distrib 5.7.9, for Win64 (x86_64) Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Dumping structure and contents of MySQL databases and tables. Usage: mysqldump [OPTIONS] database [tables] OR mysqldump [OPTIONS] --databases [OPTIONS] DB1 [DB2 DB3...] OR mysqldump [OPTIONS] --all-databases [OPTIONS] Default options are read from the following files in the given order: C:\WINDOWS\my.ini C:\WINDOWS\my.cnf C:\my.ini C:\my.cnf C:\wamp64\bin\mysql\mysql5.7.9\my.ini C:\wamp64\bin\mysql\mysql5.7.9\my.cnf The following groups are read: mysqldump client The following options may be given as the first argument: --print-defaults Print the program argument list and exit. --no-defaults Don't read default options from any option file, except for login file. --defaults-file=# Only read default options from the given file #. --defaults-extra-file=# Read this file after the global files are read. --defaults-group-suffix=# Also read groups with concat(group, suffix) --login-path=# Read this path from the login file. -A, --all-databases Dump all the databases. This will be same as --databases with all databases selected. -Y, --all-tablespaces Dump all the tablespaces. -y, --no-tablespaces Do not dump any tablespace information. --add-drop-database Add a DROP DATABASE before each create. --add-drop-table Add a DROP TABLE before each create. (Defaults to on; use --skip-add-drop-table to disable.) --add-drop-trigger Add a DROP TRIGGER before each create. --add-locks Add locks around INSERT statements. (Defaults to on; use --skip-add-locks to disable.) --allow-keywords Allow creation of column names that are keywords. --apply-slave-statements Adds 'STOP SLAVE' prior to 'CHANGE MASTER' and 'START SLAVE' to bottom of dump. --bind-address=name IP address to bind to. --character-sets-dir=name Directory for character set files. -i, --comments Write additional information. (Defaults to on; use --skip-comments to disable.) --compatible=name Change the dump to be compatible with a given mode. By default tables are dumped in a format optimized for MySQL. Legal modes are: ansi, mysql323, mysql40, postgresql, oracle, mssql, db2, maxdb, no_key_options, no_table_options, no_field_options. One can use several modes separated by commas. Note: Requires MySQL server version 4.1.0 or higher. This option is ignored with earlier server versions. --compact Give less verbose output (useful for debugging). Disables structure comments and header/footer constructs. Enables options --skip-add-drop-table --skip-add-locks --skip-comments --skip-disable-keys --skip-set-charset. -c, --complete-insert Use complete insert statements. -C, --compress Use compression in server/client protocol. -a, --create-options Include all MySQL specific create options. (Defaults to on; use --skip-create-options to disable.) -B, --databases Dump several databases. Note the difference in usage; in this case no tables are given. All name arguments are regarded as database names. 'USE db_name;' will be included in the output. -#, --debug[=#] This is a non-debug version. Catch this and exit. --debug-check This is a non-debug version. Catch this and exit. --debug-info This is a non-debug version. Catch this and exit. --default-character-set=name Set the default character set. --delete-master-logs Delete logs on master after backup. This automatically enables --master-data. -K, --disable-keys '/*!40000 ALTER TABLE tb_name DISABLE KEYS */; and '/*!40000 ALTER TABLE tb_name ENABLE KEYS */; will be put in the output. (Defaults to on; use --skip-disable-keys to disable.) --dump-slave[=#] This causes the binary log position and filename of the master to be appended to the dumped data output. Setting the value to 1, will printit as a CHANGE MASTER command in the dumped data output; if equal to 2, that command will be prefixed with a comment symbol. This option will turn --lock-all-tables on, unless --single-transaction is specified too (in which case a global read lock is only taken a short time at the beginning of the dump - don't forget to read about --single-transaction below). In all cases any action on logs will happen at the exact moment of the dump.Option automatically turns --lock-tables off. -E, --events Dump events. -e, --extended-insert Use multiple-row INSERT syntax that include several VALUES lists. (Defaults to on; use --skip-extended-insert to disable.) --fields-terminated-by=name Fields in the output file are terminated by the given string. --fields-enclosed-by=name Fields in the output file are enclosed by the given character. --fields-optionally-enclosed-by=name Fields in the output file are optionally enclosed by the given character. --fields-escaped-by=name Fields in the output file are escaped by the given character. -F, --flush-logs Flush logs file in server before starting dump. Note that if you dump many databases at once (using the option --databases= or --all-databases), the logs will be flushed for each database dumped. The exception is when using --lock-all-tables or --master-data: in this case the logs will be flushed only once, corresponding to the moment all tables are locked. So if you want your dump and the log flush to happen at the same exact moment you should use --lock-all-tables or --master-data with --flush-logs. --flush-privileges Emit a FLUSH PRIVILEGES statement after dumping the mysql database. This option should be used any time the dump contains the mysql database and any other database that depends on the data in the mysql database for proper restore. -f, --force Continue even if we get an SQL error. -?, --help Display this help message and exit. --hex-blob Dump binary strings (BINARY, VARBINARY, BLOB) in hexadecimal format. -h, --host=name Connect to host. --ignore-error=name A comma-separated list of error numbers to be ignored if encountered during dump. --ignore-table=name Do not dump the specified table. To specify more than one table to ignore, use the directive multiple times, once for each table. Each table must be specified with both database and table names, e.g., --ignore-table=database.table. --include-master-host-port Adds 'MASTER_HOST=, MASTER_PORT=' to 'CHANGE MASTER TO..' in dump produced with --dump-slave. --insert-ignore Insert rows with INSERT IGNORE. --lines-terminated-by=name Lines in the output file are terminated by the given string. -x, --lock-all-tables Locks all tables across all databases. This is achieved by taking a global read lock for the duration of the whole dump. Automatically turns --single-transaction and --lock-tables off. -l, --lock-tables Lock all tables for read. (Defaults to on; use --skip-lock-tables to disable.) --log-error=name Append warnings and errors to given file. --master-data[=#] This causes the binary log position and filename to be appended to the output. If equal to 1, will print it as a CHANGE MASTER command; if equal to 2, that command will be prefixed with a comment symbol. This option will turn --lock-all-tables on, unless --single-transaction is specified too (in which case a global read lock is only taken a short time at the beginning of the dump; don't forget to read about --single-transaction below). In all cases, any action on logs will happen at the exact moment of the dump. Option automatically turns --lock-tables off. --max-allowed-packet=# The maximum packet length to send to or receive from server. --net-buffer-length=# The buffer size for TCP/IP and socket communication. --no-autocommit Wrap tables with autocommit/commit statements. -n, --no-create-db Suppress the CREATE DATABASE ... IF EXISTS statement that normally is output for each dumped database if --all-databases or --databases is given. -t, --no-create-info Don't write table creation info. -d, --no-data No row information. -N, --no-set-names Same as --skip-set-charset. --opt Same as --add-drop-table, --add-locks, --create-options, --quick, --extended-insert, --lock-tables, --set-charset, and --disable-keys. Enabled by default, disable with --skip-opt. --order-by-primary Sorts each table's rows by primary key, or first unique key, if such a key exists. Useful when dumping a MyISAM table to be loaded into an InnoDB table, but will make the dump itself take considerably longer. -p, --password[=name] Password to use when connecting to server. If password is not given it's solicited on the tty. -W, --pipe Use named pipes to connect to server. -P, --port=# Port number to use for connection. --protocol=name The protocol to use for connection (tcp, socket, pipe, memory). -q, --quick Don't buffer query, dump directly to stdout. (Defaults to on; use --skip-quick to disable.) -Q, --quote-names Quote table and column names with backticks (`). (Defaults to on; use --skip-quote-names to disable.) --replace Use REPLACE INTO instead of INSERT INTO. -r, --result-file=name Direct output to a given file. This option should be used in systems (e.g., DOS, Windows) that use carriage-return linefeed pairs (\r\n) to separate text lines. This option ensures that only a single newline is used. -R, --routines Dump stored routines (functions and procedures). --set-charset Add 'SET NAMES default_character_set' to the output. (Defaults to on; use --skip-set-charset to disable.) --set-gtid-purged[=name] Add 'SET @@GLOBAL.GTID_PURGED' to the output. Possible values for this option are ON, OFF and AUTO. If ON is used and GTIDs are not enabled on the server, an error is generated. If OFF is used, this option does nothing. If AUTO is used and GTIDs are enabled on the server, 'SET @@GLOBAL.GTID_PURGED' is added to the output. If GTIDs are disabled, AUTO does nothing. If no value is supplied then the default (AUTO) value will be considered. --shared-memory-base-name=name Base name of shared memory. --single-transaction Creates a consistent snapshot by dumping all tables in a single transaction. Works ONLY for tables stored in storage engines which support multiversioning (currently only InnoDB does); the dump is NOT guaranteed to be consistent for other storage engines. While a --single-transaction dump is in process, to ensure a valid dump file (correct table contents and binary log position), no other connection should use the following statements: ALTER TABLE, DROP TABLE, RENAME TABLE, TRUNCATE TABLE, as consistent snapshot is not isolated from them. Option automatically turns off --lock-tables. --dump-date Put a dump date to the end of the output. (Defaults to on; use --skip-dump-date to disable.) --skip-opt Disable --opt. Disables --add-drop-table, --add-locks, --create-options, --quick, --extended-insert, --lock-tables, --set-charset, and --disable-keys. -S, --socket=name The socket file to use for connection. --secure-auth Refuse client connecting to server if it uses old (pre-4.1.1) protocol. Deprecated. Always TRUE --ssl If set to ON, this option enforces that SSL is established before client attempts to authenticate to the server. To disable client SSL capabilities use --ssl=OFF. (Defaults to on; use --skip-ssl to disable.) --ssl-ca=name CA file in PEM format. --ssl-capath=name CA directory. --ssl-cert=name X509 cert in PEM format. --ssl-cipher=name SSL cipher to use. --ssl-key=name X509 key in PEM format. --ssl-crl=name Certificate revocation list. --ssl-crlpath=name Certificate revocation list path. --ssl-verify-server-cert Verify server's "Common Name" in its cert against hostname used when connecting. This option is disabled by default. -T, --tab=name Create tab-separated textfile for each table to given path. (Create .sql and .txt files.) NOTE: This only works if mysqldump is run on the same machine as the mysqld server. --tables Overrides option --databases (-B). --triggers Dump triggers for each dumped table. (Defaults to on; use --skip-triggers to disable.) --tz-utc SET TIME_ZONE='+00:00' at top of dump to allow dumping of TIMESTAMP data when a server has data in different time zones or data is being moved between servers with different time zones. (Defaults to on; use --skip-tz-utc to disable.) -u, --user=name User for login if not current user. -v, --verbose Print info about the various stages. -V, --version Output version information and exit. -w, --where=name Dump only selected records. Quotes are mandatory. -X, --xml Dump a database as well formed XML. --plugin-dir=name Directory for client-side plugins. --default-auth=name Default authentication client-side plugin to use. Variables (--variable-name=value) and boolean options {FALSE|TRUE} Value (after reading options) --------------------------------- ---------------------------------------- all-databases FALSE all-tablespaces FALSE no-tablespaces FALSE add-drop-database FALSE add-drop-table TRUE add-drop-trigger FALSE add-locks TRUE allow-keywords FALSE apply-slave-statements FALSE bind-address (No default value) character-sets-dir (No default value) comments TRUE compatible (No default value) compact FALSE complete-insert FALSE compress FALSE create-options TRUE databases FALSE default-character-set utf8 delete-master-logs FALSE disable-keys TRUE dump-slave 0 events FALSE extended-insert TRUE fields-terminated-by (No default value) fields-enclosed-by (No default value) fields-optionally-enclosed-by (No default value) fields-escaped-by (No default value) flush-logs FALSE flush-privileges FALSE force FALSE hex-blob FALSE host (No default value) ignore-error (No default value) include-master-host-port FALSE insert-ignore FALSE lines-terminated-by (No default value) lock-all-tables FALSE lock-tables TRUE log-error (No default value) master-data 0 max-allowed-packet 16777216 net-buffer-length 1046528 no-autocommit FALSE no-create-db FALSE no-create-info FALSE no-data FALSE order-by-primary FALSE port 3306 quick TRUE quote-names TRUE replace FALSE routines FALSE set-charset TRUE shared-memory-base-name (No default value) single-transaction FALSE dump-date TRUE socket /tmp/mysql.sock secure-auth TRUE ssl TRUE ssl-ca (No default value) ssl-capath (No default value) ssl-cert (No default value) ssl-cipher (No default value) ssl-key (No default value) ssl-crl (No default value) ssl-crlpath (No default value) ssl-verify-server-cert FALSE tab (No default value) triggers TRUE tz-utc TRUE user (No default value) verbose FALSE where (No default value) plugin-dir (No default value) default-auth (No default value) **EDIT 2:** @Vérace Yes it is running. A new error this time: C:\wamp64\bin\mysql\mysql5.7.9\bin>mysqldump -u root -pabc mystuff > C:\Users\Jon\Desktop\TEMP\allgames.sql mysqldump: [Warning] Using a password on the command line interface can be insecure. mysqldump: Got error: 1862: Your password has expired. To log in you must change it using a client that supports expired passwords. when trying to connect So I tried no password: C:\wamp64\bin\mysql\mysql5.7.9\bin>mysqldump -u root mystuff > C:\Users\Jon\Desktop\TEMP\allgames.sql mysqldump: Got error: 1045: Access denied for user 'root'@'localhost' (using password: NO) when trying to connect

I have another open question which at the moment seems to be a bit tricky to answer: https://dba.stackexchange.com/questions/186892/phpmyadmin-cannot-login-even-when-changed-password I am hoping someone can still answer it. I think one of the config files or ini files is wrong in some way. So I need to ask this question as a back up. **I have a few databases in my present install of Wamp server on Windows 10. Can I reinstall, or do a repair-install, on this Wamp server without overwriting or deleting my databases?**

I have wamp server which is installed in windows server. Since database is becoming large want to move code to other machine from there I want logon to wamp mysql. I have disabled **bind-to-address** and created new user with all permission, but unfortunately not able to connect mysql remotely. Steps I followed: CREATE USER 'user'@'x.x.x.x' IDENTIFIED BY 'password'; GRANT ALL PRIVILEGES ON *.* TO 'user'@'x.x.x.x'; Please let me what is steps do I need to follow.

I've installed WAMP on my new Windows 8 machine and for some reason when I use PHPMyAdmin to import an sql file (it's only about 5mb), it takes several minutes before timing out. And then when I check I can see it's only imported a fraction of the tables. I've tried other sql files and it's the same story. These same sql files import perfectly fine (and in a few couple of seconds) on my Windows 7 machine also running WAMP. I've since uninstalled WAMP and tried XAMPP, and the problem still exists. Even just browsing the databases with PHPMyAdmin takes a long time between page loads. I am guessing it's a problem with MySQL. Any suggestions would be helpful.

*I can ping successfully from my Windows command line to localhost and to 127.0.0.1, but attempts to connect with mysql.exe fail...* I found similar errors but their suggested solutions don't work/apply... https://stackoverflow.com/questions/19101243/error-1130-hy000-host-is-not-allowed-to-connect-to-this-mysql-server https://dba.stackexchange.com/questions/64741/host-is-not-allowed-to-connect-to-mysql https://dba.stackexchange.com/questions/135474/host-not-allowed-connectivity-to-mysql-server I'm using a Windows 7 WAMP environment (an old Zend installation) meaning its all local (connections made from localhost/127.0.0.1). All worked fine last Friday when I did an import of a database, today, I get the cannot connect error. I did not overwrite mysql database (or at least, i am pretty sure I did not), so the error has taken me a little by surprise. C:\Backups\Daily\201607>ping /n 1 localhost Pinging Silver [::1] with 32 bytes of data: Reply from ::1: timeping /n 1 127.0.0.1 Pinging 127.0.0.1 with 32 bytes of data: Reply from 127.0.0.1: bytes=32 timemysql --user=root ERROR 1130 (HY000): Host 'localhost' is not allowed to connect to this MySQL server C:\Backups\Daily\201607>mysql --user=root --host=localhost ERROR 1130 (HY000): Host 'localhost' is not allowed to connect to this MySQL server My partial extract from my.ini file: [client] port=3306 # [mysqld] # The TCP/IP Port the MySQL Server will listen on port=3306 #Path to installation directory. All paths are usually resolved relative to this. basedir="C:/Program Files (x86)/Zend/MySQL55/" #Path to the database root datadir="C:/Program Files (x86)/Zend/MySQL55/Data/" # The default character set that will be used when a new schema or table is # created and no character set is defined character-set-server = utf8 # The default storage engine that will be used when create new tables when default-storage-engine=INNODB # Set the SQL mode to strict sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION" I'm curious on what went wrong - I suspect I'm responsible for it but lack a history file to examine the error of my ways. Can anyone advise how I can fix and reconnect?

My WAMP directory accidentally get deleted by another user. Only data folder in MySQLis available. And, in that only database-folders (folders in "\bin\mysql\mysql5.6.12\data\" with name of databases) are available. **All files** including "**ibdata1**" in root of "\bin\mysql\mysql5.6.12\data\" are also deleted. The database folders contains files with below extensions only. *.frm, *.ibd and "db.opt" file. How the databases can be recovered? I already have tried to recover bdata1. But, unable to get it back. And, some database contains MYISAM also.

I have created a POS system for our corporation, in the HQ we have a wamp server with the main database, we also have more than 25 branches across the country. I will setup a wamp server on each branch, so I can access its database directly when putting wamp online. I want to make MySQL replication with all branches, so every query on any branch will affect the main database on HQ. I tried to test but found no one to explain how to do it using wamp on different PCs.