1Z0-063 Exam Questions Free Download From Lead2pass.v.2018-3-29.236q:
Which three statements are true about unplugging a pluggable database (PDB)?
A. A PDB must be in closed state before it can be unplugged.
B. A PDB must have been opened at least once after creation.
C. A PDB must be in MOUNT state before it can be unplugged.
D. PDB data file are automatically removed from disk.
E. An unplugged PDB can be plugged into the same or another container database (CDB).
A: To unplug a PDB, you first close it.
E: You can disassociate or unplug a PDB from a CDB and reassociate or plug the PDB into the same CDB or into another CDB.
C: The PDB must be in a closed stated, not in a mounted state when unplugging it.
D: The unplugging operation makes changes in the PDB data files to record that the PDB was properly and successfully unplugged. Because the PDB is still part of the CDB, you can back it up in Oracle Recovery Manager (Oracle RMAN).
You want to create a duplicate database DUP_DB from your production database PROD on the same host. The PROD database uses Automatic Storage Management (ASM) for storage. Regular backups are taken using RMAN connected to a recovery catalog.
You create an auxiliary instance and want to execute the command:
What is a prerequisite for the successful execution of this command?
A. The target database must be in MOUNT state.
B. RMAN must be connected to the target database instance and the auxiliary instance.
C. A most recent backup set of the PROD database must exist.
D. Flashback must be enabled for the PROD database.
Assume that the source database prod is on host1 and stores its data files in a non-ASM file system. The control files for prod are located in /oracle/oradata/prod/.
You want to duplicate the source database to database dupdb on remote host host2.
You want to store the duplicate database files in ASM disk group +DISK1.
After connecting RMAN to the target, duplicate, and recovery catalog databases, run the following RMAN script to duplicate the database.
DUPLICATE TARGET DATABASE TO dupdb
FROM ACTIVE DATABASE
PARAMETER_VALUE_CONVERT ‘/oracle/oradata/prod/’, ‘+DISK1’ SET DB_CREATE_FILE_DEST +DISK1;
When the DUPLICATE command completes, the duplicate database is created, with data files, online redo log files, and control files in ASM disk group +DISK1.
References: Oracle Database, Backup and Recovery User’s Guide, 12 Release 2 (January 2017), page 26-7
You execute the command to recover your database:
Which statement is true?
A. It restores all data files from the specified time, and then applies the redo logs.
B. It restores all data files, redo log files, and control files, and then applies the redo logs up to the specified time.
C. It restores all data files and control files from the most recent backup taken before the “until time”. and then recovers up to the “until time” using any restored archive logs that are needed to complete the task.
D. It restores the control file and all data files from the most recent backups, and then applies the redo logs up to the “until time”.
UNTIL TIME = ‘date_string’ specifies a time as an upper limit. RMAN selects only files that can be used to restore and recover up to but not including the specified time.
RMAN can perform recovery of the whole database to a specified past time, SCN, or log sequence number. This type of recovery is sometimes called incomplete recovery because it does not completely use all of the available redo. Incomplete recovery of the whole database is also called database point-in- time recovery (DBPITR).
DBPITR requires restoring your database from an older backup, then performing media recovery until your specified target time, SCN or log sequence number. Note that because you need your archived redo log files to perform this process, you cannot perform database point-in-time recovery if you have been running your database in NOARCHIVELOG mode.
You need to perform a block media recovery on the tools01.dbf data file in your database by using Recovery Manager (RMAN).
Which two are prerequisites for performing this operation?
A. You must configure a block change tracking file.
B. You must use an incremental level-1 backup to restore blocks.
C. You must ensure that the database is mounted or open.
D. You must have full or level-0 backups to restore blocks.
E. You must take the tools01.dbf data file offline.
The target database must run in ARCHIVELOG mode and be open or mounted with a current control file.
The backups of the data files containing the corrupt blocks must be full or level 0 backups. They cannot be proxy copies or incremental backups.
References: Oracle Database, Backup and Recovery User’s Guide, 12 Release 2 (January 2017), page 19-4
The CATDB12c database contains an Oracle Database version 12c catalog schema owned by the RC12C user.
The RCAT11 database contains an Oracle Database version 11g catalog schema owned by the RC11 user in which several databases are registered. Both databases are open.
You execute the RMAN commands:
Which two tasks are performed as part of the import?
A. All databases registered in the RC11 catalog are registered in the RC12C catalog.
B. Databases from the RC12C catalog are implicitly unregistered if the RC11 catalog has registered databases with same name.
C. Local and global stored scripts that have the same name as existing scripts in the RC12C catalog are automatically renamed.
D. Imported databases are unregistered from the RC11 catalog.
E. Recovery catalog is resynchronized with the control files of the registered databases.
C: Stored scripts are either global or local. It is possible for global scripts, but not local scripts, to have name conflicts during import because the destination schema contains an object with the same name. In this case, RMAN renames the global script name to COPY OF script_name.
B: Ensure that the same database is not registered in both the source recovery catalog schema and destination catalog schema. If a database is registered in both schemas, then UNREGISTER this database from source recovery catalog and execute the IMPORT command again.
Note: Use the IMPORT CATALOG command to import the metadata from one recovery catalog schema into a different catalog schema. If you created catalog schemas of different versions to store metadata for multiple target databases, then this command enables you to maintain a single catalog schema for all databases.
In CDB$ROOT of your multitenant container database (CDB), you create a common user, C##A_ADMIN.
and then execute the command:
Which statement is true?
A. The command executes successfully, enabling the C##A_ADMIN user to create a tablespace only in the root database.
B. The command executes successfully, enabling the C##A_ADMIN user to create tablespaces in the root database, as well as in the pluggable databases (PDBs).
C. The command fails because the CONTAINER clause is not used.
D. The command fails because system privileges cannot be granted to a common user.
For commonly granted privileges the grantor must be connected to the root and must specify CONTAINER=ALL in the GRANT statement.
Examine the probable steps involved in the basic backup process of RMAN and Oracle Secure Backup (OSB):
1. RMAN initiates backup and passes the database backup storage selector to OSB.
2. RMAN creates the backup job.
3. OSB creates the backup job with an OSB user.
4. RMAN updates its repository.
5. RMAN executes the job and transfers data from a client to media.
6. OSB executes the job and transfers data from a client to media.
7. OSB updates its repository.
Identify the required steps in the correct order.
A. 1, 3, 6, 7, 4
B. 2, 1, 6, 4, 7
C. 1, 3, 5, 7, 4
D. 1, 3, 6, 4, 7
The storage selector act as a layer between RMAN, which accesses the database, and the Oracle Secure Backup software, which manages the backup media.
For backups, Oracle Secure Backup stores metadata about RMAN backup pieces in the Oracle Secure Backup catalog.
The Oracle Secure Backup catalog is stored and managed completely separately from the RMAN recovery catalog. Oracle Secure Backup stores each backup piece and corresponding metadata about the piece.
Which three statements are true about common roles?
A. A common role can be granted only to a common user.
B. Only system privileges can be granted to a common role in a container database (CDB).
C. Object privileges can be granted to a common role in a pluggable database (PDB).
D. A common user that is granted a common role can grant the role to other common and local users in a PDB.
E. A common role cannot be created by a local user.
C: Commonly granted privileges that have been made to the common role apply in the root and all PDBs to which the grantor can connect, including PDBs that may be added later on.
D: Common users can both create and grant common roles to other common and local users.
E: Local users cannot create common roles.
Note: A common role is a role that is created in the root; a local role is created in a PDB.
A: Local users can grant common roles to common and other local users.
Which statement is true about the ALTER SESSION SET CONTAINER command to switch between containers?
A. It can be executed only from CDB$ROOT.
B. It rolls back any pending transactions in the container from which it is executed.
C. It will not fire login triggers for the specified container.
D. It cannot be used to connect to PDB$SEED.
E. It cannot be used to connect to CDB$ROOT from a pluggable database (PDB).
The current container can be the root or a PDB.
The current container can be CDB$ROOT (root) only for common users. The current container can be a particular PDB for both common users and local users.
Which two statements are true about 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, all sessions for that PDB are treated to an equal share of resources.
B. To enable a resource plan for a PDB, a CDB resource plan must be created and enabled.
C. If a PDB plan is enabled for a pluggable database, Resource Manager uses the resource allocation at the PDB level and ignores the limits set at the CDB level.
D. If no PDB plan is enabled for a pluggable database, the PDB uses the CDB plan.
E. If a PDB plan is enabled for a pluggable database, 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: A CDB resource plan determines the amount of resources allocated to each PDB. A PDB resource plan determines how the resources allocated to a specific PDB are allocated to consumer groups within that PDB.
Resource Manager allocates the resources in two steps:
1. It allocates a portion of the system’s resources to each PDB.
2. In a specific PDB, it allocates a portion of system resources obtained in Step 1 to each session connected to the PDB.
E: A PDB resource plan allocates resource among the consumer groups within a PDB.
1Z0-063 dumps full version (PDF&VCE): https://www.lead2pass.com/1z0-063.html
Large amount of free 1Z0-063 exam questions on Google Drive: https://drive.google.com/open?id=1KOnr3ehUBvZFATrr9N7qE_zU1doGP8Qk