READ Free Dumps For Oracle- 1z0-060
| Question ID 20781 | Examine the following impdp command to import a database over the network from a pre-12c Oracle database (source):
Which three are prerequisites for successful execution of the command?
|
| Option A | The import operation must be performed by a user on the target database with the DATAPUMP_IMP_FULL_DATABASE role, and the database link must
connect to a user on the source database with the DATAPUMP_EXD_FULL_DATABASE role.
|
| Option B | All the user-defined tablespaces must be in read-only mode on the source database.
|
| Option C | The export dump file must be created before starting the import on the target database.
|
| Option D | The source and target database must be running on the same platform with the same endianness.
|
| Option E | The path of data files on the target database must be the same as that on the source database.
|
| Option F | The impdp operation must be performed by the same user that performed the expdp operation.
|
| Correct Answer | A,B,D |
Explanation In this case we have run the impdp without performing any conversion if endian format is different then we have to first perform conversion.
| Question ID 20782 | Which two are true concerning a multitenant container database with three pluggable database?
|
| Option A | All administration tasks must be done to a specific pluggable database.
|
| Option B | The pluggable databases increase patching time.
|
| Option C | The pluggable databases reduce administration effort.
|
| Option D | The pluggable databases are patched together.
|
| Option E | Pluggable databases are only used for database consolidation.
|
| Correct 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 Reference: Real 25 Oracle 1z0-060 Exam