Proper study guides for Up to the minute Oracle Oracle Database 12c: Installation and Administration certified begins with Oracle 1z0 062 pdf preparation products which designed to deliver the High quality oracle database 12c installation and administration 1z0 062 pdf questions by making you pass the oracle database 12c installation and administration 1z0 062 pdf test at your first time. Try the free 1z0 062 pdf demo right now.
♥♥ 2017 NEW RECOMMEND ♥♥
Free VCE & PDF File for Oracle 1Z0-062 Real Exam (Full Version!)
★ Pass on Your First TRY ★ 100% Money Back Guarantee ★ Realistic Practice Exam Questions
Q11. Examine the details of the Top 5 Timed Events in the following Automatic Workloads Repository (AWR) report:
What are three possible causes for the latch-related wait events?
A. The size of the shared pool is too small.
B. Cursors are not being shared.
C. A large number COMMITS are being performed.
D. There are frequent logons and logoffs.
E. The buffers are being read into the buffer cache, but some other session is changing the buffers.
Q12. Which Oracle Database component is audited by default if the unified Auditing option is enabled?
A. Oracle Data Pump
B. Oracle Recovery Manager (RMAN)
C. Oracle Label Security
D. Oracle Database Vault
E. Oracle Real Application Security
Q13. You install a non-RAC Oracle Database. During Installation, the Oracle Universal Installer (OUI) prompts you to enter the path of the Inventory directory and also to specify an operating system group name.
Which statement is true?
A. The ORACLE_BASE base parameter is not set.
B. The installation is being performed by the root user.
C. The operating system group that is specified should have the root user as its member.
D. The operating system group that is specified must have permission to write to the inventory directory.
Providing a UNIX Group Name
If you are installing a product on a UNIX system, the Installer will also prompt you to provide the name of the group which should own the base directory.
You must choose a UNIX group name which will have permissions to update, install, and deinstall Oracle software. Members of this group must have write permissions to the base directory chosen.
Only users who belong to this group are able to install or deinstall software on this machine.
Q14. To implement Automatic Management (AMM), you set the following parameters:
When you try to start the database instance with these parameter settings, you receive the following error message:
SQL > startup
ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings, see alert log for more information.
Identify the reason the instance failed to start.
A. The PGA_AGGREGATE_TARGET parameter is set to zero.
B. The STATISTICS_LEVEL parameter is set to BASIC.
C. Both the SGA_TARGET and MEMORY_TARGET parameters are set.
D. The SGA_MAX_SIZE and SGA_TARGET parameter values are not equal.
Example: SQL> startup force ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings ORA-00848: STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or MEMORY_TARGET
Q15. Examine the parameters for your database instance:
Which three statements are true about the process of automatic optimization by using cardinality feedback?
A. The optimizer automatically changes a plan during subsequent execution of a SQL statement if there is a huge difference in optimizer estimates and execution statistics.
B. The optimizer can re optimize a query only once using cardinality feedback.
C. The optimizer enables monitoring for cardinality feedback after the first execution of a query.
D. The optimizer does not monitor cardinality feedback if dynamic sampling and multicolumn statistics are enabled.
E. After the optimizer identifies a query as a re-optimization candidate, statistics collected by the collectors are submitted to the optimizer.
Explanation: C: During the first execution of a SQL statement, an execution plan is generated as usual.
D: if multi-column statistics are not present for the relevant combination of columns, the optimizer can fall back on cardinality feedback.
(not B)* Cardinality feedback. This feature, enabled by default in 11.2, is intended to improve plans for repeated executions.
* dynamic sampling or multi-column statistics allow the optimizer to more accurately estimate selectivity of conjunctive predicates.
* OPTIMIZER_DYNAMIC_SAMPLING controls the level of dynamic sampling performed by the optimizer. Range of values. 0 to 10
* Cardinality feedback was introduced in Oracle Database 11gR2. The purpose of this feature is to automatically improve plans for queries that are executed repeatedly, for which the optimizer does not estimate cardinalities in the plan properly. The optimizer may misestimate cardinalities for a variety of reasons, such as missing or inaccurate statistics, or complex predicates. Whatever the reason for the misestimate, cardinality feedback may be able to help.
Q16. Examine the parameters for your database instance:
undo_management string AUTO
undo_retentioninteger 12 00
undo_tablespace string UNDOTBS1
You execute the following command:
SQL> ALTER TABLESPACE undotbs1 RETENTION NOGUARANTEE;
Which statement is true in this scenario?
A. Undo data is written to flashback logs after 1200 seconds.
B. Inactive undo data is retained for 1200 seconds even if subsequent transactions fail due to lack of space in the undo tablespace.
C. You can perform a Flashback Database operation only within the duration of 1200 seconds.
D. An attempt is made to keep inactive undo for 1200 seconds but transactions may overwrite the undo before that time has elapsed.
Q17. Examine the contents of SQL loader control file:
Which three statements are true regarding the SQL* Loader operation performed using the control file?
A. An EMP table is created if a table does not exist. Otherwise, if the EMP table is appended with the loaded data.
B. The SQL* Loader data file myfile1.dat has the column names for the EMP table.
C. The SQL* Loader operation fails because no record terminators are specified.
D. Field names should be the first line in the both the SQL* Loader data files.
E. The SQL* Loader operation assumes that the file must be a stream record format file with the normal carriage return string as the record terminator.
Explanation: A: The APPEND keyword tells SQL*Loader to preserve any preexisting data in the table. Other options allow you to delete preexisting data, or to fail with an error if the table is not empty to begin with.
B (not D): Note:
* SQL*Loader-00210: first data file is empty, cannot process the FIELD NAMES record
Cause: The data file listed in the next message was empty. Therefore, the FIELD NAMES
FIRST FILE directive could not be processed.
Action: Check the listed data file and fix it. Then retry the operation
* A comma-separated values (CSV) (also sometimes called character-separated values, because the separator character does not have to be a comma) file stores tabular data (numbers and text) in plain-text form. Plain text means that the file is a sequence of characters, with no data that has to be interpreted instead, as binary numbers. A CSV file consists of any number of records, separated by line breaks of some kind; each record consists of fields, separated by some other character or string, most commonly a literal comma or tab. Usually, all records have an identical sequence of fields.
* Fields with embedded commas must be quoted.
1997,Ford,E350,"Super, luxurious truck"
* SQL*Loader is a bulk loader utility used for moving data from external files into the Oracle database.
Q18. You wish to enable an audit policy for all database users, except SYS, SYSTEM, and SCOTT.
You issue the following statements:
SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SYS;
SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SYSTEM;
SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SCOTT;
For which database users is the audit policy now active?
A. All users except SYS
B. All users except SCOTT
C. All users except sys and SCOTT
D. All users except sys, system, and SCOTT
Explanation: If you run multiple AUDIT statements on the same unified audit policy but specify different EXCEPT users, then Oracle Database uses the last exception user list, not any of the users from the preceding lists. This means the effect of the earlier AUDIT POLICY ... EXCEPT statements are overridden by the latest AUDIT POLICY ... EXCEPT statement.
* The ORA_DATABASE_PARAMETER policy audits commonly used Oracle Database parameter settings. By default, this policy is not enabled.
* You can use the keyword ALL to audit all actions. The following example shows how to audit all actions on the HR.EMPLOYEES table, except actions by user pmulligan.
Example Auditing All Actions on a Table
CREATE AUDIT POLICY all_actions_on_hr_emp_pol ACTIONS ALL ON HR.EMPLOYEES;
AUDIT POLICY all_actions_on_hr_emp_pol EXCEPT pmulligan;
Reference: Oracle Database Security Guide 12c, About Enabling Unified Audit Policies
Q19. You must track all transactions that modify certain tables in the sales schema for at least three years.
Automatic undo management is enabled for the database with a retention of one day.
Which two must you do to track the transactions?
A. Enable supplemental logging for the database.
B. Specify undo retention guarantee for the database.
C. Create a Flashback Data Archive in the tablespace where the tables are stored.
D. Create a Flashback Data Archive in any suitable tablespace.
E. Enable Flashback Data Archiving for the tables that require tracking.
Explanation: E: By default, flashback archiving is disabled for any table. You can enable flashback archiving for a table if you have the FLASHBACK ARCHIVE object privilege on the Flashback Data Archive that you want to use for that table.
D: Creating a Flashback Data Archive
/ Create a Flashback Data Archive with the CREATE FLASHBACK ARCHIVE statement, specifying the following:
Name of the Flashback Data Archive
Name of the first tablespace of the Flashback Data Archive
(Optional) Maximum amount of space that the Flashback Data Archive can use in the first tablespace
/ Create a Flashback Data Archive named fla2 that uses tablespace tbs2, whose data will be retained for two years:
CREATE FLASHBACK ARCHIVE fla2 TABLESPACE tbs2 RETENTION 2 YEAR;
Q20. Which three statements are true about SQL plan directives?
A. They are tied to a specific statement or SQL ID.
B. They instruct the maintenance job to collect missing statistics or perform dynamic sampling to generate a more optimal plan.
C. They are used to gather only missing statistics.
D. They are created for a query expression where statistics are missing or the cardinality estimates by the optimizer are incorrect.
E. They instruct the optimizer to create only column group statistics.
F. Improve plan accuracy by persisting both compilation and execution statistics in the SYSAUX tablespace.
Explanation: During SQL execution, if a cardinality misestimate occurs, then the database creates SQL plan directives. During SQL compilation, the optimizer examines the query corresponding to the directive to determine whether missing extensions or histograms exist (D). The optimizer records any missing extensions. Subsequent DBMS_STATS calls collect statistics for the extensions.
The optimizer uses dynamic sampling whenever it does not have sufficient statistics corresponding to the directive. (B, not C)
E: Currently, the optimizer monitors only column groups. The optimizer does not create an extension on expressions.
Not A: SQL plan directives are not tied to a specific SQL statement or SQL ID.
* A SQL plan directive is additional information and instructions that the optimizer can use to generate a more optimal plan. For example, a SQL plan directive can instruct the optimizer to record a missing extension.