Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration

I read My Oracle Support note “Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration [ID 413484.1]” .
I made decision that let me check this.Then I have create two virtual machines with Oracle Virtual Box. Witch is a virtual machine OS Oracle Linux server 6.2 (x86_64) and a Virtual Machine with OS Microsoft Windows 2008 Server R2 (x64) . Installed Oracle Database 11g Release 2 ( both server, and a database (ADMDB) is created on first server.

I used RMAN Duplicate command for creation of standby database and after creation of standby  database used Data Guard Manager Command-Line interface for creation of data guard configuration.
I think about that I achieved this, this will be for all oracle database administrators very interesting.

[ID 413484.1]

The simplest path when deploying Data Guard is to configure a homogeneous and symmetric primary/standby configuration.  However, it is often useful to deploy a heterogeneous configuration either to utilize existing servers that happen to run different operating systems or to facilitate migrations from one platform to another with minimal downtime or risk. It is also reasonable for users to wish to reduce their disaster recovery investment by purposely configuring a standby system with less processing capacity than production, or by utilizing lower cost components than used for their primary system. 
Prior to Data Guard 11g, the Data Guard Broker did not support different word-size in the same Data Guard configuration, thus requiring management from the SQL*Plus command line for mixed word-size Data Guard configurations.  This restriction is lifted from Data Guard 11g onward.
RMAN generally supports instantiation of a physical standby database for the supported platform combinations. Please see Support Note 1079563.1 for details.
Enterprise Manager can not be used for standby database creation or other administrative functions in any configuration where PLATFORM_IDs are not identical. Oracle recommends using the Data Guard Broker command line interface (DGMGRL) to administer mixed platform combinations from Oracle Database 11g onward and SQL*Plus command line for configurations that pre-date Oracle Database 11g.

Platform name
 Release name
Platform name supported within the same Data Guard configuration when using Data Guard Redo Apply
(Physical Standby)
Linux 64-bit for AMD
Linux x86-64
Microsoft Windows 64-bit for AMD
Microsoft Windows (x86-64) - Oracle 11g onward, requires patch for Bug 13104881

Mahir M. Quluzade


Oracle Data Guard 11g - Overview Logical Standby Database

Logical Standby  Database is one part of Oracle Database Guard.
The benefits are obvious: the standby database can not only be open for reads, but it can also support additional entities such as indexes and materialized views that can be too expensive to maintain at the primary database. In addition, you can add other tables or even entire schemas to a logical standby database and have complete read-write access to those tables as they are not maintained by SQL Apply.
Logical standby databases are support all role transition operations that are available in the context of a physical standby database.
Creating Logical  Standby Database.

For creating logical standby database we are need create a physical standby database, then convert to logical standby.

I had created broker-managed configuration admdg with admdb – Primary database, admts – Physical  standby database.

1. Created Physical Standby database