Oracle Tidbits – October 2014

Oracle *daily* TidBits” published at on all weekdays in October 2014. You will also see these tidbits, one tidbit at a time, for each page refresh on the right side of this blog as well… Hope you find these helpful to learn something new or to remind you of its existence and use…

Publish Date TidBit
6-Oct The Grid Infrastructure Management Repository is automatically installed with Oracle Grid Infrastructure 12c release 1 ( The GIMR enables such features as Cluster Health Monitor, Oracle Database QoS Management, and Rapid Home Provisioning, and provides a historical metric repository that simplifies viewing of past performance and diagnosis of issues. This capability is fully integrated into Oracle Enterprise Manager Cloud Control for seamless management.
7-Oct The Grid infrastructure Management Repository database (12c feature) is named MGMTDB and it is managed using the “srvctl” commands.  For example “srvctl config mgmtdb” or “srvctl start mgmtdb” or “srvctl stop mgmtdb”
8-Oct When you install Oracle Grid Infrastructure 12c, the GI management repository database MGMTDB is created by default on the same diskgroup as the OCR.
9-Oct The Cluster Health Monitor (CHM) in Oracle Grid Infrastructure 12c detects and analyzes operating system and cluster resource-related degradation and failures. CHM stores real-time operating system metrics in the Oracle Grid Infrastructure Management Repository.
10-Oct The Grid infrastructure Management Repository database (MGMTDB, 12c feature) runs on one node in the cluster, and must support failover to another node in case of node or storage failure. The GIMR database is single-tenant deployment of CDB with one PDB.
13-Oct In #DB12c statistics are automatically created as part of a bulk load operation such as a CREATE TABLE AS SELECT operation or an INSERT INTO … SELECT operation on an empty table.
15-Oct Starting with #DB12c, you can use the SAVE STATE clause of ALTER PLUGGABLE DATABASE statement to preserve the open mode of the pluggable database. If SAVE STATE is specified, open mode of specified PDB is preserved across CDB restart on instances specified in the INSTANCES clause. Similarly, with the DISCARD STATE clause, the open mode of specified PDB is no longer preserved. This clause provides the flexibility to choose the automatic startup of application PDBs when a CDB undergoes a restart.
17-Oct In #DB12c, ALTER TABLE … MOVE PARTITION becomes non-blocking online DDL while DML operations continue to run uninterrupted on the partition that is being moved. Global indexes are maintained during the move partition, so a manual index rebuild is no longer required.
20-Oct Using Active Dataguard in #DB12c, reporting applications are able to write to global temporary tables at the standby database without any modification.
22-Oct SQL*Loader in #DB12c has a new option that does not require the user to create a SQL*Loader control file. Instead, command-line parameters are used to specify how the data file is loaded, and SQL*Loader automatically chooses the best method with which to load the data. Data files formatted as comma-separated values (CSV) to both SQL*Loader and external tables are supported.
24-Oct Rapid Home Provisioning (rhpctl utility) is a method of deploying software homes to nodes in a cloud computing environment from a single cluster where you create, store, and manage templates of Oracle homes as images (called gold images) of Oracle software, such as databases, middleware, and applications. You can make a working copy of any gold image, and then you can provision that working copy to any node in the cloud.
27-Oct In #DB12c Datapump Export and Import, the LOGTIME command-line parameter allows you to request that messages displayed during export and import operations be timestamped. The options for this parameter are STATUS (timestamps on status messages only), LOGFILE (timestamps on log file messages only) and ALL (timestamps on both status and log file messages).
29-Oct Staring in Oracle #DB12c, the SIMILAR value for CURSOR_SHARING is deprecated. Use FORCE instead.
31-Oct Starting with Oracle #DB12c, the software deinstallation standalone utility is replaced with a deinstall option using Oracle Universal Installer (OUI). You can also run the deinstallation tool using the runInstaller command on Linux and UNIX (or setup.exe on Windows) with the -deinstall and -home options from the base directory of the installation media for Oracle Database, Oracle Database Client, or Oracle Grid Infrastructure.

Leave a Reply

%d bloggers like this: