[2021-New] Oracle 1Z0-062 Dumps With Update Exam Questions (51-60)

1Z0-062 Dumps

1Z0-062 Exam Questions - Online Test

1Z0-062 Premium VCE File

Learn More 100% Pass Guarantee - Dumps Verified - Instant Download
150 Lectures, 20 Hours

Q1. Which statement is true regarding the startup of a database instance?

A. The instance does not start up normally and requires manual media recovery after a shutdown using the abort option.

B. Uncommitted transactions are rolled back during the startup of the database instance after a shutdown using the immediate option.

C. There is no difference in the underlying mechanics of the startup whether the database is shut down by using the immediate option or the abort option.

D. Media recovery is required when the database is shut down by using either the immediate option or the abort option.

E. Instance recovery is not required if the database instance was shut down by using SHUTDOWN IMMEDIATE.

Answer: B

Reference: http://docs.oracle.com/cd/A87860_01/doc/server.817/a76956/start.htm

Q2. Which four actions are possible during an Online Data file Move operation?

A. Creating and dropping tables in the data file being moved

B. Performing file shrink of the data file being moved

C. Querying tables in the data file being moved

D. Performing Block Media Recovery for a data block in the data file being moved

E. Flashing back the database

F. Executing DML statements on objects stored in the data file being moved

Answer: A,C,E,F

Explanation: - You can now move On line Datafile without hove to stop Monoged Recovery and manually copy and rename Files. This can even be used to move Datafiles from or to ASM.

-New in Oracle Database 12c: FROM METAUNK. Physical Standby Database is in Active Data Guard Mode (opened READ ONLY and Managed Recovery is running): It is now possible to online move a Datafile while Managed Recovery is running, ie. the Physical Standby Database is in Active Data Guard Mode. You con use this Command to move the Datafile

-A flashback operation does not relocate a moved data file to its previous location. If you move a data file online from one location to another and later flash back the database to a point in time before the move, then the Data file remains in the new location, but the contents of the Data file ore changed to the contents at the time specified in the flashback. Oracle0 Database Administrator's Guide 12c Release 1 (12.1)

Q3. Which two are true concerning a multitenant container database with three pluggable database?

A. All administration tasks must be done to a specific pluggable database.

B. The pluggable databases increase patching time.

C. The pluggable databases reduce administration effort.

D. The pluggable databases are patched together.

E. Pluggable databases are only used for database consolidation.

Answer: C,E

Explanation: The benefits of Oracle Multitenant are brought by implementing a pure deployment choice. The following list calls out the most compelling examples.

* High consolidation density. (E) The many pluggable databases in a single multitenant container database share its memory and background processes, letting you operate many more pluggable databases on a particular platform than you can single databases that use the old architecture. This is the same benefit that schema-based consolidation brings.

* Rapid provisioning and cloning using SQL.

* New paradigms for rapid patching and upgrades. (D, not B) The investment of time and effort to patch one multitenant container database results in patching all of its many pluggable databases. To patch a single pluggable database, you simply unplug/plug to a multitenant container database at a different Oracle Database software version.

* (C, not A) Manage many databases as one. By consolidating existing databases as pluggable databases, administrators can manage many databases as one. For example, tasks like backup and disaster recovery are performed at the multitenant container database level.

* Dynamic between pluggable database resource management. In Oracle Database 12c, Resource Manager is extended with specific functionality to control the competition for resources between the pluggable databases within a multitenant container database. Note:

* Oracle Multitenant is a new option for Oracle Database 12c Enterprise Edition that helps customers reduce IT costs by simplifying consolidation, provisioning, upgrades, and more. It is supported by a new architecture that allows a multitenant container database to hold many pluggable databases. And it fully complements other options, including Oracle Real Application Clusters and Oracle Active Data Guard. An existing database can be simply adopted, with no change, as a pluggable database; and no changes are needed in the other tiers of the application.

Reference: 12c Oracle Multitenant

Q4. You are planning the creation of a new multitenant container database (CDB) and want to store the ROOT and SEED container data files in separate directories.

You plan to create the database using SQL statements.

Which three techniques can you use to achieve this?

A. Use Oracle Managed Files (OMF).

B. Specify the SEED FILE_NAME_CONVERT clause.

C. Specify the PDB_FILE_NAME_CONVERT initialization parameter.

D. Specify the DB_FILE_NAMECONVERT initialization parameter.

E. Specify all files in the CREATE DATABASE statement without using Oracle managed Files (OMF).

