Oracle 1z0-908 - MySQL 8.0 Database Administrator

recording the order in which queries are issued

audit of all queries

point-in-time recovery

replication

logging the duration and locks for all queries

Enable GTID by executing this on the master and the slave:

SET GLOBAL GTID_ENABLED=on;

Execute this on the slave to enable GTID:

START SLAVE IO_THREAD WITH GTID;

Restart MySQL (master and slave) with these options enabled:

--gtid_mode=ON

--log-bin

--log-slave-updates

--enforce-gtid-consistency

Execute this on the slave to enable GTID:

RESET SLAVE; START SLAVE GTID_NEXT=AUTOMATIC;

On the slave, alter the MySQL master connection setting with:

ALTER channel CHANGE MASTER TO MASTER_AUTO_POSITION = 1;

On the slave, alter the MySQL master connection setting with:

CHANGE MASTER TO MASTER_AUTO_POSITION = 1;

The single query QRTi pie chart in the Query Analyzer view is based on the average execution of all statements.

It is possible to retrieve a normalized statement, but never the exact statement that was executed.

It is possible to configure the Query Analysis built-in advisor to get notified about slow query execution.

It is possible to list and analyze statements in an arbitrary graph range selection from timeseries graphs.

It is possible to import data into the Query Analyzer from heterogeneous sources, such as CSV.

ALTER USER statement

mysql_secure_installation utility

SET PASSWORD statement

mysqladmin client program

GRANT statement

Remove ib_logfile0 and ib_logfile1 files from the file system.

Execute mysqladmin flush-logs.

First run mysqld --initialize to refresh the Size of ib_logfile.

Create a new ib_logfile0 file of size 26214400.

The instance deployed on host2 is elected as the new primary instance.

The instance deployed on host3 is expelled from the cluster and must be rejoined using cluster.addInstance ('host3:3377')

The instance deployed on host3 will automatically rejoin the cluster when connectivity is re-established.

Failure of the instance deployed on host1 provokes an outage.

The issuing command cluster.switchToMuitiPrimaryMode() will fail to enable multi-primary mode.

The primary instance can be specified by using the command cluster.setPrimaryInstance(:).

on slave: --replicate-wild-ignore=example.%

on slave: --replicate-ignore-db=example

on master: --replicate-ignore-db=example

on master: --binlog-ignore-db=example

on slave: --binlog-ignore-db=example

The instance deployed on host3 must be rebuilt with a backup from the primary instance.

The cluster is running and there is at least one ONLINE instance.

The instance deployed on host3 must be synchronized from a donor deployed on host1 by using the command cluster.addInstance(‘host1:3377’).

It is possible to determine the most up-to-date instance by comparing different global transaction identifier (GTID) sets with GTID_SUBSET(set1,set2).

The active session instance is invalid and must be re-created by using the command shell.connect (‘host3:3377’).

The mysqlcheck --check --all-databases command takes table write locks while performing a series of checks.

The mysqlcheck --optimize --all-databases command reclaims free space from table files.

The mysqlcheck --repair --all-databases command can repair an InnoDB corrupted table.

The mysqlcheck command can be renamed mysqlrepair so that it repairs tables by default.

The mysqlcheck --analyze --all-databases command performs a series of checks to spot eventual table corruptions.

GRANT ALL PRIVILEGES ON ‘world’.‘city’ TO ‘tom’@’%’;

GRANT SELECT (‘code’) ON ‘world’.‘country’ TO ‘tom’@’%’;

GRANT UPDATE ON ‘world’.* TO ‘tom’@’%’;

GRANT ALL PRIVILEGES ON ‘world’.‘country’ TO ‘tom’@’%’;

GRANT UPDATE ON ‘world’.‘city’ TO ‘tom’@’%’; GRANT SELECT ON ‘world’.* TO ‘tom’@’%’;

GRANT UPDATE ON ‘world’.‘city’ TO ‘tom’@’%’; GRANT SELECT ON ‘world’.‘country’ TO ‘tom’@’%’;