[2016-6-NEW]Oracle 1Z0-060 PDF and VCE Dumps Free 161q Offered by Braindump2go for Free Downloading[NQ51-NQ60]
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!
NEW QUESTION 51 – NEW QUESTION 60:
You executed a DROP USER CASCADE on an Oracle 11g release 1 database and immediately realized that you forgot to copy the OCA.EXAM_RESULTS table to the OCP schema.
The RECYCLE_BIN enabled before the DROP USER was executed and the OCP user has been granted the FLASHBACK ANY TABLE system privilege.
What is the quickest way to recover the contents of the OCA.EXAM_RESULTS table to the OCP schema?
A. Execute FLASHBACK TABLE OCA.EXAM_RESULTS TO BEFORE DROP RENAME TO
OCP.EXAM_RESULTS; connected as SYSTEM.
B. Recover the table using traditional Tablespace Point In Time Recovery.
C. Recover the table using Automated Tablespace Point In Time Recovery.
D. Recovery the table sing Database Point In Time Recovery.
E. Execute FLASHBACK TABLE OCA.EXAM_RESULTS TO BEFORE DROP RENAME TO
EXAM_RESULTS; connected as the OCP user.
RMAN tablespace point-in-time recovery (TSPITR).
Recovery Manager (RMAN) TSPITR enables quick recovery of one or more tablespaces in a
database to an earlier time without affecting the rest of the tablespaces and objects in the
Fully Automated (the default)
In this mode, RMAN manages the entire TSPITR process including the auxiliary instance. You
specify the tablespaces of the recovery set, an auxiliary destination, the target time, and you allow RMAN to manage all other aspects of TSPITR.
The default mode is recommended unless you specifically need more control over the location of
recovery set files after TSPITR, auxiliary set files during TSPITR, channel settings and parameters or some other aspect of your auxiliary instance.
In your multitenant container database (CDB) containing pluggable database (PDBs), the HR user executes the following commands to create and grant privileges on a procedure:
CREATE OR REPLACE PROCEDURE create_test_v (v_emp_id NUMBER, v_ename
VARCHAR2, v_SALARY NUMBER, v_dept_id NUMBER)
INSERT INTO hr.test VALUES (V_emp_id, V_ename, V_salary, V_dept_id);
GRANT EXECUTE ON CREATE_TEST TO john, jim, smith, king;
How can you prevent users having the EXECUTE privilege on the CREATE_TEST procedure from inserting values into tables on which they do not have any privileges?
A. Create the CREATE_TEST procedure with definer’s rights.
B. Grant the EXECUTE privilege to users with GRANT OPTION on the CREATE_TEST procedure.
C. Create the CREATE_TEST procedure with invoker’s rights.
D. Create the CREATE_TEST procedure as part of a package and grant users the EXECUTE privilege
If a program unit does not need to be executed with the escalated privileges of the definer, you should specify that the program unit executes with the privileges of the caller, also known as the invoker. Invoker’s rights can mitigate the risk of SQL injection.
Not A: By default, stored procedures and SQL methods execute with the privileges of their owner, not their current user. Such definer-rights subprograms are bound to the schema in which they reside.
not B:Using the GRANT option, a user can grant an Object privilege to another user or to PUBLIC.
You created a new database using the “create database” statement without specifying the “ENABLE PLUGGABLE” clause.
What are two effects of not using the “ENABLE PLUGGABLE database” clause?
A. The database is created as a non-CDB and can never contain a PDB.
B. The database is treated as a PDB and must be plugged into an existing multitenant container
C. The database is created as a non-CDB and can never be plugged into a CDB.
D. The database is created as a non-CDB but can be plugged into an existing CDB.
E. The database is created as a non-CDB but will become a CDB whenever the first PDB is plugged in.
A (not B,not E): The CREATE DATABASE … ENABLE PLUGGABLE DATABASE SQL statement creates a new CDB. If you do not specify the ENABLE PLUGGABLE DATABASE clause, then the newly created database is a non-CDB and can never contain PDBs.
D: You can create a PDB by plugging in a Non-CDB as a PDB. The following graphic depicts the options for creating a PDB:
Description of cncpt358.png follows
Not E:For the duration of its existence, a database is either a CDB or a non-CDB. You cannot transform a non-CDB into a CDB or vice versa. You must define a database as a CDB at creation, and then create PDBs within this CDB.
What is the effect of specifying the “ENABLE PLUGGABLE DATABASE” clause in a “CREATE DATABASE” statement?
A. It will create a multitenant container database (CDB) with only the root opened.
B. It will create a CDB with root opened and seed read only.
C. It will create a CDB with root and seed opened and one PDB mounted.
D. It will create a CDB that must be plugged into an existing CDB.
E. It will create a CDB with root opened and seed mounted.
*The CREATE DATABASE … ENABLE PLUGGABLE DATABASE SQL statement creates a new CDB. If you do not specify the ENABLE PLUGGABLE DATABASE clause, then the newly created database is a non-CDB and can never contain PDBs.
Along with the root (CDB$ROOT), Oracle Database automatically creates a seed PDB (PDB$SEED). The following graphic shows a newly created CDB:
*Creating a PDB
Rather than constructing the data dictionary tables that define an empty PDB from scratch, and then populating its Obj$ and Dependency$ tables, the empty PDB is created when the CDB is created. (Here, we use empty to mean containing no customer-created artifacts.) It is referred to as the seed PDB and has the name PDB$Seed. Every CDB non-negotiably contains a seed PDB; it is non-negotiably always open in read-only mode. This has no conceptual significance; rather, it is just an optimization device. The create PDB operation is implemented as a special case of the clone PDB operation.
You have installed two 64G flash devices to support the Database Smart Flash Cache feature on your database server that is running on Oracle Linux.
You have set the DB_SMART_FLASH_FILE parameter:
DB_FLASH_CACHE_FILE= `/dev/flash_device_1 `,’ /dev/flash_device_2′
How should the DB_FLASH_CACHE_SIZE be configured to use both devices?
A. Set DB_FLASH_CACHE_ZISE = 64G.
B. Set DB_FLASH_CACHE_ZISE = 64G, 64G
C. Set DB_FLASH_CACHE_ZISE = 128G.
D. DB_FLASH_CACHE_SIZE is automatically configured by the instance at startup.
* Smart Flash Cache concept is not new in Oracle 12C – DB Smart Flash Cache in Oracle 11g.
In this release Oracle has made changes related to both initialization parameters used by DB Smart Flash cache. Now you can define many files|devices and its sizes for “Database Smart Flash Cache” area. In previous releases only one file|device could be defined.
DB_FLASH_CACHE_FILE = /dev/sda, /dev/sdb, /dev/sdc
DB_FLASH_CACHE_SIZE = 32G, 32G, 64G
So above settings defines 3 devices which will be in use by “DB Smart Flash Cache”
/dev/sda ?size 32G
/dev/sdb ?size 32G
/dev/sdc ?size 64G
New view V$FLASHFILESTAT ?it’s used to determine the cumulative latency and read counts of each file|device and compute the average latency
Examine the following parameters for a database instance:
Which three initialization parameters are not controlled by Automatic Shared Memory Management (ASMM)?
Manually Sized SGA Components that Use SGA_TARGET Space SGA Component,Initialization Parameter
/The log buffer
/The keep and recycle buffer caches
/Nonstandard block size buffer caches
* In addition to setting SGA_TARGET to a nonzero value, you must set to zero all initialization parameters listed inthe table belowto enable full automatic tuning of the automatically sized SGA components.
* Table,Automatically Sized SGA Components and Corresponding Parameters
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.
In your multitenant container database (CDB) containing pluggable database (PDBs), you granted the CREATE TABLE privilege to the common user C # # A_ADMIN in root and all PDBs. You execute the following command from the root container:
SQL > REVOKE create table FROM C # # A_ADMIN;
What is the result?
A. It executes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN
in root only.
B. It fails and reports an error because the CONTAINER=ALL clause is not used.
C. It excludes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN
in root and all PDBs.
D. It fails and reports an error because the CONTAINER=CURRENT clause is not used.
E. It executes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN
in all PDBs.
If the current container is the root:
/Specify CONTAINER = CURRENT to revoke a locally granted system privilege, object privilege, or role from a common user or common role. The privilege or role is revoked from the user or role only in the root. This clause does not revoke privileges granted with CONTAINER = ALL.
/Specify CONTAINER = ALL to revoke a commonly granted system privilege, object privilege on a common object, or role from a common user or common role. The privilege or role is revoked from the user or role across the entire CDB. This clause can revoke only a privilege or role granted with CONTAINER = ALL from the specified common user or common role. This clause does not revoke privileges granted locally with CONTAINER = CURRENT. However, any locally granted privileges that depend on the commonly granted privilege being revoked are also revoked.
If you omit this clause, then CONTAINER = CURRENT is the default.
Which two statements are true concerning the Resource Manager plans for individual pluggable databases (PDB plans) in a multitenant container database (CDB)?
A. If no PDB plan is enabled for a pluggable database, then all sessions for that PDB are treated to an
equal degree of the resource share of that PDB.
B. In a PDB plan, subplans may be used with up to eight consumer groups.
C. If a PDB plan is enabled for a pluggable database, then resources are allocated toconsumergroups
across all PDBs in the CDB.
D. If no PDB plan is enabled for a pluggable database, then the PDB share in the CDB plan is dynamically
E. If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups
based on the shares provided to the PDB in the CDB plan and the shares provided to the consumer
groups in the PDB plan.
A:Setting a PDB resource plan is optional. If not specified, allsessions within the PDB are treated equally.
* In a non-CDB database, workloads within a databaseare managed with resource plans. In a PDB, workloads are also managed with resourceplans, also called PDB resource plans. The functionality is similar except for the followingdifferences:
Multi-level resource plans
Up to 32 consumer groups
Single-level resource plansonly
Up to 8 consumer groups
(not B)No subplans
Incorrect Not C
You use a recovery catalog for maintaining your database backups.
You execute the following command:
$rman TARGET / CATALOG rman / cat@catdb
RMAN > BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
Which two statements are true?
A. Corrupted blocks, if any, are repaired.
B. Checks are performed for physical corruptions.
C. Checks are performed for logical corruptions.
D. Checks are performed to confirm whether all database files exist in correct locations
E. Backup sets containing both data files and archive logs are created.
B (not C): You can validate that all database files and archived redo logs can be backed up by running a command as follows:
RMAN> BACKUP VALIDATE DATABASE ARCHIVELOG ALL;
This form of the command would check for physical corruption. To check for logical corruption,
RMAN> BACKUP VALIDATE CHECK LOGICAL DATABASE ARCHIVELOG ALL;
D: You can use the VALIDATE keyword of the BACKUP command to do the following:
Check datafiles for physical and logical corruption
Confirm that all database files exist and are in the correct locations.
You can use theVALIDATEoption of theBACKUPcommand to verify that database files exist and are in the correct locations (D), and have no physical or logical corruptions that would prevent RMAN from creating backups of them. When performing aBACKUP…VALIDATE, RMAN reads the files to be backed up in their entirety, as it would during a real backup. It does not, however, actually produce any backup sets or image copies (Not A, not E).
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%!
————— Pass All IT Exams at the first Try!