Answer: A,B,C

Explanation: You must specify the names and locations of the seed's files in one of the following ways:

* (A) Oracle Managed Files

* (B) The SEED FILE_NAME_CONVERT Clause

* (C) The PDB_FILE_NAME_CONVERT Initialization Parameter

Q5. Which task would you recommend before using the Database Upgrade Assistant (DBUA) to upgrade a single-instance Oracle 11g R2 database to Oracle Database 12c?

A. shutting down the database instance that is being upgraded

B. executing the catctl.pl script to run the upgrade processes in parallel

C. running the Pre-Upgrade Information Tool

D. copying the listener.ora file to the new ORACLE_HOME

Answer: C

Reference: http://docs.oracle.com/cd/E11882_01/server.112/e23633/upgrade.htm#UPGRD12395

Q6. What is the result of executing a TRUNCATE TABLE command on a table that has Flashback Archiving enabled?

A. It fails with the ORA-665610 Invalid DDL statement on history-tracked message

B. The rows in the table are truncated without being archived.

C. The rows in the table are archived, and then truncated.

D. The rows in both the table and the archive are truncated.

Answer: B

Explanation: You cannot roll back a TRUNCATE TABLE statement, nor can you use a FLASHBACK TABLE statement to retrieve the contents of a table that has been truncated.

Q7. You are connected to a pluggable database (PDB) as a common user with DBA privileges. The STATISTICS_LEVEL parameter is PDB_MODIFIABLE. You execute the following: SQL > ALTER SYSTEM SET STATISTICS_LEVEL = ALL SID = ‘*’ SCOPE = SPFILE; Which is true about the result of this command?

A. The STATISTICS_LEVEL parameter is set to all whenever this PDB is re-opened.

B. The STATISTICS_LEVEL parameter is set to ALL whenever any PDB is reopened.

C. The STATISTICS_LEVEL parameter is set to all whenever the multitenant container database (CDB) is restarted.

D. Nothing happens; because there is no SPFILE for each PDB, the statement is ignored.

Answer: C

Explanation:

Note:

* In a container architecture, the parameters for PDB will inherit from the root database. That means if statistics_level=all in the root that will cascade to the PDB databases.

You can over ride this by using Alter system set, if that parameter is pdb modifiable, there is a new column in v$system_parameter for the same.

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

Q9. The hr user receiver, the following error while inserting data into the sales table:

ERROR at line 1:

ORA-01653; unable to extend table HR.SALES by 128 in tablespace USERS

On investigation, you find that the users tablespace uses Automnrif Segment Space Management (ASSM). It is the default tablespace for the HR user with an unlimited quota on it.

Which two methods would you use to resolve this error?

A. Altering the data life associated with the USERS tablespace to ex automatically

B. Adding a data life to the USERS tablespace

C. Changing segment space management for the USERS tablespace to manual

D. Creating a new tablespace with autoextend enabled and changing the default tablespace of the HR user to the new tablespace

E. Enabling resumable space allocation by setting the RESUMABLE_TIMEOUT parameter to a nonzero value

Answer: A,D

Q10. Examine this command:

SQL > exec DBMS_STATS.SET_TABLE_PREFS (‘SH’, ‘CUSTOMERS’, ‘PUBLISH’, ‘false’);

Which three statements are true about the effect of this command?

A. Statistics collection is not done for the CUSTOMERS table when schema stats are gathered.

B. Statistics collection is not done for the CUSTOMERS table when database stats are gathered.

C. Any existing statistics for the CUSTOMERS table are still available to the optimizer at parse time.

D. Statistics gathered on the CUSTOMERS table when schema stats are gathered are stored as pending statistics.

E. Statistics gathered on the CUSTOMERS table when database stats are gathered are stored as pending statistics.

Answer: C,D,E

Explanation: * SET_TABLE_PREFS Procedure

This procedure is used to set the statistics preferences of the specified table in the specified schema.

* Example: Using Pending Statistics Assume many modifications have been made to the employees table since the last time statistics were gathered. To ensure that the cost-based optimizer is still picking the best plan, statistics should be gathered once again; however, the user is concerned that new statistics will cause the optimizer to choose bad plans when the current ones are acceptable. The user can do the following:

EXEC DBMS_STATS.SET_TABLE_PREFS('hr', 'employees', 'PUBLISH', 'false');

By setting the employees tables publish preference to FALSE, any statistics gather from now on will not be automatically published. The newly gathered statistics will be marked as pending.