Oracle Database 1Z0-060 (Upgrade to Oracle Database 12c) 시험이 너무 어려워서 시험 볼 엄두도 나지 않는다구요? Pass4Test 덤프만 공부하신다면 IT인증시험공부고민은 이젠 그만 하셔도 됩니다. Pass4Test에서 제공해드리는 Oracle Database 1Z0-060 (Upgrade to Oracle Database 12c) 시험대비 덤프는 덤프제공사이트에서 가장 최신버전이여서 시험패스는 한방에 갑니다. Oracle Database 1Z0-060 (Upgrade to Oracle Database 12c) 시험뿐만 아니라 IT인증시험에 관한 모든 시험에 대비한 덤프를 제공해드립니다. 많은 애용 바랍니다.
NO.1 You notice that the performance of your production 24 /7 Oracle database significantly
degraded. Sometimes you are not able to connect to the instance because it hangs. You do not want
to restart the database instance.
How can you detect the cause of the degraded performance?
A. Enable Memory Access Mode, which reads performance data from SGA.
B. Use emergency monitoring to fetch data directly from SGA analysis.
C. Run Automatic Database Diagnostic Monitor (ADDM) to fetch information from the latest
Automatic Workload Repository (AWR) snapshots.
D. Use Active Session History (ASH) data and hang analysis in regular performance monitoring.
E. Run ADDM in diagnostic mode.
Answer: C
Explanation:
*In most cases, ADDM output should be the first place that a DBA looks when notified of a
performance problem. *Performance degradation of the database occurs when your database was
performing optimally in the past, such as 6 months ago, but has gradually degraded to a point
where it becomes noticeable to the users. The Automatic Workload Repository (AWR) Compare
Periods report enables you to compare database performance between two periods of time.
While an AWR report shows AWR data between two snapshots (or two points in time), the AWR
Compare Periods report shows the difference between two periods (or two AWR reports with a
total of four snapshots). Using the AWR Compare Periods report helps you to identify detailed
performance attributes and configuration settings that differ between two time periods.
Reference:Resolving Performance Degradation Over Time
NO.2 Open the database with RESETLOGS.
NO.3 Which three are true about the large poolfor anOracle database instance that supports
shared server connections?
A. Allocates memory for RMAN backup and restore operations
B. Allocates memory for shared and private SQL areas
C. Contains a cursor area for storing runtime information about cursors
D. Contains stack space
E. Contains a hash area performing hash joins of tables
Answer: A,B,C
Explanation:
The large pool can provide large memory allocations for the following:
/(B)UGA(User Global Area)for the shared server and the Oracle XA interface (used where
transactions interact with multiple databases)
/Message buffers used in the parallel execution of statements
/(A)Buffers for Recovery Manager (RMAN) I/O slaves
Note:
*large pool
Optional area in the SGA that provides large memory allocations for backup and restore
operations, I/O server processes, and session memory for the shared server and Oracle
XA.
*Oracle XA
An external interface that allows global transactions to be coordinated by a transaction
manager other than Oracle Database.
*UGA
User global area. Session memory that stores session variables, such as logon
information, and can also contain the OLAP pool.
*Configuring the Large Pool
Unlike the shared pool, the large pool does not have an LRU list(not D). Oracle Database
does not attempt to age objects out of the large pool. Consider configuring a large pool if
the database instance uses any of the following Oracle Database features:
*Shared server
In a shared server architecture, the session memory for each client process is included in
the shared pool.
*Parallel query
Parallel query uses shared pool memory to cache parallel execution message buffers.
*Recovery Manager
Recovery Manager (RMAN) uses the shared pool to cache I/O buffers during backup and restore
operations. For I/O server processes, backup, and restore operations, Oracle Database allocates
buffers that are a few hundred kilobytes in size.
NO.4 Execute the command SHUTDOWN ABORT.
Which option identifies the correct sequence to recover the SYSAUX tablespace?
A. 6, 5, 4, 7
B. 10, 1, 2, 5, 8
C. 10, 1, 2, 5, 4, 9, 8
D. 10, 1, 5, 8, 10
Answer: C
Explanation:
* Example:
While evaluating the 12c beta3 I was not able to do the recover while testing "all pdb files
lost".
Cannot close the pdb as the system datafile was missing...
So only option to recover was:
Shutdown cdb(10)
startup mount;(1)
restore pluggable database
recover pluggable databsae
alter database open;
alter pluggable database name open;
Oracle support says: You should be able to close the pdb and restore/recover the system
tablespace of PDB.
*Open the database with the RESETLOGS option after finishing recovery: SQL> ALTER DATABASE
OPEN RESETLOGS;
9. Which three are direct benefits of the multiprocess, multithreaded architecture of Oracle
Database 12c when it is enabled?
A. Reduced logical I/O
B. Reduced virtual memory utilization
C. Improved parallel Execution performance
D. Improved Serial Execution performance
E. Reduced physical I/O
F. Reduced CPU utilization
Answer: C
Explanation:
*Multiprocess and Multithreaded Oracle Database Systems
Multiprocess Oracle Database (also called multiuser Oracle Database) uses several processes to run
different parts of the Oracle Database code and additional Oracle processes for the users-either one
process for each connected user or one or more processes shared by multiple users. Most databases
are multiuser because a primary advantage of a database is managing data needed by multiple
users simultaneously.
Each process in a database instance performs a specific job. By dividing the work of the database
and applications into several processes, multiple users and applications can connect to an instance
simultaneously while the system gives good performance.
*In previous releases, Oracle processes did not run as threads on UNIX and Linux systems. Starting
in Oracle Database 12c, the multithreaded Oracle Database model enables Oracle processes to
execute as operating system threads in separate address spaces.
10. In order to exploit some new storage tiers that have been provisioned by a storage
administrator, the partitions of a large heap table must be moved to other tablespaces in your
Oracle 12c database?
Both local and global partitioned B-tree Indexes are defined on the table.
A high volume of transactions access the table during the day and a medium volume of transactions
access it at night and during weekends.
Minimal disrupt ion to availability is required.
Which three statements are true about this requirement?
A. The partitions can be moved online to new tablespaces.
B. Global indexes must be rebuilt manually after moving the partitions.
C. The partitions can be compressed in the same tablespaces.
D. The partitions can be compressed in the new tablespaces.
E. Local indexes must be rebuilt manually after moving the partitions.
Answer: A,B,D
Explanation:
A:You can create and rebuild indexes online. Therefore, you can update base tables at the same
time you are building or rebuilding indexes on that table. You can perform DML operations while
the index build is taking place, but DDL operations are not allowed. Parallel execution is not
supported when creating or rebuilding an index online.
B: Note: *Transporting and Attaching Partitions for Data Warehousing Typical enterprise data
warehouses contain one or more large fact tables. These fact tables can be partitioned by date,
making the enterprise data warehouse a historical database. You can build indexes to speed up star
queries. Oracle recommends that you build local indexes for such historically partitioned tables to
avoid rebuilding global indexes every time you drop the oldest partition from the historical database.
D:Moving (Rebuilding) Index-Organized Tables Because index-organized tables are primarily stored
in a B-tree index, you can encounter fragmentation as a consequence of incremental updates.
However, you can use the ALTER TABLE...MOVE statement to rebuild the index and reduce this
fragmentation.
NO.5 Examine the followingcommands forredefininga table withVirtual Private Database(VPD)
policies:
Which two statements are true about redefining the table?
A. All the triggers for the table are disabled without changing any of the column names or column
types in the table.
B. The primary key constraint on the EMPLOYEES table is disabled during redefinition.
C. VPD policies are copied from the original table to the new table during online redefinition.
D. You must copy the VPD policies manually from the original table to the new table during online
redefinition.
Answer: B,C
Explanation:
C (not D):CONS_VPD_AUTO Used to indicate to copy VPD policies automatically
*DBMS_RLS.ADD_POLICY /The DBMS_RLS package contains the fine-grained access control
administrative interface, which is used to implement Virtual Private Database (VPD).DBMS_RLS is
available with the Enterprise Edition only.
Note: *CONS_USE_PK and CONS_USE_ROWID are constants used as input to the "options_flag"
parameter in both the START_REDEF_TABLE Procedure and CAN_REDEF_TABLE Procedure.
CONS_USE_ROWID is used to indicate that the redefinition should be done using rowids while
CONS_USE_PK implies that the redefinition should be done using primary keys or pseudo-primary
keys (which are unique keys with all component columns having NOT NULL constraints).
*DBMS_REDEFINITION.START_REDEF_TABLE
To achieve online redefinition, incrementally maintainable local materialized views are used. These
logs keep track of the changes to the master tables and are used by the materialized views during
refresh synchronization.
*START_REDEF_TABLE Procedure Prior to calling this procedure, you must manually create an empty
interim table (in the same schema as the table to be redefined) with the desired attributes of the
post-redefinition table, and then call this procedure to initiate the redefinition.
NO.6 In your multitenant container database (CDB) containing pluggable databases (PDB), users
complain about performance degradation.
How does real-time Automatic database Diagnostic Monitor (ADDM) check performance
degradation and provide solutions?
A. It collects data from SGA and compares it with a preserved snapshot.
B. It collects data from SGA, analyzes it, and provides a report.
C. It collects data from SGA and compares it with the latest snapshot.
D. It collects data from both SGA and PGA, analyzes it, and provides a report.
Answer: B
Explanation:
Note: *The multitenant architecture enables an Oracle database to function as a multitenant
container database (CDB) that includes zero, one, or many customer-created pluggable databases
(PDBs). A PDB is a portable collection of schemas, schema objects, and nonschema objects that
appears to an Oracle Net client as a non-CDB. All Oracle databases before Oracle Database 12c were
non-CDBs. *The System Global Area (SGA) is a group of shared memory areas that are dedicated to
an Oracle "instance" (an instance is your database programs and RAM).
*The PGA (Program or Process Global Area) is a memory area (RAM) that stores data and control
information for a single process.
NO.7 Your multitenant container (CDB) containing three pluggable databases (PDBs) is running in
ARCHIVELOG mode. You find that the SYSAUX tablespace is corrupted in the root container.
The steps to recover the tablespace are as follows:
1.Mount the CDB.
2.Close all the PDBs.
3.Open the database.
4.Apply the archive redo logs.
5.Restore the data file.
6.Take the SYSAUX tablespace offline.
7.Place the SYSAUX tablespace offline.
8.Open all the PDBs with RESETLOGS.
NO.8 Your multitenant container (CDB) contains two pluggable databases(PDB), HR_PDB and
ACCOUNTS_PDB, both of which use the CDB tablespace. The temp file is called temp01.tmp.
A user issues a query on a table on one of the PDBs and receives the following error:
ERROR at line 1:
ORA-01565: error in identifying file '/u01 /app/oracle/oradata/CDB1 /temp01.tmp'
ORA-27037: unable to obtain file status
Identify two ways to rectify the error.
A. Add a new temp file to the temporary tablespace and drop the temp file that that produced the
error.
B. Shut down the database instance, restore the temp01.tmp file from the backup, and then restart
the database.
C. Take the temporary tablespace offline, recover the missing temp file by applying redo logs, and
then bring the temporary tablespace online.
D. Shutdown the database instance, restore and recover the temp file from the backup, and then
open the database with RESETLOGS.
E. Shut down the database instance and then restart the CDB and PDBs.
Answer: C,E
Explanation:
* Because temp files cannot be backed up and because no redo is ever generated for them, RMAN
never restores or recovers temp files. RMAN does track the names of temp files, but only so that it
can automatically re-create them when needed.
*If you use RMAN in a Data Guard environment, then RMAN transparently converts primary control
files to standby control files and vice versa. RMAN automatically updates file names for data files,
online redo logs, standby redo logs, and temp files when you issue RESTORE and RECOVER.