♥♥ 2017 NEW RECOMMEND ♥♥

Free VCE & PDF File for Oracle 1Z0-062 Real Exam (Full Version!)

★ Pass on Your First TRY ★ 100% Money Back Guarantee ★ Realistic Practice Exam Questions

Free Instant Download NEW 1Z0-062 Exam Dumps (PDF & VCE):
Available on: http://www.exam.com/1Z0-062-dumps.html


Master the 1z0 062 dumps Oracle Database 12c: Installation and Administration content and be ready for exam day success quickly with this Actualtests 1z0 062 dumps free question. We guarantee it!We make it a reality and give you real 1z0 062 pdf questions in our Oracle oracle database 12c installation and administration 1z0 062 pdf braindumps.Latest 100% VALID Oracle 1z0 062 pdf Exam Questions Dumps at below page. You can use our Oracle 1z0 062 dumps braindumps and pass your exam.

Q1. Your multitenant container database (CDB) contains a pluggable database, HR_PDB. The default permanent tablespace in HR_PDB is USERDATA. The container database (CDB) is open and you connect RMAN. 

You want to issue the following RMAN command: 

RMAN > BACKUP TABLESPACE hr_pdb:userdata; 

Which task should you perform before issuing the command? 

A. Place the root container in ARHCHIVELOG mode. 

B. Take the user data tablespace offline. 

C. Place the root container in the nomount stage. 

D. Ensure that HR_PDB is open. 

Answer:


Q2. As a user of the ORCL database, you establish a database link to the remote HQ database such that all users in the ORCL database may access tables only from the SCOTT schema in the HQ database. SCOTT’s password is TIGER. The service mane “HQ” is used to connect to the remote HQ database. 

Which command would you execute to create the database link? 

A. CREATE DATABASE LINK HQ USING 'HQ' 

B. CREATE DATABASE LINK HQ CONNECT TO CXJRRENT_USER USING HQ' S 

C. CREATE PUBLIC DATABASE LINK HQ CONNECT TO scott IDENTIFIED BY tiger USING 'HQ' 

D. CREATE DATABASE LINK HQ CONNECT TO scott IDENTIFIED BY tiger USING 'HQ' 

Answer:


Q3. 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. 

Answer: A,B,E 

Explanation: A: The APPEND keyword tells SQL*Loader to preserve any preexisting data in the table. Other options allow you to delete preexisting data, or to fail with an error if the table is not empty to begin with. 

B (not D): Note: 

* SQL*Loader-00210: first data file is empty, cannot process the FIELD NAMES record 

Cause: The data file listed in the next message was empty. Therefore, the FIELD NAMES 

FIRST FILE directive could not be processed. 

Action: Check the listed data file and fix it. Then retry the operation 

E: 

* A comma-separated values (CSV) (also sometimes called character-separated values, because the separator character does not have to be a comma) file stores tabular data (numbers and text) in plain-text form. Plain text means that the file is a sequence of characters, with no data that has to be interpreted instead, as binary numbers. A CSV file consists of any number of records, separated by line breaks of some kind; each record consists of fields, separated by some other character or string, most commonly a literal comma or tab. Usually, all records have an identical sequence of fields. 

* Fields with embedded commas must be quoted. 

Example: 

1997,Ford,E350,"Super, luxurious truck" 

Note: 

* SQL*Loader is a bulk loader utility used for moving data from external files into the Oracle database. 


Q4. You enabled an audit policy by issuing the following statements: 

SQL> AUDIT POLICY ORA_DATABASE_PARAMETER BY SCOTT; 

SQL> AUDIT POLICY ORA_DATABASE_PARAMETER BY SYS, SYSTEM; 

For which database users and for which executions is the audit policy now active? Select two. 

A. SYS, SYSTEM 

B. SCOTT 

C. Only for successful executions 

D. Only for failed executions 

E. Both successful and failed executions 

Answer: A,E 

Explanation: * The ORA_DATABASE_PARAMETER policy audits commonly used Oracle Database parameter settings. By default, this policy is not enabled. 


Q5. You execute the following piece of code with appropriate privileges: 

User SCOTT has been granted the CREATE SESSION privilege and the MGR role. 

