[2016-6-NEW]1Z0-060 Dumps Questions New Updated By Braindump2go[NQ31-NQ40]

2016 June Oracle Official 1Z0-060: Upgrade to Oracle Database 12c Exam Questions New Updated Today in Braindump2go.com. 100% 1Z0-060 Exam Pass Guaranteed!


You upgrade your Oracle database in a multiprocessor environment. As a recommended you execute the following script:
SQL > @utlrp.sql
Which two actions does the script perform?

A.    Parallel compilation of only the stored PL/SQL code
B.    Sequential recompilation of only the stored PL/SQL code
C.    Parallel recompilation of any stored PL/SQL code
D.    Sequential recompilation of any stored PL/SQL code
E.    Parallel recompilation of Java code
F.    Sequential recompilation of Java code

Answer: CE
utlrp.sql and utlprp.sql
The utlrp.sql and utlprp.sql scripts are provided by Oracle to recompile all invalid objects in the database. They are typically run after major database changes such as upgrades or patches. They are located in the $ORACLE_HOME/rdbms/admin directory and provide a wrapper on the UTL_RECOMP package. The utlrp.sql script simply calls the utlprp.sql script with a command line parameter of “0”. The utlprp.sql accepts a single integer parameter that indicates the level of parallelism as follows.
0 – The level of parallelism is derived based on the CPU_COUNT parameter.
1 – The recompilation is run serially, one object at a time.
N – The recompilation is run in parallel with “N” number of threads. Both scripts must be run as the SYS user, or another user with SYSDBA, to work correctly.

Which statement is true concerning dropping a pluggable database (PDB)?

A.    The PDB must be open in read-only mode.
B.    The PDB must be in mount state.
C.    The PDB must be unplugged.
D.    The PDB data files are always removed from disk.
E.    A dropped PDB can never be plugged back into a multitenant container database (CDB).

Answer: B
Possible to drop a PDB without unplugging it. The PDB must be in MOUNT stage.

You notice a high number of waits for the db file scattered read and db file sequential read events in the recent Automatic Database Diagnostic Monitor (ADDM) report. After further investigation, you find that queries are performing too many full table scans and indexes are not being used even though the filter columns are indexed.
Identify three possible reasons for this.

A.    Missing or stale histogram statistics
B.    Undersized shared pool
C.    High clustering factor for the indexes
D.    High value for the DB_FILE_MULTIBLOCK_READ_COUNT parameter
E.    Oversized buffer cache

Answer: ACD
D:DB_FILE_MULTIBLOCK_READ_COUNT is one of the parameters you can use to minimize I/O during table scans. It specifies the maximum number of blocks read in one I/O operation during a sequential scan. The total number of I/Os needed to perform a full table scan depends on such factors as the size of the table, the multiblock read count, and whether parallel execution is being utilized for the operation.

Which three features work together, to allow a SQL statement to have different cursors for the same statement based on different selectivity ranges?

A.    Bind Variable Peeking
B.    SQL Plan Baselines
C.    Adaptive Cursor Sharing
D.    Bind variable used in a SQL statement
E.    Literals in aSQL statement

Answer: ACE
*In bind variable peeking (also known as bind peeking), the optimizer looks at the value in a bind variable when the database performs a hard parse of a statement.
When a query uses literals, the optimizer can use the literal values to find the best plan. However, when a query uses bind variables, the optimizer must select the best plan without the presence of literals in the SQL text. This task can be extremely difficult. By peeking at bind values the optimizer can determine the selectivity of a WHERE clause condition as if literals had been used, thereby improving the plan.
C:Oracle 11g/12guses Adaptive Cursor Sharing to solve this problem by allowing the server to compare the effectiveness of execution plans between executions with different bind variable values. If it notices suboptimal plans, it allows certain bind variable values, or ranges of values, to use alternate execution plans for the same statement. This functionality requires no additional configuration.

You notice a performance change in your production Oracle 12c database. You want to know which change caused this performance difference.
Which method or feature should you use?

A.    Compare Period ADDM report
B.    AWR Compare Period report
C.    Active Session History (ASH) report
D.    Taking a new snapshot and comparing it with a preserved snapshot

