Download Upgrade Oracle9i-10g-11g OCA OR OCP to Oracle Database 12c OCP.1z0-067.TestKing.2020-02-13.144q.vcex

References: http://docs.oracle.com/cd/E24628_01/server.121/e17635/tdppt_degrade.htm

Because according to oracle PDFs if you run restore table ... auxiliary a impede and rename can be included. So there is no reason to make the import manually if it can be already included in step 2.  Reference: https://docs.oracle.com/database/121/BRADV/rcmresind.htm#BRADV689

The Automatic Diagnostic Repository (ADR) is a directory structure that is stored outside of the database. It is therefore available for problem diagnosis when the database is down. The ADR root directory is known as ADR base. Its location is set by the DIAGNOSTIC_DEST initialization parameter. If this parameter is omitted or left null, the database sets DIAGNOSTIC_DEST upon startup as follows:If environment variable ORACLE_BASE is set, DIAGNOSTIC_DEST is set to the directory designated by ORACLE_BASE. If environment variable ORACLE_BASE is not set, DIAGNOSTIC_DEST is set to ORACLE_HOME/log. Reference:http://docs.oracle.com/cd/B28359_01/server.111/b28310/diag001.htm#ADMIN11008

The bulk loader would be started in response to a file watcher scheduler event and the indexes would be rebuilt in response to an application event raised by the bulk loader.  Your application can raise an event to notify the Scheduler to start a job. A job started in this way is referred to as an event-based job. The job can optionally retrieve the message content of the event.  References:https://docs.oracle.com/cd/B28359_01/server.111/b28310/scheduse008.htm#CHDIAJEBhttps://docs.oracle.com/cd/E18283_01/server.112/e17120/scheduse005.htm#CIABIEJA

SQL> REVOKE c##role1 FROM c##a_admin; REVOKE c##role1 FROM c##a_admin * ERROR at line 1: ORA - 01951: ROLE ‘C##ROLE1’ not granted to ‘C##A_ADMIN’ SQL> REVOKE c##role1 FROM c##a_admin CONTAINER=ALL; Revoke succeeded. SQL> This CREATE USER c##a_admin IDENTIFIED BY orcl123; will create common user event container is not specified.

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.  CONFIGURE 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.Reference:http://docs.oracle.com/cd/E25054_01/backup.1111/e10642/rcmbckad.htm#CEGEJABH

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.

The threshold for activating tiering policies is based on two parameters:TBS PERCENT USED TBS PERCENT FREE Both values can be controlled by the DBMS_ILM_ADMIN package. TBS PERCENT USED and TBS PERCENT FREE default to 85 and 25, respectively. Hence, whenever the source tablespace’s usage percentage goes beyond 85 percent, any tiering policy specified on its objects will be executed and objects will be moved to the target tablespace until the source tablespace becomes at least 25 percent free. Note that it is possible to add a custom condition to tiering policies to enable movement of data based on conditions other than how full the tablespace is. In addition, the READ ONLY option must be explicitly specified for the target tablespace.

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. References:http://www.oracle.com/technetwork/articles/oem/havewala-rman-em12c-2104270.html