Which two statements are true when a session logged in as SCOTT queries the SAL column in the view and the table? 

A. Data is redacted for the EMP.SAL column only if the SCOTT session does not have the MGR role set. 

B. Data is redacted for EMP.SAL column only if the SCOTT session has the MGR role set. 

C. Data is never redacted for the EMP_V.SAL column. 

D. Data is redacted for the EMP_V.SAL column only if the SCOTT session has the MGR role set. 

E. Data is redacted for the EMP_V.SAL column only if the SCOTT session does not have the MGR role set. 

Answer: A,C 

Explanation: 

Note: 

* DBMS_REDACT.FULL completely redacts the column data. 

* DBMS_REDACT.NONE applies no redaction on the column data. Use this function for development testing purposes. LOB columns are not supported. 

* The DBMS_REDACT package provides an interface to Oracle Data Redaction, which enables you to mask (redact) data that is returned from queries issued by low-privileged users or an application. 

* If you create a view chain (that is, a view based on another view), then the Data Redaction policy also applies throughout this view chain. The policies remain in effect all of the way up through this view chain, but if another policy is created for one of these views, then for the columns affected in the subsequent views, this new policy takes precedence. 


Q6. To implement Automatic Management (AMM), you set the following parameters: 

When you try to start the database instance with these parameter settings, you receive the following error message: 

SQL > startup 

ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings, see alert log for more information. 

Identify the reason the instance failed to start. 

A. The PGA_AGGREGATE_TARGET parameter is set to zero. 

B. The STATISTICS_LEVEL parameter is set to BASIC. 

C. Both the SGA_TARGET and MEMORY_TARGET parameters are set. 

D. The SGA_MAX_SIZE and SGA_TARGET parameter values are not equal. 

Answer:

Explanation: 

Example: SQL> startup force ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings ORA-00848: STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or MEMORY_TARGET 


Q7. The user SCOTT owns the CUST table that is placed in the SALES tablespace. The user SCOTT opens a session and executes commands as follows: 

SQL> INSERT INTO cust VALUES(101, 'JACK'); 

1 row created. 

SQL> INSERT INTO cust VALUES(102, 'SMITH'); 

1 row created. 

As a DBA, you execute the following command from another session: 

ALTER TABLESPACE sales READ ONLY; 

Which statement is true regarding the effect of this command on the transaction in Scott's session? 

A. The command fails as a transaction is still pending. 

B. The transaction in Scott's session is rolled back and the tablespace becomes readonly. 

C. The command waits and the user SCOTT can execute data manipulation language (DML) statements only as part of the current transaction. 

D. The command hangs until all transactions on the objects in the tablespace commit or rollback, and then the tablespace is placed in readonly mode. 

Answer:


Q8. The persistent configuration settings for RMAN have default for all parameters. 

Identify four RMAN commands that produce a multi-section backup. 

A. BACKUP TABLESPACE SYSTEM SECTION SIZE 100M; 

B. BACKUP AS COPY TABLESPACE SYSTEM SECTION SIZE 100M; 

C. BACKUP ARCHIVELOG ALL SECTION SIZE 25M; 

D. BACKUP TABLESPACE "TEMP" SECTION SIZE 10M; 

E. BACKUP TABLESPACE "UNDO" INCLUDE CURRENT CONTROLFILE SECTION SIZE 100M; 

F. BACKUP SPFILE SECTION SIZE 1M; 

G. BACKUP INCREMENTAL LEVEL 0 TABLESPACE SYSAUX SECTION SIZE 100M; 

Answer: A,B,C,G 


Q9. Your database is open and the LISTENER listener running. You stopped the wrong listener LISTENER by issuing the following command: 

1snrctl > STOP 

What happens to the sessions that are presently connected to the database Instance? 

A. They are able to perform only queries. 

B. They are not affected and continue to function normally. 

C. They are terminated and the active transactions are rolled back. 

D. They are not allowed to perform any operations until the listener LISTENER is started. 

Answer:

Explanation: The listener is used when the connection is established. The immediate impact of stopping the listener will be that no new session can be established from a remote host. Existing sessions are not compromised. 


Q10. 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: A,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.