多选题A MySQL replication slave is set up as follows: User all InnoDB tables Receives ROW-based binary logs Has the read-only option The replication slave has been found in an error state. You check the MySQL error log file and find the following entries: 2013-08-27 13:55:44 9056 [ERROR] Slave SQL: Could not execute Write_rows event on table test.tl; Duplicate entry ‘3’ for key’PRIMARY’ , Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event’s master log 56_master-bin.000003, end_log_pas 653, Error_code: 1062 2013-08-27 13:55:44 9056 [Warning] Salve: Duplicate entry ‘3’ for key ‘PRIMARY’ Error_code: 1062 2013-08-27 13:55:44 9056 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with “SLAVE START”, We stopped at log ‘56_masterbin.000003’ position 496 What are two possible causes for this error to occur?（）AThe slave was created with mysqldump –u root –p – skip-lock-table—all-databases /data/data.sqlBThe slave user does have INSERT, UPDATE, or DELETE permission and cannot execute the write_rows functionCFor tables with UNIQUE keys, statement-based replication must be used maintain integrityDThe root user on the slave has executed FLUSH LOGS, causing the relay-log to doublewriteEThe applications have the SUPER privilege, which allows them to update rows
多选题
A MySQL replication slave is set up as follows: User all InnoDB tables Receives ROW-based binary logs Has the read-only option The replication slave has been found in an error state. You check the MySQL error log file and find the following entries: 2013-08-27 13:55:44 9056 [ERROR] Slave SQL: Could not execute Write_rows event on table test.tl; Duplicate entry ‘3’ for key’PRIMARY’ , Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event’s master log 56_master-bin.000003, end_log_pas 653, Error_code: 1062 2013-08-27 13:55:44 9056 [Warning] Salve: Duplicate entry ‘3’ for key ‘PRIMARY’ Error_code: 1062 2013-08-27 13:55:44 9056 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with “SLAVE START”, We stopped at log ‘56_masterbin.000003’ position 496 What are two possible causes for this error to occur?（）
A
The slave was created with mysqldump –u root –p – skip-lock-table—all-databases > /data/data.sql
B
The slave user does have INSERT, UPDATE, or DELETE permission and cannot execute the write_rows function
C
For tables with UNIQUE keys, statement-based replication must be used maintain integrity
D
The root user on the slave has executed FLUSH LOGS, causing the relay-log to doublewrite
E
The applications have the SUPER privilege, which allows them to update rows
参考解析
解析：
暂无解析
相关考题：
While reviewing the MySQL error log, you see occasions where MySQL has exceeded the number of file handles allowed to it by the operating system.Which method will reduce the number of file handles in use?（）A.Activating the MySQL Enterprise thread pool pluginB.Relocating your data and log files to separate storage devicesC.Disconnecting idle localhost client sessionsD.Implementing storage engine data compression options
A user executes the statement;PURGE BINARY LOGS TO ‘mysql－bin.010‘;What is the result?() A.It deletes all binary log files, except ‘mysql-in.010‘B.It deletes all binary log files up to and including ‘mysql-bin.010‘C.It deletes all binary log files before ‘mysql-bin.010‘D.It deletes all binary log files after ‘mysql-bin.010‘
MySQL is installed on a Linux server and has the following configuration:What is the purpose of changing ownership of datadir to the ‘mysql’ user?() A.MySQL requires correct file ownership while remaining secureB.MySQL needs to be run as the root user, but file cannot be owned by itC.MySQL cannot be run as the root user
A MySQL replication slave is set up as follows: User all InnoDB tablesReceives ROW-based binary logs Has the read-only optionThe replication slave has been found in an error state.You check the MySQL error log file and find the following entries:2013-08-27 13:55:44 9056 [ERROR] Slave SQL: Could not execute Write_rows event on table test.tl; Duplicate entry ‘3’ for key’PRIMARY’ , Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event’s master log 56_master-bin.000003, end_log_pas 653, Error_code: 10622013-08-27 13:55:44 9056 [Warning] Salve: Duplicate entry ‘3’ for key ‘PRIMARY’Error_code: 10622013-08-27 13:55:44 9056 [ERROR] Error running query, slave SQL thread aborted. Fix theproblem, and restart the slave SQL thread with SLAVE START”, We stopped at log ‘56_masterbin.000003’ position 496 What are two possible causes for this error to occur?（）A.The slave was created with mysqldump –u root –p – skip-lock-table—all-databases /data/data.sqlB.The slave user does have INSERT, UPDATE, or DELETE permission and cannot execute the write_rows functionC.For tables with UNIQUE keys, statement-based replication must be used maintain integrityD.The root user on the slave has executed FLUSH LOGS, causing the relay-log to doublewriteE.The applications have the SUPER privilege, which allows them to update rows
Consider the MySQL Enterprise Audit plugin.On attempting to start the MySQL service after a crash, notice the following error: [ERROR] Plugin ‘audit_log’ init function returned error.In the audit log file, you notice the final entry:…What action should you take to fix the error and allow the service to start?（）A.Re-install the audit pluginB.Execute the command FLUSH LOGSC.Execute the command SET GLOBAL audit_log_fiush= OND.Move or rename the existing audit.log file
You have forgotten the root user account password. You decide to reset the password and execute the following:Shell＞ /etc/init.d/mysql stopShell＞ /etc/init.d/mysql start – skip-grant tablesWhich additional argument makes this operation safer?（）A.–skip-networking, to prohibit access from remote locationsB.–reset-grant-tables, to start the server with only the mysql database accessibleC.–read-only,to set all data to read-only except for super usersD.–old-passwords, to start Mysql to use the old password format while running without the grant tables
The validate_password plugin is loaded and displays the following settings in global variables: Mysql＞ SHOW VARIABLES LIKE ‘validate_password%’;When attempting to set your password, you get the following error: Mysql＞ SET PASSWORD = PASSWORD (‘Hoverl@%’);ERROR 1819 (HY000): Your password does not satisfy the current policy requirements What is the cause of the error?（）A.The password is eight characters long, but needs to exceed validate_password_length to be validB.All of the MEDIUM password policy requirements have not been honoredC.The password matches a substring Hover as a dictionary wordD.The password does not match the validate_passoword_number_count requirementE.There is no dictionary file defined, so password validation cannot work as expected
When backing up a replication slave, which three should also be backed up in addition to data?() A.The master.info and relay.info filesB.The relay log filesC.The relay index fileD.Mysql.slave_master_info tableE.Mysql.slave_relay_log_info tableF.Mysql.slave_worker_info table
You are using CTIDS in replication. You need to skip a transaction with the CTID of aaa－bbb－cccddd－eee : 3 on a slave. Which command would you execute from a Mysql prompt?() A.STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVEB.STOP SLAVE; BEGIN; SET GTID_IGNORE=aaa-bbb-ccc-ddd-eee: 3; COMMIT; START SLAVEC.STOP SLAVE; SETGTID_NEXT=aaa-bbb-ccc-ddd-eee: 3; BEGIN; COMMIT; SET GTID_NEXT=AUTOMATIC; START SLAVED.STOP SLAVE; RESET SLAVE; BEGIN; SKIP NEXT GTID; COMMIT; START SLAVE
You execute the following statement in a Microsoft Windows environment. There are no conflicts in the path name definitions.C: \＞ mysqld – install Mysql56 – defaults – file = C :\my –opts.cnf What is the expected outcome?（）A.Mysql is installed as the Windows service name Mysql56, and uses c: \my-opts.cnf as the configuration fileB.An error message is issued because – install is not a valid option for mysqldC.A running Mysql 5.6 installation has its runtime configuration updated with the server variables set in c: \my-opts.cnfD.Mysqld acts as an MSI installer and installs the Mysql 5.6 version, with the c: \my-opts.cnf configuration file
ROW-based replication has stopped working. You investigate the error log file and find the following entries: 2013-08-27 14:15:47 9056 [ERROR] Slave SQL: Could not execute Delete_rows event on table test.t1;Can‘t find record in ‘t1‘, Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event‘s master log 56_master-bin. 000003, end_log_pos 851, Error_code: 10322013-08-27 14:15:47 9056 [warning] Slave: Can‘t find record in ‘t1‘ Error_code: 10322013-08-27 14:15:47 9056 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START.We stopped at log ‘56_masterbin. 000003‘ position 684 Why did you receive this error?（）A.The slave SQL thread does not have DELETE privileges to execute on test.t1 table.sB.The table definition on the slave -litters from the masterC.Multi-threaded replication slaves can have temporary errors occurring for cross database updatesD.The slave SQL thread attempted to remove a row from the test.t1 table, but the row did not exist
You execute the following statement in a Microsoft Windows environment. There are no conflicts in the path name definitions. C: /＞ mysqld – install Mysql56 – defaults – file = C :/my –opts.cnf What is the expected outcome?（）A、Mysql is installed as the Windows service name Mysql56, and uses c: /my-opts.cnf as the configuration fileB、An error message is issued because – install is not a valid option for mysqldC、A running Mysql 5.6 installation has its runtime configuration updated with the server variables set in c: /my-opts.cnfD、Mysqld acts as an MSI installer and installs the Mysql 5.6 version, with the c: /my-opts.cnf configuration file
An existing master-slave setup is currently using a delayed replication of one hour. The master has crashed and the slave must be "rolled forward" to provide all the latest data. The SHOW SLAVE STATUS indicates the following values: RELAY_LOG_FILE =hostname-relay-bin.00004 RELAY_LOG_POS = 1383 Which command set would make the slave current?（）A、Gtid_mode must be set to AUTO during point in time recoveriesB、Mysqlbinlog ignores arguments to – exclude-gtids-it means ignore all events with GTIDsC、The server keeps track of which GTIDs have already been executed and skips thoseD、Enforce_gtid_consistency is set to ON
You are attempting to secure a MySQL server by using SSL encryption. On starting MySQL, you get this error: 130123 10:38:02 [ERROR] mysqld: unknown option '—ssl' What is the cause of the error?（）A、The — ssl level was not specifiedB、The server was not started with the – enable–ssl-plugin optionC、— ssl is not a valid server optionD、The mysqld binary was not compiled with SSL supportE、The server's SSL certificate was invalid
A user executes the statement; PURGE BINARY LOGS TO 'mysql-bin.010'; What is the result?（）A、It deletes all binary log files, except 'mysql-in.010'B、It deletes all binary log files up to and including 'mysql-bin.010'C、It deletes all binary log files before 'mysql-bin.010'D、It deletes all binary log files after 'mysql-bin.010'
You are using replication and the binary log files on your master server consume a lot of disk space. Which two steps should you perform to safely remove some of the older binary log files?（）A、Use the command PURGE BINARY LOGS and specify a binary log file name or a date and time to remove unused filesB、Execute the PURGE BINARY LOGE NOT USED commandC、Remove all of the binary log files that have a modification date earlier than todayD、Edit the .index file to remove the files you want to deleteE、Ensure that none of the attached slaves are using any of the binary logs you want to delete
While reviewing the MySQL error log, you see occasions where MySQL has exceeded the number of file handles allowed to it by the operating system. Which method will reduce the number of file handles in use?（）A、Activating the MySQL Enterprise thread pool pluginB、Relocating your data and log files to separate storage devicesC、Disconnecting idle localhost client sessionsD、Implementing storage engine data compression options
An existing master-slave setup is currently using a delayed replication of one hour. The master has crashed and the slave must be "rolled forward" to provide all the latest data. The SHOW SLAVE STATUS indicates the following values: RELAY_LOG_FILE =hostname-relay-bin.00004 RELAY_LOG_POS = 1383 Which command set would make the slave current?（）A、STOP SLAVE; CHANGE MASTER TO MASTER_DELAY =0, RELAY_LOG_FILE = 'hostnamerelay- bin.00004' , RELAY_LOG_POS= 1383B、STOP SLAVE; CHANGE MASTER TO RELAY_LOG_FILE = 'hostname-relay-bin.00004', RELAY_LOG_POS = 1383C、STOP SLAVE; CHANGE MASTER TO MASTER_DELAY=0; START SLAVED、STOP SLAVE; SET GLOBAL master_delay =0; START SLAVE
You have forgotten the root user account password. You decide to reset the password and execute the following: Shell＞ /etc/init.d/mysql stop Shell＞ /etc/init.d/mysql start – skip-grant tables Which additional argument makes this operation safer?（）A、–skip-networking, to prohibit access from remote locationsB、–reset-grant-tables, to start the server with only the mysql database accessibleC、–read-only,to set all data to read-only except for super usersD、–old-passwords, to start Mysql to use the old password format while running without the grant tables
ROW-based replication has stopped working. You investigate the error log file and find the following entries: 2013-08-27 14:15:47 9056 [ERROR] Slave SQL: Could not execute Delete_rows event on table test.t1; Can't find record in 't1', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log 56_master-bin. 000003, end_log_pos 851, Error_code: 1032 2013-08-27 14:15:47 9056 [warning] Slave: Can't find record in 't1' Error_code: 1032 2013-08-27 14:15:47 9056 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log '56_masterbin. 000003' position 684 Why did you receive this error?（）A、The slave SQL thread does not have DELETE privileges to execute on test.t1 table.sB、The table definition on the slave -litters from the masterC、Multi-threaded replication slaves can have temporary errors occurring for cross database updatesD、The slave SQL thread attempted to remove a row from the test.t1 table, but the row did not exist
You are using CTIDS in replication. You need to skip a transaction with the CTID of aaa-bbb-cccddd-eee : 3 on a slave. Which command would you execute from a Mysql prompt?（）A、STOP SLAVE; SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVEB、STOP SLAVE; BEGIN; SET GTID_IGNORE="aaa-bbb-ccc-ddd-eee: 3"; COMMIT; START SLAVEC、STOP SLAVE; SETGTID_NEXT="aaa-bbb-ccc-ddd-eee: 3"; BEGIN; COMMIT; SET GTID_NEXT="AUTOMATIC"; START SLAVED、STOP SLAVE; RESET SLAVE; BEGIN; SKIP NEXT GTID; COMMIT; START SLAVE
Which statement is true about FLUSH LOGS command?（）A、It requires the RELOAD, FILE, and DROP privilegesB、It closes and reopens all log filesC、It closes and sends binary log files to slave serversD、It flushes dirty pages in the buffer pool to the REDO logs
单选题You have forgotten the root user account password. You decide to reset the password and execute the following: Shell＞ /etc/init.d/mysql stop Shell＞ /etc/init.d/mysql start – skip-grant tables Which additional argument makes this operation safer?（）A–skip-networking, to prohibit access from remote locationsB–reset-grant-tables, to start the server with only the mysql database accessibleC–read-only,to set all data to read-only except for super usersD–old-passwords, to start Mysql to use the old password format while running without the grant tables
多选题A MySQL replication slave is set up as follows: User all InnoDB tables Receives ROW-based binary logs Has the read-only option The replication slave has been found in an error state. You check the MySQL error log file and find the following entries: 2013-08-27 13:55:44 9056 [ERROR] Slave SQL: Could not execute Write_rows event on table test.tl; Duplicate entry ‘3’ for key’PRIMARY’ , Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event’s master log 56_master-bin.000003, end_log_pas 653, Error_code: 1062 2013-08-27 13:55:44 9056 [Warning] Salve: Duplicate entry ‘3’ for key ‘PRIMARY’ Error_code: 1062 2013-08-27 13:55:44 9056 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with “SLAVE START”, We stopped at log ‘56_masterbin.000003’ position 496 What are two possible causes for this error to occur?（）AThe slave was created with mysqldump –u root –p – skip-lock-table—all-databases /data/data.sqlBThe slave user does have INSERT, UPDATE, or DELETE permission and cannot execute the write_rows functionCFor tables with UNIQUE keys, statement-based replication must be used maintain integrityDThe root user on the slave has executed FLUSH LOGS, causing the relay-log to doublewriteEThe applications have the SUPER privilege, which allows them to update rows
多选题When backing up a replication slave, which three should also be backed up in addition to data?（）AThe master.info and relay.info filesBThe relay log filesCThe relay index fileDMysql.slave_master_info tableEMysql.slave_relay_log_info tableFMysql.slave_worker_info table
单选题You execute the following statement in a Microsoft Windows environment. There are no conflicts in the path name definitions. C: /＞ mysqld – install Mysql56 – defaults – file = C :/my –opts.cnf What is the expected outcome?（）AMysql is installed as the Windows service name Mysql56, and uses c: /my-opts.cnf as the configuration fileBAn error message is issued because – install is not a valid option for mysqldCA running Mysql 5.6 installation has its runtime configuration updated with the server variables set in c: /my-opts.cnfDMysqld acts as an MSI installer and installs the Mysql 5.6 version, with the c: /my-opts.cnf configuration file
多选题You are using replication and the binary log files on your master server consume a lot of disk space. Which two steps should you perform to safely remove some of the older binary log files?（）AUse the command PURGE BINARY LOGS and specify a binary log file name or a date and time to remove unused filesBExecute the PURGE BINARY LOGE NOT USED commandCRemove all of the binary log files that have a modification date earlier than todayDEdit the .index file to remove the files you want to deleteEEnsure that none of the attached slaves are using any of the binary logs you want to delete