Pass4Test의 Oracle Database 1Z0-060 (Upgrade to Oracle Database 12c)덤프는 시험패스율이 거의 100%에 달하여 많은 사랑을 받아왔습니다. 저희 사이트에서 처음 구매하는 분이라면 덤프풀질에 의문이 갈것입니다. 여러분이 신뢰가 생길수 있도록 Pass4Test에서는 Oracle Database 1Z0-060 (Upgrade to Oracle Database 12c)덤프구매 사이트에 무료샘플을 설치해두었습니다.무료샘플에는 5개이상의 문제가 있는데 구매하지 않으셔도 공부가 됩니다. Oracle Database 1Z0-060 (Upgrade to Oracle Database 12c)덤프로 Oracle Database 1Z0-060 (Upgrade to Oracle Database 12c)시험을 준비하여 한방에 시험패하세요.
NO.1 You are administering a database stored in Automatic Storage Management (ASM). You
use RMAN to back up the database and the MD_BACKUP command to back up the ASM metadata
regularly. You lost an ASM disk group DG1 due to hardware failure.
In which three ways can you re-create the lost disk group and restore the data?
A. Use the MD_RESTORE command to restore metadata for an existing disk group by passing the
existing disk group name as an input parameter and use RMAN to restore the data.
B. Use the MKDG command to restore the disk group with the same configuration as the backed-up
disk group and data on the disk group.
C. Use the MD_RESTORE command to restore the disk group with the changed disk group
specification, failure group specification, name, and other attributes and use RMAN to restore the
data.
D. Use the MKDG command to restore the disk group with the same configuration as the backed-up
disk group name and same set of disks and failure group configuration, and use RMAN to restore
the data.
E. Use the MD_RESTORE command to restore both the metadata and data for the failed disk group.
F. Use the MKDG command to add a new disk group DG1 with the same or different specifications
for failure group and other attributes and use RMAN to restore the data.
Answer: C,E,F
Explanation:
Note:
*The md_restore command allows you to restore a disk group from the metadata created
by the md_backup command.
/md_restore Command
Purpose
This command restores a disk group backup using various options that are described in
this section.
/In the restore mode md_restore, it re-create the disk group based on the backup file with
all user-defined templates with the exact configuration as the backuped disk group. There
are several options when restore the disk group
full - re-create the disk group with the exact configuration
nodg - Restores metadata in an existing disk group provided as an input parameter
newdg - Change the configuration like failure group, disk group name, etc..
*The MD_BACKUP command creates a backup file containing metadata for one or more
disk groups. By default all the mounted disk groups are included in the backup file which is
saved in the current working directory. If the name of the backup file is not specified, ASM names
the file AMBR_BACKUP_INTERMEDIATE_FILE.
NO.2 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.3 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.
NO.4 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.5 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.6 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
Answer: E
Explanation:
Type ofUnifiedauditing:
Standard
Fine Grained Audit
XS
Database Vault(not D)
Label Security(not C)
RMAN AUDIT(not B)
Data Pump(not A)
Note:
*Oracle 12c introduces Unified Auditing, which consolidates database audit records
including :-
DDL, DML, DCL
Fine Grained Auditing (DBMS_FGA)
Oracle Database Real Application Security
Oracle Recovery Manager
Oracle Database Vault
Oracle Label Security
Oracle Data Mining
Oracle Data Pump
Oracle SQL*Loader Direct Load
NO.7 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.8 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.