Pass4Test는 저희 Oracle Database 1Z0-060 (Upgrade to Oracle Database 12c) 제품을 구매한 분들이 100%통과율을 보장해드리도록 최선을 다하고 있습니다. Pass4Test를 선택한것은 Oracle Database 1Z0-060 (Upgrade to Oracle Database 12c) 시험패스와 자격증취득을 예약한것과 같습니다. Pass4Test의 믿음직한 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 plan to use the In Database Archiving feature of Oracle Database 12c, and store rows that

are inactive for over three months, in Hybrid Columnar Compressed (HCC) format.

Which three storage options support the use of HCC?

A. ASM disk groups with ASM disks consisting of Exadata Grid Disks.

B. ASM disk groups with ASM disks consisting of LUNS on any Storage Area Network array

C. ASM disk groups with ASM disks consisting of any zero padded NFS-mounted files

D. Database files stored in ZFS and accessed using conventional NFS mounts.

E. Database files stored in ZFS and accessed using the Oracle Direct NFS feature

F. Database files stored in any file system and accessed using the Oracle Direct NFS feature

G. ASM disk groups with ASM disks consisting of LUNs on Pillar Axiom Storage arrays

Answer: A,E,G

Explanation:

HCC requires the use of Oracle Storage - Exadata(A), Pillar Axiom(G)or Sun ZFS Storage Appliance

(ZFSSA).

Note: *Hybrid Columnar Compression, initially only available on Exadata, has been extended to

supportPillar Axiom and Sun ZFS Storage Appliance (ZFSSA) storage when used with Oracle

Database Enterprise Edition 11.2.0.3 and above *Oracle offers the ability to manage NFS using a

feature called Oracle Direct NFS (dNFS). Oracle Direct NFS implements NFS V3 protocol within the

Oracle database kernel itself. Oracle Direct NFS client overcomes many of the challenges associated

with using NFS with the Oracle Database with simple configuration, betterperformance than

traditional NFS clients, and offers consistent configuration across platforms.

 

NO.3 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.4 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.5 What are three purposes of the RMAN "FROM" clause?

A. to support PUSH-based active database duplication

B. to support synchronization of a standby database with the primary database in a Data

environment

C. To support PULL-based active database duplication

D. To support file restores over the network in a Data Guard environment

E. To support file recovery over the network in a Data Guard environment

Answer: B,C,E

Explanation:

E:

*With a control file autobackup, RMAN can recover the database even if the current

control file, recovery catalog, and server parameter file are inaccessible.

*RMAN uses a recovery catalog to track filenames for all database files in a Data Guard

environment. A recovery catalog is a database schema used by RMAN to store metadata

about one or more Oracle databases. The catalog also records where the online redo logs,

standby redo logs, tempfiles, archived redo logs, backup sets, and image copies are

created.

 

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 Open the database 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.