PDF (US Ltr)
- 35.1Mb
PDF (A4)
- 35.2Mb
Man Pages (TGZ)
- 256.4Kb
Man Pages (Zip)
- 361.2Kb
Info (Gzip)
- 3.4Mb
Info (Zip)
- 3.4Mb
Search Results
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-howto.html
Ideally, wait for the server to purge all binary logs, and wait for any existing backup to expire. Before proceeding, you must be sure that transactions without GTIDs do not exist anywhere in the topology. Existing backups that were made before you ... This section describes a process for configuring and starting GTID-based replication in MySQL ...
https://dev.mysql.com/doc/refman/5.7/en/replication-gtids-lifecycle.html
The gtid_purged System Variable The set of GTIDs in the gtid_purged system variable (@@GLOBAL.gtid_purged) contains the GTIDs of all the transactions that have been committed on the server, but do not exist in any binary log file on the server. You ... The life cycle of a GTID consists of the following steps: A transaction is executed and committed on the replication source ...
https://dev.mysql.com/doc/refman/5.7/en/replication-howto.html
To set up replication of a new source using the data from an existing MySQL server, see Section 16.1.2.5.4, “Setting Up Replication with Existing Data”. To add replicas to an existing replication environment, see Section 16.1.2.6, “Adding ...
https://dev.mysql.com/doc/refman/5.7/en/replication-mode-change-online-disable-gtids.html
Wait for all transactions that currently exist in any binary log to replicate to all replicas. Ideally, wait for the server to purge all binary logs that existed when step 5 was completed. Before proceeding you must be sure that GTID transactions do ... This section describes how to disable GTID transactions on servers that are already ...
https://dev.mysql.com/doc/refman/5.7/en/replication-snapshot-method.html
If the database on the source contains existing data it is necessary to copy this data to each replica. 16.1.2.4.1 Creating a Data Snapshot Using mysqldump To create a snapshot of the data in an existing source, use the mysqldump tool. There are ...
https://dev.mysql.com/doc/refman/5.7/en/reset-slave.html
(This is a condition likely to exist on a replica if you have issued a STOP SLAVE statement or if the replica is highly loaded.) For a server where GTIDs are in use (gtid_mode is ON), issuing RESET SLAVE has no effect on the GTID execution history.
https://dev.mysql.com/doc/refman/5.7/en/rewriter-query-rewrite-plugin-usage.html
Check the rewrite_rules table for rows with non-NULL message column values to see what problems exist. row *************************** Level: Note Code: 1105 Message: Query 'SELECT 10' rewritten to 'SELECT 10 + 1' by a query rewrite plugin To enable ... To enable or disable the plugin, enable or disable the rewriter_enabled system ...
https://dev.mysql.com/doc/refman/5.7/en/savepoint.html
If the ROLLBACK TO SAVEPOINT statement returns the following error, it means that no savepoint with the specified name exists: ERROR 1305 (42000): SAVEPOINT identifier does not exist The RELEASE SAVEPOINT statement removes the named savepoint from ... SAVEPOINT identifier ROLLBACK [WORK] TO [SAVEPOINT] identifier RELEASE SAVEPOINT identifier InnoDB supports the SQL statements SAVEPOINT, ROLLBACK TO SAVEPOINT, RELEASE SAVEPOINT and the optional WORK keyword for ...
https://dev.mysql.com/doc/refman/5.7/en/se-csv-repair.html
When running the CHECK TABLE statement, the CSV file is checked for validity by looking for the correct field separators, escaped fields (matching or missing quotation marks), the correct number of fields compared to the table definition and the ...
https://dev.mysql.com/doc/refman/5.7/en/solaris-installation-pkg.html
(default: all) [?,??,q]: The PKG installer installs all of the files and tools needed, and then initializes your database if one does not exist. To upgrade when using the Solaris package file format, you must remove the existing installation before ... You can install MySQL on Solaris using a binary package of the native Solaris PKG format instead of the binary tarball ...