Answer: A
You may have noticed a performance change on a production system and would like to know why, or you may have implemented a change to a production system and want to know the effect of the change, such as increased concurrency waits.
The Compare Period ADDM compares the performance of the database server in two time periods, and returns a report describing the performance changes and the root origin of the changes

You want to capture column group usage and gather extended statistics for better cardinality estimates for the CUSTOMERS table in the SH schema.
Examine the following steps:
2. Execute the DBMS_STATS.SEED_COL_USAGE (null, `SH’, 500) procedure.
3. Execute the required queries on the CUSTOMERS table.
Identify the correct sequence of steps.

A.    3, 2, 1, 4
B.    2, 3, 4, 1
C.    4, 1, 3, 2
D.    3, 2, 4, 1

Answer: B
Step1(2). Seed column usage
Oracle must observe a representative workload, in order to determine the appropriate column groups. Using the new procedure DBMS_STATS.SEED_COL_USAGE, you tell Oracle how long it should observe the workload.
Step 2: (3) You don’t need to execute all of the queries in your work during this window.
You can simply run explain plan for some of your longer running queries to ensure column group information is recorded for these queries.
Step 3. (1) Create the column groups
At this point you can get Oracle to automatically create the column groups for each of the tables based on the usage information captured during the monitoring window. You simply have to call the DBMS_STATS.CREATE_EXTENDED_STATS function for each table.This function requires just two arguments, the schema name and the table name. From then on, statistics will be maintained for each column group whenever statistics are gathered on the table.
*DBMS_STATS.REPORT_COL_USAGE reports column usage information and records all the SQL operations the database has processed for a given object.
*The Oracle SQL optimizer has always been ignorant of the implied relationships between data columns within the same table. While the optimizer has traditionally analyzed the distribution of values within a column, he does not collect value-based relationships between columns. *Creating extended statisticsHere are the steps to create extended statistics for related table columns withdbms_stats.created_extended_stats:
1 – The first step is to create column histograms for the related columns.
2 – Next, we run dbms_stats.create_extended_stats to relate the columns together.
Unlike a traditional procedure that is invoked via an execute (“exec”) statement, Oracle extended statistics are created via a select statement.

Which three statements are true about Automatic Workload Repository (AWR)?

A.    All AWR tables belong to the SYSTEM schema.
B.    The AWR data is stored in memory and in the database.
C.    The snapshots collected by AWR are used by the self-tuning components in the database
D.    AWR computes time model statistics based on time usage for activities, which are displayed in
the v$SYS time model and V$SESS_TIME_MODEL views.
E.    AWR contains systemwide tracing and logging information.

Answer: BCD
The statistics collected and processed by AWR include:
Time model statistics based on time usage for activities, displayed in the V$SYS_TIME_MODEL and V$SESS_TIME_MODEL views

You upgraded your database from pre-12c to a multitenant container database (CDB) containing pluggable databases (PDBs).
Examine the query and its output:
Which two tasks must you perform to add users with SYSBACKUP, SYSDG, and SYSKM privilege to the password file?

A.    Assign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.
B.    Grant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.
C.    Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the FORCE
argument set to Yes.
D.    Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE
arguments set to Yes.
E.    Re-create the password file in the Oracle Database 12c format.

Answer: BD
/You can create a database password file using the password file creation utility, ORAPWD.
The syntax of the ORAPWD command is as follows:
orapwd FILE=filename [ENTRIES=numusers] [FORCE={y|n}] [ASM={y|n}] [DBUNIQUENAME=dbname] [FORMAT={12|legacy}] [SYSBACKUP={y|n}] [SYSDG={y|n}] [SYSKM={y|n}] [DELETE={y|n}] [INPUT_FILE=input-fname]
force – whether to overwrite existing file (optional),
/ 12c:V$PWFILE_USERS lists all users in the password file, and indicates whether the user has been granted the SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, and SYSKM privileges.
/ 10c:sts users who have been granted SYSDBA and SYSOPER privileges as derived from the password file.
USERNAMEVARCHAR2(30)The name of the user that is contained in the password file SYSDBAVARCHAR2(5)If TRUE, the user can connect with SYSDBA privileges SYSOPERVARCHAR2(5)If TRUE, the user can connect with SYSOPER privileges
not E: The format of the v$PWFILE_users file is already in 12c format.

An application accesses a small lookup table frequently.
You notice that the required data blocks are getting aged out of the default buffer cache.
How would you guarantee that the blocks for the table never age out?

A.    Configure the KEEP buffer pool and alter the table with the corresponding storage clause.
B.    Increase the database buffer cache size.
C.    Configure the RECYCLE bufferpool and alter the table with the corresponding storage clause.
D.    Configure Automata Shared Memory Management.
E.    Configure Automatic Memory Management-

Answer: A
Schema objects are referenced with varying usage patterns; therefore, their cache behavior may be quite different. Multiple buffer pools enable you to address these differences.
You can use a KEEP buffer pool to maintain objects in the buffer cache and a RECYCLE buffer pool to prevent objects from consuming unnecessary space in the cache. When an object is allocated to a cache, all blocks from that object are placed in that cache. Oracle maintains a DEFAULT buffer pool for objects that have not been assigned to one of the buffer pools.

You conned using SQL Plus to the root container of a multitenant container database (CDB) with SYSDBA privilege.
The CDB has several pluggable databases (PDBs) open in the read/write mode.
There are ongoing transactions in both the CDB and PDBs.
What happens alter issuing the SHUTDOWN TRANSACTIONAL statement?

A.    The shutdown proceeds immediately.
The shutdown proceeds as soon as all transactions in the PDBs are either committed or rolled hack.
B.    The shutdown proceeds as soon as all transactions in the CDB are either committed or rolled back.
C.    The shutdown proceeds as soon as all transactions in both the CDB and PDBs are either committed
or rolled back.
D.    The statement results in an error because there are open PDBs.

Answer: B
Shuts down a currently running Oracle Database instance, optionally closing and dismounting a database. If the current database is a pluggable database, only the pluggable database is closed.
The consolidated instance continues to run.
Shutdown commands that wait for current calls to complete or users to disconnect such as SHUTDOWN NORMAL and SHUTDOWN TRANSACTIONAL have a time limit that the SHUTDOWN command will wait. If all events blocking the shutdown have not occurred within the time limit, the shutdown command cancels with the following message:
ORA-01013: user requested cancel of current operation
*If logged into a CDB, shutdown closes the CDB instance.
To shutdown a CDB or non CDB, you must be connected to the CDB or non CDB instance that you want to close, and then enter
Database closed.
Database dismounted.
Oracle instance shut down.
To shutdown a PDB, you must log into the PDB to issue the SHUTDOWN command.
Pluggable Database closed.
*Prerequisites for PDB Shutdown
When the current container is a pluggable database (PDB), the SHUTDOWN command can only be used if:
The current user has SYSDBA, SYSOPER, SYSBACKUP, or SYSDG system privilege.
The privilege is either commonly granted or locally granted in the PDB.
The current user exercises the privilege using AS SYSDBA, AS SYSOPER, AS SYSBACKUP, or AS SYSDG at connect time.
To close a PDB, the PDB must be open.

2016 Valid Braindump2go Oracle 1Z0-060 Study Materials:


1.| Braindump2go Latest 1Z0-060 PDF and 1Z0-060 VCE Dumps with New 161q 1Z0-060 Exam Questions: http://www.braindump2go.com/1z0-060.html

[100% Exam Pass Guaranteed!]


2.| Braindump2go New 1Z0-060 Exam Questions and Answers – Google Drive: https://drive.google.com/folderview?id=0B75b5xYLjSSNWm1lN2tlY1ZKVVk&usp=sharing


MORE Practice is the Most Important IF You want to PASS Oracle 1Z0-060 Exam 100%!
————— Braindump2go.com
————— Pass All IT Exams at the first Try!


Braindump2go Testking Pass4sure Actualtests Others
$99.99 $124.99 $125.99 $189 $29.99/$49.99
Real Questions
Error Correction
Printable PDF
Premium VCE
VCE Simulator
One Time Purchase
Instant Download
Unlimited Install
100% Pass Guarantee
100% Money Back