1z0-062 Exam Dumps - Oracle Database 12c: Installation and Administration

Multipartition maintenance enables adding, dropping, truncate, merge, split operations on multiple partitions.

A: Merge Multiple Partitions:

The new “ALTER TABLE … MERGE PARTITIONS ” help merge multiple partitions or subpartitions with a single statement. When merging multiple partitions, local and global index operations and semantics for inheritance of unspecified physical attributes are the same for merging two partitions.

B: Drop Multiple Partitions:

The new “ALTER TABLE … DROP PARTITIONS ” help drop multiple partitions or subpartitions with a single statement.

Example:

view plaincopy to clipboardprint?

SQL> ALTER TABLE Tab_tst1 DROP PARTITIONS

Tab_tst1_PART5, Tab_tst1_PART6, Tab_tst1_PART7;

Table altered

SQL>

Restrictions :

- You can’t drop all partitions of the table.

- If the table has a single partition, you will get the error: ORA-14083: cannot drop the only partition of a partitioned.

https://docs.oracle.com/database/121/CNCPT/process.htm

The alert log is a chronological log of messages and errors, and includes the following items:

*All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock errors (ORA-60) that occur

* Administrative operations, such as CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements

* Messages and errors relating to the functions of shared server and dispatcher processes

* Errors occurring during the automatic refresh of a materialized view

* The values of all initialization parameters that had nondefault values at the time the database and instance start

Note:

* The alert log file (also referred to as the ALERT.LOG) is a chronological log of messages and errors written out by an Oracle Database. Typical messages found in this file is: database startup, shutdown, log switches, space errors, etc. This file should constantly be monitored to detect unexpected messages and corruptions.

B: Job priorities are used only to prioritize among jobs in the same class.

Note: Group jobs for prioritization

Within the same job class, you can assign priority values of 1-5 to individual jobs so that if two jobs in the class are scheduled to start at the same time, the one with the higher priority takes precedence. This ensures that you do not have a less important job preventing the timely completion of a more important one.

C: Set resource allocation for member jobs

Job classes provide the link between the Database Resource Manager and the Scheduler, because each job class can specify a resource consumer group as an attribute. Member jobs then belong to the specified consumer group and are assigned resources according to settings in the current resource plan.

* Creating a PDB

Rather than constructing the data dictionary tables that define an empty PDB from scratch, and then populating its Obj$ and Dependency$ tables, the empty PDB is created when the CDB is created. (Here, we use empty to mean containing no customer-created artifacts.) It is referred to as the seed PDB and has the name PDB$Seed. Every CDB non-negotiably contains a seed PDB; it is non-negotiably always open in read-only mode. This has no conceptual significance; rather, it is just an optimization device. The create PDB operation is implemented as a special case of the clone PDB operation. The size of the seed PDB is only about 1 gigabyte and it takes only a few seconds on a typical machine to copy it.

References: