Skip to main content

Posts

Showing posts from 2013

Oracle Database 12c - What's new with Oracle Dataguard for Physical Standbys? (New Features)

We know Dataguard by far is the industry's utmost reliable DR solution to protect the enterprise data for Oracle Databases. Let me share some of the new features I have learned so far,

Following points to be noted
=>SYSDG Privilege
A special privilege "SYSDG" has been introduced to simplify Dataguard operations.

=>Far Sync Instance
A New Standby destination type is allowed in Active Dataguard environment that ensures zero data loss failover and zero performance impact on Primary Database, is called "Far Sync Instance". This destination contains parameterfile, controlfile, and standby redo logs (SRLs), it receives the redo from Primary Database, and archives it to local destination through Standby Redo Logs. There are no Datafiles here. Technically, A Standby Database Instance without Datafiles is called Far Sync Instance. A far sync instance consumes very little disk and processing resources, yet provides the ability to failover to a terminal destination with …

Oracle Database 12c New Features Explained - RMAN with Multitenant Architecture

RMAN is the beauty of Oracle Backup and Recovery architecture, has changed completely the way backups work and unlimited so many possibilities. We saw so many enhancements by Oracle with each version from Compression of Backups to Handling block corruption. And, 12c is no exception for that. 

In this post, I would like to discuss about new enhancements made to RMAN as part of changes influenced by the Oracle Database Architecture like Multitenant Architecture.

Let's start with Multitenant Architecture, Please refer to my blog post to know more about it.

Backup and Recovery of Pluggable Databases

"SYSBACKUP" is the new privilege or user that has been introduced in 12c to perform RMAN Backup and Recovery Operations, no more SYSDBA privilege is required for a specific user to perform Backup operations. "SYSBACKUP" has two roles assigned "SELECT_CATALOG_ROLE" and "HS_ADMIN_SELECT_ROLE""BACKUP PLUGGABLE DATABASE" is the new command introduc…

Moving a Non Container Database (Non CDB) to Container Database (CDB, as PDB)

In this post, I discuss moving a regular Non CDB Database to CDB architecture. DBMS_PDB.DESCRIBE metadata procedure is used for the same purpose. Following analogy applies to the post,

  ORA12C - Non CDB Database (Instance)
  CONDB - CDB Database (Instance)
Please follow steps below to move a Non CDB to CDB environment as PDB,

1. Open the Non CDB (ORA12C) in READ-ONLY Mode to keep it transactionally consistent.

SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> STARTUP MOUNT
ORACLE instance started.

Total System Global Area  668082176 bytes
Fixed Size    2291952 bytes
Variable Size  507512592 bytes
Database Buffers  155189248 bytes
Redo Buffers    3088384 bytes
Database mounted.
SQL> ALTER DATABASE OPEN READ ONLY;
Database altered.

SQL> SELECT NAME,OPEN_MODE FROM V$DATABASE;

NAME  OPEN_MODE
--------- --------------------
ORA12C  READ ONLY

2. Connect to the Non-CDB Database(ORA12C) and execute DBMS_PDB.DESCRIBE procedure to generate an xml file that…