Download Upgrade Oracle9i-10g-11g OCA OR OCP to Oracle Database 12c OCP.1z0-067.Pass4Sure.2018-12-17.131q.vcex

Configuration encryption will used by Transparent encryption. For transparent encryption, you will need to create a wallet, and it must be open. Transparent encryption will then occur automatically after you have issued the CONFIGURE ENCRYPTION FOR DATABASE ON or CONFIGURE ENCRYPTION FOR TABLESPACE ON command.  http://docs.oracle.com/cd/E25054_01/backup.1111/e10642/rcmbckad.htm#CEGEJABHCONFIGURE ENCRYPTION : You can use this command to persistently configure transparent encryption. You cannot persistently configure dual mode or password mode encryption. SET ENCRYPTION : You can use this command to configure dual mode or password mode encryption at the RMAN session level.

COMPRESSED enables binary compression. RMAN compresses the data written into the backup set to reduce the overall size of the backup set. All backups that create backup sets can create compressed backup sets. Restoring compressed backup sets is no different from restoring uncompressed backup sets. RMAN applies a binary compression algorithm as it writes data to backup sets. This compression is similar to the compression provided by many media manager vendors. When backing up to a locally attached tape device, compression provided by the media management vendor is usually preferable to the binary compression provided by BACKUP AS COMPRESSED BACKUPSET. Therefore, use uncompressed backup sets and turn on the compression provided by the media management vendor when backing up to locally attached tape devices. You should not use RMAN binary compression andmedia manager compression together. Some CPU overhead is associated with compressing backup sets. If the target database is running at or near its maximum load, then you may find the overhead unacceptable. In most other circumstances, compressing backup sets saves enough disk space to be worth the CPU overhead. SECTION SIZE sizeSpec  Specifies the size of each backup section produced during a data file backup. By setting this parameter, RMAN can create a multisection backup. In a multisection backup, RMAN creates a backup piece that contains one file section, which is a contiguous range of blocks in a file. All sections of a multisection backup are the same size. You can create a multisection backup for a data file, but not a data file copy. File sections enable RMAN to create multiple steps for the backup of a single large data file. RMAN channels can process each step independently and in parallel, with each channel producing one section of a multisection backup set. If you specify a section size that is larger than the size of the file, then RMAN does not use multisection backup for the file. If you specify a small section size that would produce more than 256 sections, then RMAN increases the section size to a value that results in exactly 256 sections. Depending on where you specify this parameter in the RMAN syntax, you can specify different section sizes for different files in the same backup job. Note: You cannot use SECTION SIZE with MAXPIECESIZE or with INCREMENTAL LEVEL 1.

Enterprise Manager allows a centralized control of database backups. It is possible to set up and schedule RMAN backups for all the databases in a large company, use a consistent backup strategy, and refer to all past RMAN output logs at any time, since they are stored in the Enterprise Manager Cloud Control repository. There is no need to use a central RMAN catalog, because information about the backups is centrally available from Enterprise Manager. And with the group backup feature new to Enterprise Manager Cloud Control 12c, it can be even faster to set up RMAN backups for all the databases-even if there are thousands-that are part of an Enterprise Manager group. http://www.oracle.com/technetwork/articles/oem/havewala-rman-em12c-2104270.html

Configuring Backup Duplexing You can use the CONFIGURE ... BACKUP COPIES command to specify how many copies of each backup piece should be created on the specified device type for the specified type of file. This type of backup is known as a duplexed backup set. The CONFIGURE settings for duplexing only affect backups of datafiles, control files, and archived logs into backup sets, and do not affect image copies. NOT A The CONFIGURE MAXSETSIZE command limits the size of backup sets created on a channel. This CONFIGURE setting applies to any channel, whether manually allocated or configured, when the BACKUP command is used to create backup sets. The default value is given in bytes and is rounded down to the lowest kilobyte value. Reference: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfa.htm#BRADV137

Data Recovery Advisor can diagnose failures such as the following: Components such as datafiles and control files that are not accessible because they do not exist, do not have the correct access permissions, have been taken offline, and so on Physical corruptions such as block checksum failures and invalid block header field values

The seed actually doesn’t use anything since it’s read-only, but any PDB created from the seed will use the undotbs1 undo tablespace. Each PDB can have its own default tablespace, but cannot change the undo tablespace.

Reference:http://docs.oracle.com/cd/B19306_01/backup.102/b14234/obadm_odb.htm#BDCBGJBF

http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmbckad.htm#CEGEJABH To make dual-mode encrypted backups: Start RMAN and connect to a target database and recovery catalog (if used). Execute the SET ENCRYPTION BY PASSWORD command, making sure to omit the ONLY keyword. The following example sets the encryption password for all tablespaces (where password is a placeholder for the actual password that you enter) in the backup and omits ONLY to indicate dual-mode encryption: SET ENCRYPTION IDENTIFIED BY password ON FOR ALL TABLESPACES;