File Info
| Exam | MySQL 5.6 Database Administrator |
| Number | 1z0-883 |
| File Name | Oracle.1z0-883.CertDumps.2018-07-24.30q.vcex |
| Size | 42 KB |
| Posted | Jul 24, 2018 |
| Download | Oracle.1z0-883.CertDumps.2018-07-24.30q.vcex |
How to open VCEX & EXAM Files?
Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.
Coupon: MASTEREXAM
With discount: 20%
Demo Questions
Question 1
Consider the following statement on a RANGE partitioned table :
ALTER TABLE orders DROP PARTITION p1, p3;
What is the outcome of executing the above statement?
- Only the first partition (p1) will be dropped as only one can be dropped at any time.
- All data in p1 and p3 partitions are removed, but the table definition remains unchanged.
- A syntax error will result as you cannot specify more than one partition in the same statement.
- All data in pi and p3 partitions are removed and the table definition is changed.
Correct answer: B
Explanation:
http://docs.oracle.com/cd/F49540_01/DOC/server.815/a67772/partiti.htm http://docs.oracle.com/cd/F49540_01/DOC/server.815/a67772/partiti.htm
Question 2
You inherit a legacy database system when the previous DBA, Bob, leaves the company. You are notified that users are getting the following error:
mysql> CALL film_in_stock (40, 2, @count); ERROR 1449 (HY000):
The user specified as a definer (‘bon’@’localhost’) does not exist.
How would you identify all stored procedures that pose the same problem?
- Execute SELECT * FROM mysql.routines WHERE DEFINER=’bob@localhost’;.
- Execute SHOW ROUTINES WHERE DEFINER=’bob@localhost’.
- Execute SELECT * FROM INFORMATION_SCHEMA. ROUTINES WHERE DEFINER=’bob@localhost’;.
- Execute SELECT * FROM INFORMATION_SCHEMA. PROCESSLIST WHERE USER=’bob’ and HOST=’ localhost’;.
- Examine the Mysql error log for other ERROR 1449 messages.
Correct answer: D
Question 3
A simple master-to-slave replication is currently being used. The following information is extracted from the SHOW SLAVE STATUS output :
Last_SQL_Error: Error 'Duplicate entry '8' for key 'PRIMARY' ' on query.
Default database: 'mydb'. Query : 'insert into mytable VALUES ('8','George') ' Skip_Counter : 0
Retrieved _Gtid_Set : 38f32e23480a7-32a1-c323f78067fd37821: 1-8 Auto _Position: 1
You execute a “SHOW CREATE TABLE mytable” on the slave :
CREATE TABLE ‘mytable’ (
‘ID’ int(11) NOT NULL DEFAULT ‘0’, ‘name’ char(10) DEFAULT NULL, PRIMARY KEY (‘ID’)
)
The table mytable on the slave contains the following :
You have issued a STOP SLAVE command. One or more statements are required before you can issue a START SLAVE command to resolve the duplicate key error.
Which statement should be used?
- SET GLOBAL SQL_SKIP_SLAVE_COUNTER=1
- SET GTID_NEXT=”CONSISTENCY”; BEGIN; COMMIT; SET GTID_NEXT=” AUTOMATIC’;
- SET GLOBAL enforce_gtid_consistency=ON
- SET GTID_EXECUTED=”38f32e23480a7-32a1-c323f78067fd37821 : 9”;
- SET GTID_NEXT=”38f32e23480a7-32a1-c323f78067fd37821 : 9”; BEGIN; COMMIT; SET GTID_NEXT=”AUTOMATIC”;
Correct answer: A
Question 4
When designing an InnoDB table, identify an advantage of using the BIT datatype Instead of one of the integer datatypes.
- BIT columns are written by InnoDB at the head of the row, meaning they are always the first to beretrieved.
- Multiple BIT columns pack tightly into a row, using less space.
- BIT (8) takes less space than eight TINYINT fields.
- The BIT columns can be manipulated with the bitwise operators &, |, ~, ^, <<, and >>. The other integer types cannot.
Correct answer: B
Question 5
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
Why did you receive this error?
- The slave SQL thread does not have DELETE privileges to execute on test.t1 table.s
- The table definition on the slave -litters from the master.
- Multi-threaded replication slaves can have temporary errors occurring for cross database updates.
- The slave SQL thread attempted to remove a row from the test.t1 table, but the row did not exist.
Correct answer: D
