READ Free Dumps For Oracle- 1z0-062
| Question ID 21735 | Identify two correct statements about multitenant architectures.
|
| Option A | Multitenant architecture can be deployed only in a Real Application Clusters (RAC) configuration.
|
| Option B | Multiple pluggable databases (PDBs) share certain multitenant container database (CDB) resources.
|
| Option C | Multiple CDBs share certain PDB resources.
|
| Option D | Multiple non-RAC CDB instances can mount the same PDB as long as they are on the same server.
|
| Option E | Patches are always applied at the CDB level.
|
| Option F | A PDB can have a private undo tablespace.
|
| Correct Answer | B,E |
Explanation Explanation: B: Using 12c Resource manager you will be able control CPU, Exadata I/O, sessions and parallel servers. A new 12c CDB Resource Manager Plan will use so-called "Shares" (resource allocations) to specify how CPU is distributed between PDBs. A CDB Resource Manager Plan also can use "utilization limits" to limit the CPU usage for a PDB. With a default directive, you do not need to modify the resource plan for each PDB plug and unplug. E: New paradigms for rapid patching and upgrades. 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. Incorrect: Not A: * The Oracle RAC documentation describes special considerations for a CDB in an Oracle RAC environment. * 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 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. Not D: You can unplug a PDB from one CDB and plug it into a different CDB without altering your schemas or applications. A PDB can be plugged into only one CDB at a time. not F: * UNDO tablespace can NOT be local and stays on the CDB level. * Redo and undo go hand in hand, and so the CDB as a whole has a single undo tablespace per RAC instance.
| Question ID 21736 | You upgrade your Oracle database in a multiprocessor environment. As a recommended you execute the following script:
SQL > @utlrp.sql
Which two actions does the script perform?
|
| Option A | Parallel compilation of only the stored PL/SQL code
|
| Option B | Sequential recompilation of only the stored PL/SQL code
|
| Option C | Parallel recompilation of any stored PL/SQL code
|
| Option D | Sequential recompilation of any stored PL/SQL code
|
| Option E | Parallel recompilation of Java code
|
| Option F | Sequential recompilation of Java code
|
| Correct Answer | C,E |
Explanation Explanation: utlrp.sql and utlprp.sql The utlrp.sql and utlprp.sql scripts are provided by Oracle to recompile all invalid objects in the database. They are typically run after major database changes such as upgrades or patches. They are located in the $ORACLE_HOME/rdbms/admin directory and provide a wrapper on the UTL_RECOMP package. The utlrp.sql script simply calls the utlprp.sql script with a command line parameter of "0". The utlprp.sql accepts a single integer parameter that indicates the level of parallelism as follows. 0 - The level of parallelism is derived based on the CPU_COUNT parameter. 1 - The recompilation is run serially, one object at a time. N - The recompilation is run in parallel with "N" number of threads. Both scripts must be run as the SYS user, or another user with SYSDBA, to work correctly. Reference: Recompiling Invalid Schema Objects