Oracle11g heterogenous data guard Linux-ASM primary, Windows-Filesystem standby

Is it possible to setup a standby database on (Windows 64bit) OS filesystem with 32GB datafile limit that syncs with a primary database on (Linux 64bit) ASM that has datafiles that are larger than 32GB.
There is a Linux-ASM standby in place, this will be an additional standby, to be used as a reporting database using Oracle11g snapshot standby
I have used datapump to export-import from Linux-ASM to Windows-filesystem by precreating additional 32GB datafiles in the Windows database, the import works, it takes too long to import for a reporting database
it's not clear to me how to synchronize the new standby without using RMAN full or incremental backup-restores
Any suggestions or suggested document IDs are welcome!
Thank you,
Drew Salisbury

Hi Drew,
Standby files have to be the same size/distribution as the primary - that can be differnet os, in ASM etc but they have to be the same number and size.
There are some ways to speed up import - parallel etc but in a big database there is always a lot of time lost in index building post data load.
How feasible is it to shrink the datafiles in wondows nack to 32GB......?
Can you set up ASM on windows?
You could use streams or something to replicate and keep the copy you created up to date rather than using physical standby?
Cheers,
Rich

Similar Messages

Steps for Data Guard with one primary and 2 standby

Hi,
Database :10.2.0.4, 11.2.0.1
Os: Windows , Unix
A ----------------> Primary database
B ----------------> Standby Database 1
C ----------------> Standby Database 2
I want to configure *2 standby* databases for single primary database.
Lets take, A ,B and C are my machines.My data guard configuration will be like,*archive logs will be moving* from A to B and A to C.
If i do any switchover in between A and B , now B is primary and remaining A and C are standby databases.At this stage also , archive logs should move from B to A and B to C. Also, same should happen from C to A and C to B,If i do switchover in between B and C.If everything is fine , then i will do switchback to main Primary database(A).
How do i have to mention PFILE in all machines ,the parameters like
LOG_ARCHIVE_DEST_1=LOCATION=<PATH> -- LOCAL ARCHIVE PATH
LOG_ARCHIVE_DEST_2=SERVICE=
LOG_ARCHIVE_DEST_3=SERVICE=
FAL_SERVER=
FAL_CLIENT=
STANDBY_FILE_MANAGEMENT=
In my tnsnames.ora , primary,standby1 and standby2 are my service entries and these are same in all of my machines.
Please suggest me , how do i can configure my pfiles in all machines ?.
Thanks,
Sunand

Not yet, but now you have me interested.
Please consider Flashback.
I still have to test but here's my take:
PRIMARY SETTINGS
*.FAL_SERVER=STANDBY
*.FAL_CLIENT=PRIMARY
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=PRIMARY
*.LOG_FILE_NAME_CONVERT='STANDBY','PRIMARY'
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PRIMARY'
*.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE
*.LOG_ARCHIVE_DEST_STATE_3=ENABLE
*.LOG_ARCHIVE_MAX_PROCESSES=30
STANDBY 1 SETTINGS
*.FAL_SERVER=PRIMARY
*.FAL_CLIENT=STANDBY
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=STANDBY
*.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY'
*.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_2='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
*.log_archive_dest_3='SERVICE=STANDBY2 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY2'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=DEFER
*.LOG_ARCHIVE_DEST_STATE_3=DEFER
*.LOG_ARCHIVE_MAX_PROCESSES=30
STANDBY2 SETTINGS
*.FAL_SERVER=PRIMARY
*.FAL_CLIENT=STANDBY2
*.STANDBY_FILE_MANAGEMENT=AUTO
*.DB_UNIQUE_NAME=STANDBY2
*.LOG_FILE_NAME_CONVERT='PRIMARY','STANDBY2'
*.log_archive_dest_1=LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=STANDBY2'
*.log_archive_dest_2='SERVICE=STANDBY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STANDBY'
*.log_archive_dest_3='SERVICE=PRIMARY LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PRIMARY'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=DEFER
*.LOG_ARCHIVE_DEST_STATE_3=DEFER
*.LOG_ARCHIVE_MAX_PROCESSES=30
Edited by: mseberg on Nov 29, 2010 9:39 AM
The first test slapped me. Looking at 409013.1 Cascaded Standby Databases
Edited by: mseberg on Nov 29, 2010 12:49 PM

Oracle data guard configuration for primary and standby db_name

I am working on configuring an active data guard for one primary DB and one standby DB. I have a few questions:
1. Can I use different db_name, db_unique_name and instance_name for primary and standby. For example: primary(db_name, db_unique_name and instance_name)=chicago. When I create standby DB with Rman backup and copy of pfile and control file from primary DB or use Grid control to create standby database. Oracle document or Grid control all keep standby db_name=chicago. Only make standby db_unique_name and instance_name=boston. Due to my application system condition, I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?
2. In primary datafiles, application system generate datafile name like this: hr_chicago_01.dbf, fn_chicago_01.dbf. When I move datafiles to standby server, if I plan to use db_name=boston for standby DB, can I rename datafiles as
hr_boston_01.dbf, fn_boston_01.dbf? In this way, datafile name match up with db_name. but I will create standby log group and members on primary and standby identically. If in future switching over, DB will not have problems.
3. If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standby. Then "alter database backup controlfile to trace" from promary and also " create pfile='/xxx/initSTANDBY.ora' from primary. Then modify init.ora and controlfile. Then run control.sql to bring standby DB up. After that, configure redo log shipping and apply with data guard or SQL. Is this a acceptable way to create physical standby DB?
Please advise your comments. Thanks in advance.

I want to make db_name=boston, not keep it as the same as primary=chicago. Is this valid configuration?NO. DB_NAME must be the same ("chicago") at both sites. The Standby will be using a different DB_UNIQUE_NAME (e.g. "boston") and can be using a different Instance name / SID (e.g. "boston").
can I rename datafiles Yes. The database file names can be changed.
If I don't use primary DB backup. Instead, I copy all datafiles, redo_log files (no control files) to standbyWhat is the difference between the first sentence (a backup of the primary) and the second sentence (a copy of the primary) ? A Copy is a backup.
Are you intending to differentiate between an RMAN Backup and a User-Managed (aka "scripted") backup ?
Normally, for DataGuard, tou can use non-RMAN methods to copy the database but there's no value add in this.
You'd still have to setup DataGuard ! (and I wonder if you'd have complications setting up Active DataGuard).
But remember that you MUST create the Standby controlfile from the Primary and copy it over to your Standby -- particularly as you are planning to use DataGuard. This is not created by 'alter database backup controlfile to trace' , but by 'ALTER DATABASE CREATE STANDBY CONTROLFILE AS 'filename''
Hemant K Chitale

Oracle11g R2 Active Data guard using ASM Problem?

I have configured oracle11g r2 RAC on 2 notes using ASM Grid ( OS unix).
RAC is up and running.
Now I am configuring Active data Guard.
Under grid user instance +ASM and listener is running.
Under oracle user static listener is running.
All disk is mounted.
Oracle RAC and Data Guard directory and structure I have keeped same.
Now my problem is below:
$ ./rman target sys/HPinvent123nbl@dcpdb AUXILIARY sys/HPinvent123nbl@drpdb
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Jan 16 16:28:32 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: DCPDB (DBID=316773134)
connected to auxiliary database: DRPDB (not mounted)
RMAN> duplicate target database for standby from active database;
Starting Duplicate Db at 16-JAN-13
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=5644 device type=DISK
contents of Memory Script:
backup as copy reuse
targetfile '/u02/app/oracle/product/11.2.0/dbhome_1/dbs/orapwdcpdb1' auxiliary format
'/u02/app/oracle/product/11.2.0/dbhome_1/dbs/orapwdrpdb' ;
executing Memory Script
Starting backup at 16-JAN-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=1897 instance=dcpdb1 device type=DISK
Finished backup at 16-JAN-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/16/2013 16:28:48
RMAN-06136: ORACLE error from auxiliary database: ORA-00200: control file could not be created
ORA-00202: control file: '+data'
ORA-17502: ksfdcre:4 Failed to create file +data
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15055: unable to connect to ASM instance
ORA-01031: insufficient privileges
RMAN>
Please help.\
Thanks
Solaiman

root@drpdb1 []# id oracle
uid=108(oracle) gid=700(oinstall) groups=701(dba)
root@drpdb1 []# id grid
uid=109(grid) gid=700(oinstall) groups=701(dba),702(asmdba)
Edited by: 876149 on Jan 16, 2013 3:19 AM

Data Guard Failover after primary site network failure or disconnect.

Hello Experts:
I'll try to be clear and specific with my issue:
Environment:
Two nodes with NO shared storage (I don't have an Observer running).
Veritas Cluser Server (VCS) with Data Guar Agent. (I don't use the Broker. Data Guard agent "takes care" of the switchover and failover).
Two single instance databases, one per node. NO RAC.
What I'm being able to perform with no issues:
Manual switch(over) of the primary database by running VCS command "hagrp -switch oraDG_group -to standby_node"
Automatic fail(over) when primary node is rebooted with "reboot" or "init"
Automatic fail(over) when primary node is shut down with "shutdown".
What I'm NOT being able to perform:
If I manually unplug the network cables from the primary site (all the network, not only the link between primary and standby node so, it's like a server unplug from the energy source).
Same situation happens if I manually disconnect the server from the power.
This is the alert logs I have:
This is the portion of the alert log at Standby site when Real Time Replication is working fine:
Recovery of Online Redo Log: Thread 1 Group 4 Seq 7 Reading mem 0
Mem# 0: /u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log
At this moment, node1 (Primary) is completely disconnected from the network. SEE at the end when the database (standby which should be converted to PRIMARY) is not getting all the archived logs from the Primary due to the abnormal disconnect from the network:
Identified End-Of-Redo (failover) for thread 1 sequence 7 at SCN 0xffff.ffffffff
Incomplete Recovery applied until change 15922544 time 12/23/2013 17:12:48
Media Recovery Complete (primary_db)
Terminal Recovery: successful completion
Forcing ARSCN to IRSCN for TR 0:15922544
Mon Dec 23 17:13:22 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival ErrorAttempt to set limbo arscn 0:15922544 irscn 0:15922544
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
Resetting standby activation ID 2071848820 (0x7b7de774)
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Mon Dec 23 17:13:33 2013
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Terminal Recovery: applying standby redo logs.
Terminal Recovery: thread 1 seq# 7 redo required
Terminal Recovery:
Recovery of Online Redo Log: Thread 1 Group 4 Seq 7 Reading mem 0
Mem# 0: /u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log
Identified End-Of-Redo (failover) for thread 1 sequence 7 at SCN 0xffff.ffffffff
Incomplete Recovery applied until change 15922544 time 12/23/2013 17:12:48
Media Recovery Complete (primary_db)
Terminal Recovery: successful completion
Forcing ARSCN to IRSCN for TR 0:15922544
Mon Dec 23 17:13:22 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival ErrorAttempt to set limbo arscn 0:15922544 irscn 0:15922544
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
Resetting standby activation ID 2071848820 (0x7b7de774)
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Mon Dec 23 17:13:33 2013
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH
Attempt to do a Terminal Recovery (primary_db)
Media Recovery Start: Managed Standby Recovery (primary_db)
started logmerger process
Mon Dec 23 17:13:33 2013
Managed Standby Recovery not using Real Time Apply
Media Recovery failed with error 16157
Recovery Slave PR00 previously exited with exception 283
ORA-283 signalled during: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH...
Mon Dec 23 17:13:34 2013
Shutting down instance (immediate)
Shutting down instance: further logons disabled
Stopping background process MMNL
Stopping background process MMON
License high water mark = 38
All dispatchers and shared servers shutdown
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
ALTER DATABASE DISMOUNT
Shutting down archive processes
Archiving is disabled
Mon Dec 23 17:13:38 2013
Mon Dec 23 17:13:38 2013
Mon Dec 23 17:13:38 2013
ARCH shutting downARCH shutting down
ARCH shutting down
ARC0: Relinquishing active heartbeat ARCH role
ARC2: Archival stopped
ARC0: Archival stopped
ARC1: Archival stopped
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Dec 23 17:13:40 2013
Stopping background process VKTM
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Mon Dec 23 17:13:43 2013
Instance shutdown complete
Mon Dec 23 17:13:44 2013
Adjusting the default value of parameter parallel_max_servers
from 1280 to 470 due to the value of parameter processes (500)
Starting ORACLE instance (normal)
************************ Large Pages Information *******************
Per process system memlock (soft) limit = 64 KB
Total Shared Global Region in Large Pages = 0 KB (0%)
Large Pages used by this instance: 0 (0 KB)
Large Pages unused system wide = 0 (0 KB)
Large Pages configured system wide = 0 (0 KB)
Large Page size = 2048 KB
RECOMMENDATION:
Total System Global Area size is 3762 MB. For optimal performance,
prior to the next instance restart:
1. Increase the number of unused large pages by
at least 1881 (page size 2048 KB, total size 3762 MB) system wide to
get 100% of the System Global Area allocated with large pages
2. Large pages are automatically locked into physical memory.
Increase the per process memlock (soft) limit to at least 3770 MB to lock
100% System Global Area's large pages into physical memory
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Initial number of CPU is 32
Number of processor cores in the system is 16
Number of processor sockets in the system is 2
CELL communication is configured to use 0 interface(s):
CELL IP affinity details:
    NUMA status: NUMA system w/ 2 process groups
    cellaffinity.ora status: cannot find affinity map at '/etc/oracle/cell/network-config/cellaffinity.ora' (see trace file for details)
CELL communication will use 1 IP group(s):
    Grp 0:
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =88
LICENSE_MAX_USERS = 0
SYS auditing is disabled
NUMA system with 2 nodes detected
Starting up:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options.
ORACLE_HOME = /u01/oracle/product/11.2.0.4
System name:    Linux
Node name:      node2.localdomain
Release:        2.6.32-131.0.15.el6.x86_64
Version:        #1 SMP Tue May 10 15:42:40 EDT 2011
Machine:        x86_64
Using parameter settings in server-side spfile /u01/oracle/product/11.2.0.4/dbs/spfileprimary_db.ora
System parameters with non-default values:
processes                = 500
sga_target               = 3760M
control_files            = "/u02/oracle/orafiles/primary_db/control01.ctl"
control_files            = "/u01/oracle/fast_recovery_area/primary_db/control02.ctl"
db_file_name_convert     = "standby_db"
db_file_name_convert     = "primary_db"
log_file_name_convert    = "standby_db"
log_file_name_convert    = "primary_db"
control_file_record_keep_time= 40
db_block_size            = 8192
compatible               = "11.2.0.4.0"
log_archive_dest_1       = "location=/u02/oracle/archivelogs/primary_db"
log_archive_dest_2       = "SERVICE=primary_db ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=primary_db"
log_archive_dest_state_2 = "ENABLE"
log_archive_min_succeed_dest= 1
fal_server               = "primary_db"
log_archive_trace        = 0
log_archive_config       = "DG_CONFIG=(primary_db,standby_db)"
log_archive_format       = "%t_%s_%r.dbf"
log_archive_max_processes= 3
db_recovery_file_dest    = "/u02/oracle/fast_recovery_area"
db_recovery_file_dest_size= 30G
standby_file_management = "AUTO"
db_flashback_retention_target= 1440
undo_tablespace          = "UNDOTBS1"
remote_login_passwordfile= "EXCLUSIVE"
db_domain                = ""
dispatchers              = "(PROTOCOL=TCP) (SERVICE=primary_dbXDB)"
job_queue_processes      = 0
audit_file_dest          = "/u01/oracle/admin/primary_db/adump"
audit_trail              = "DB"
db_name                  = "primary_db"
db_unique_name           = "standby_db"
open_cursors             = 300
pga_aggregate_target     = 1250M
dg_broker_start          = FALSE
diagnostic_dest          = "/u01/oracle"
Mon Dec 23 17:13:45 2013
PMON started with pid=2, OS id=29108
Mon Dec 23 17:13:45 2013
PSP0 started with pid=3, OS id=29110
Mon Dec 23 17:13:46 2013
VKTM started with pid=4, OS id=29125 at elevated priority
VKTM running at (1)millisec precision with DBRM quantum (100)ms
Mon Dec 23 17:13:46 2013
GEN0 started with pid=5, OS id=29129
Mon Dec 23 17:13:46 2013
DIAG started with pid=6, OS id=29131
Mon Dec 23 17:13:46 2013
DBRM started with pid=7, OS id=29133
Mon Dec 23 17:13:46 2013
DIA0 started with pid=8, OS id=29135
Mon Dec 23 17:13:46 2013
MMAN started with pid=9, OS id=29137
Mon Dec 23 17:13:46 2013
DBW0 started with pid=10, OS id=29139
Mon Dec 23 17:13:46 2013
DBW1 started with pid=11, OS id=29141
Mon Dec 23 17:13:46 2013
DBW2 started with pid=12, OS id=29143
Mon Dec 23 17:13:46 2013
DBW3 started with pid=13, OS id=29145
Mon Dec 23 17:13:46 2013
LGWR started with pid=14, OS id=29147
Mon Dec 23 17:13:46 2013
CKPT started with pid=15, OS id=29149
Mon Dec 23 17:13:46 2013
SMON started with pid=16, OS id=29151
Mon Dec 23 17:13:46 2013
RECO started with pid=17, OS id=29153
Mon Dec 23 17:13:46 2013
MMON started with pid=18, OS id=29155
Mon Dec 23 17:13:46 2013
MMNL started with pid=19, OS id=29157
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
ORACLE_BASE from environment = /u01/oracle
Mon Dec 23 17:13:46 2013
ALTER DATABASE   MOUNT
ARCH: STARTING ARCH PROCESSES
Mon Dec 23 17:13:50 2013
ARC0 started with pid=23, OS id=29210
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Successful mount of redo thread 1, with mount id 2071851082
Mon Dec 23 17:13:51 2013
ARC1 started with pid=24, OS id=29212
Allocated 15937344 bytes in shared pool for flashback generation buffer
Mon Dec 23 17:13:51 2013
ARC2 started with pid=25, OS id=29214
Starting background process RVWR
ARC1: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
Mon Dec 23 17:13:51 2013
RVWR started with pid=26, OS id=29216
Physical Standby Database mounted.
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Mon Dec 23 17:13:51 2013
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
         USING CURRENT LOGFILE DISCONNECT FROM SESSION
Attempt to start background Managed Standby Recovery process (primary_db)
Mon Dec 23 17:13:51 2013
MRP0 started with pid=27, OS id=29219
MRP0: Background Managed Standby Recovery process started (primary_db)
ARC2: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
ARC2: Becoming the heartbeat ARCH
ARC2: Becoming the active heartbeat ARCH
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival Error
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
At this moment, I've lost service and I have to wait until the prmiary server goes up again to receive the missing log.
This is the rest of the log:
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:13:52
Tracing not turned on.
Tns error struct:
    ns main err code: 12543
TNS-12543: TNS:destination host unreachable
    ns secondary err code: 12560
    nt main err code: 513
TNS-00513: Destination host unreachable
    nt secondary err code: 113
    nt OS err code: 0
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:13:55
Tracing not turned on.
Tns error struct:
    ns main err code: 12543
TNS-12543: TNS:destination host unreachable
    ns secondary err code: 12560
    nt main err code: 513
TNS-00513: Destination host unreachable
    nt secondary err code: 113
    nt OS err code: 0
started logmerger process
Mon Dec 23 17:13:56 2013
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery terminated with error 16157
Errors in file /u01/oracle/diag/rdbms/standby_db/primary_db/trace/primary_db_pr00_29230.trc:
ORA-16157: media recovery not allowed following successful FINISH recovery
Managed Standby Recovery not using Real Time Apply
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE
         USING CURRENT LOGFILE DISCONNECT FROM SESSION
Recovery Slave PR00 previously exited with exception 16157
MRP0: Background Media Recovery process shutdown (primary_db)
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:13:58
Tracing not turned on.
Tns error struct:
    ns main err code: 12543
TNS-12543: TNS:destination host unreachable
    ns secondary err code: 12560
    nt main err code: 513
TNS-00513: Destination host unreachable
    nt secondary err code: 113
    nt OS err code: 0
Mon Dec 23 17:14:01 2013
Fatal NI connect error 12543, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=node1)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=primary_db)(CID=(PROGRAM=oracle)(HOST=node2.localdomain)(USER=oracle))))
VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.4.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
Time: 23-DEC-2013 17:14:01
Tracing not turned on.
Tns error struct:
    ns main err code: 12543
TNS-12543: TNS:destination host unreachable
    ns secondary err code: 12560
    nt main err code: 513
TNS-00513: Destination host unreachable
    nt secondary err code: 113
    nt OS err code: 0
Error 12543 received logging on to the standby
FAL[client, ARC0]: Error 12543 connecting to primary_db for fetching gap sequence
Archiver process freed from errors. No longer stopped
Mon Dec 23 17:15:07 2013
Using STANDBY_ARCHIVE_DEST parameter default value as /u02/oracle/archivelogs/primary_db
Mon Dec 23 17:19:51 2013
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance primary_db - Archival Error
ORA-16014: log 4 sequence# 7 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/u02/oracle/fast_recovery_area/standby_db/onlinelog/o1_mf_4_9c3tk3dy_.log'
Mon Dec 23 17:26:18 2013
RFS[1]: Assigned to RFS process 31456
RFS[1]: No connections allowed during/after terminal recovery.
Mon Dec 23 17:26:47 2013
flashback database to scn 15921680
ORA-16157 signalled during: flashback database to scn 15921680...
Mon Dec 23 17:27:05 2013
alter database recover managed standby database using current logfile disconnect
Attempt to start background Managed Standby Recovery process (primary_db)
Mon Dec 23 17:27:05 2013
MRP0 started with pid=28, OS id=31481
MRP0: Background Managed Standby Recovery process started (primary_db)
started logmerger process
Mon Dec 23 17:27:10 2013
Managed Standby Recovery starting Real Time Apply
MRP0: Background Media Recovery terminated with error 16157
Errors in file /u01/oracle/diag/rdbms/standby_db/primary_db/trace/primary_db_pr00_31486.trc:
ORA-16157: media recovery not allowed following successful FINISH recovery
Managed Standby Recovery not using Real Time Apply
Completed: alter database recover managed standby database using current logfile disconnect
Recovery Slave PR00 previously exited with exception 16157
MRP0: Background Media Recovery process shutdown (primary_db)
Mon Dec 23 17:27:18 2013
RFS[2]: Assigned to RFS process 31492
RFS[2]: No connections allowed during/after terminal recovery.
Mon Dec 23 17:28:18 2013
RFS[3]: Assigned to RFS process 31614
RFS[3]: No connections allowed during/after terminal recovery.
Do you have any advice?
Thanks!
Alex.

Hello;
What's not clear to me in your question at this point:
What I'm NOT being able to perform:
If I manually unplug the network cables from the primary site (all the network, not only the link between primary and standby node so, it's like a server unplug from the energy source).
Same situation happens if I manually disconnect the server from the power.
This is the alert logs I have:"
Are you trying a failover to the Standby?
Please advise.
Is it possible your "valid_for clause" is set incorrectly?
Would also review this:
ORA-16014 and ORA-00312 Messages in Alert.log of Physical Standby
Best Regards
mseberg

Data guard difference in primary and standby OS.

Dear All,
We are planning to setup a data guard in our landscape. But my question what are the prerequisites should be consider before getting in to that.
Like my environment -
1. The primary database is running with Red hat Linux 5 - IBM 64 bit and the standby database is Redhat Linux 2.1 IBM 32 bit system.
2. The primary database is running with Red hat Linux 5 - IBM 64 bit with oracle 8.1.7.4 and the standby database is
Linux 2.1 IBM 32 bit system with oracle 10g.
Is the above thing is possible? or we should maintain the same OS / DB combination in the data guard setup.
I am following the below link.
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14239/standby.htm#i72053
If anyone have thoughts on this please do advice me.
Regards
Vijay

Please explain to us what exactly you want to do with the standby database?
According to note 105047 - Support for Oracle functions in the SAP environment
12. Data Guard
You can use "Physical Standby", but Oracle provides support (not SAP).
You cannot use "Logical Standby"
So in short, no a data guard configuration with Red hat Linux 5 - IBM 64 bit with oracle 8.1.7.4 to Linux 2.1 IBM 32 bit system with oracle 10g is NOT possible.
Regards, Michael

Create Data Guard Using ASM Managed RMAN backup

we have an oracle database 11.1.0.7 working on Windows server 2003 (64bit). The storage in ASM managed (same 11.1.0.7). Our total database size is 4TB.
I will have to create a physical standby database (Data Guard) of this instance. Now I am having issues on how to transport my RMAN backup pieces (which is also ASM managed).
I cannot do an over the network RMAN backup because it will take months to complete.
We have external 4 hard disks (2 TB each). But my RMAN backup pieces are ASM in format.
Any ideas on how to easily create a data guard in this set up.

TheAlchemist wrote:
can you provide us any clear steps....Hope you asked for Restoring from backups.
1) Prepare PFILE and put in nomount status.
2) Restore standby controlfile
RMAN> restore standby controlfile from '+DG/...'
3) Mount controlfile
SQL> alter database mount standby database;
4) Restore database.
If you are restoring into another diskgroups, then use as below.
RUN {
SET NEWNAME FOR DATAFILE 1 TO '+Dg1/....';
SET NEWNAME FOR DATAFILE 2 TO "+Dg1/...';
RESTORE DATABASE
If same diskgroup you want to use then, just give RMAN> restore database;
After successful restore
5) Start MRP
SQL> alter database recover managed standby database disconnect from session;

Listeners Problem oracle11g R2 Data Guard RAC?

Hi,
I want to Static Register LISTENERDB in Data Guard RAC.
LSNRCTL> start listenerdb
Starting /u02/app/oracle/product/11.2.0/dbhome_1/bin/tnslsnr: please wait...
TNSLSNR for HPUX: Version 11.2.0.1.0 - Production
System parameter file is /u02/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Log messages written to /u02/app/oracle/diag/tnslsnr/drpdb1/listenerdb/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENERDB)))
TNS-01155: Incorrectly specified SID_LIST_listenerdb parameter in LISTENER.ORA
NL-00303: syntax error in NV string
Listener failed to start. See the error message(s) above...
LSNRCTL>
Listene.ora file: user Oracle
LISTENERDB=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENERDB)))) # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENERDB=ON # line added by Agent
SID_LIST_LISTENERDB =
(SID_LIST =
(SID_DESC =
(ORACLE_HOME = /u02/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = drpdb1)
(GLOBAL_DBNAME = drpdb.nblitd.com)
Please help
Thanks
Solaiman

Hi,
Please check below thread. Seems like same problem.
http://www.orafaq.com/forum/t/87764/2/
Cheers
Sush

Data Guard -- v$archive_log applied column shows wrong info

I'm playing with 10g Data Guard. Both Primary and Physical Standby are in Maximum Availability mode. When I query v$archived_log column applied for dest_id=2 (which is physical standby) for some files it shows NO value but alert log on both primary and standby shows file transferred info. Even on physical standby v$archived_log shows log is applied YES value. My question is : So why is Primary database's v$archived_log shows value NO ?
I am trying to setup crontab so that once I see value YES in primary's v$archived_log for dest_id = 2 then I can backup archived log file and delete it from primary database machine. But my perl script won't work because primary v$archived_log shows value NO for applied column for dest_id = 2.
Thanks.

Hi OrionNet,
I think I am looking at the wrong column and also on the wrong database for what I need to do. Let me explain what I am trying to achieve.
I have a shell script to check if archived logs are shipped from Primary to Standby AND if Standby successfully applied it or not. My shell script was looking at Primary databases using following query
select sequence#, archived, applied
from v$archived_log
where dest_id = 2 -- running on Primary BUT looking at standby archived log destination
order by sequence# ;
SEQUENCE# ARCHIEVED APPLIED
=====================
58 YES YES
59 YES YES
*60* YES NO
61 YES YES
After reading [v$archived_log reference entry in manual|http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_1016.htm#REFRN30011]
APPLIED Indicates whether the archivelog has been applied to its corresponding standby database (YES) or not (NO). The value is always NO for local destinations.
This column is meaningful at the physical standby site for the ARCHIVED_LOG entries with REGISTRAR='RFS' (which means this log is shipped from the primary to the standby database). If REGISTRAR='RFS' and APPLIED is NO, then the log has arrived at the standby but has not yet been applied. If REGISTRAR='RFS' and APPLIED is YES, the log has arrived and been applied at the standby database.
You can use this field to identify archivelogs that can be backed up and removed from disk.
I think I should use following query on Standby database and not on primary database
select sequence#, registrar, applied
from v$archived_log
where dest_id = 1 -- query running on standby so dest_id = 1 which is standby archive log destination
and registrar = 'RFS'
order by sequence# ;
SEQUENCE# REGISTRAR APPLIED
=====================
58 RFS YES
59 RFS YES
*60* RFS YES
61 RFS YES
So, my shell script should connect to standby database from primary database and evaluate which archive logs to delete after backup from primary machine.
Now I'll generate some gaps on Standby and check query again to make sure what I understand and expect is correct.
Hope I am clear now. Thanks for your help. My bad, I didn't read the manual correctly the first time.

Steps for data guard RAC primary RAC standby

Hi,
I have some doubt in configuring data guard for rac DR to rac primary.
1) In RAC DR, physical standby will be in RAC before starting data guard for RAC Primary , right?.
2) While configuring RAC DR , should one node be down in standby?.
3) After creating the auxiliary database in standby, i mean restoring the rman backup from staging directory in DR,
Shall we have to register the services(database,instance,asm,etc..) to CRS(OCR)?. If yes ,Why?.
4) After DR configure over , Shall i shut/down one node?. Should all the nodes in DR be in up , while applying logs to
standby ?.
If anybody have made the setup and have the prepared document , requesting you to share with me.
Thank you very much,
Sunand

Hi Sunand,
Please follow the following My Oracle Support (MOS) Document ID:
MAA - Creating a RAC Physical Standby for a RAC Primary [ID 380449.1]
For further details, see the referred documents in previous post. Try practicing on VMWare because it will give you the flexibility for creating snapshots to save your work. Please see the answers for your question below:
Q1. In RAC DR, physical standby will be in RAC before starting data guard for RAC Primary , right?.
Answer: Yes, this is recommend but not mandatory. You can add a second node later on.
Q2. While configuring RAC DR , should one node be down in standby?
Answer: Yes, there are some database configuration commands that should be run in exclusive mode. You can start the remaining instance(s) after DB creation. Do not forget to set CLUSTER_DATABASE parameter to TRUE. Also, all instances except one should be close while performing switchover/failover.
Q3. After creating the auxiliary database in standby, i mean restoring the rman backup from staging directory in DR, Shall we have to register the services(database,instance,asm,etc..) to CRS(OCR)?. If yes ,Why?
Answer: Yes, this is recommended for RAC configuration to take advantage of high availability services.
Q4. After DR configure over , Shall i shut/down one node?. Should all the nodes in DR be in up , while applying logs to
standby ?
Answer: You can start up all the instances after DR creation. In this case if your one node goes down log apply services will continue to apply changes in DR.
Hope, this helps to clear your questions.
Regards,
Shahid

DATA GUARD IN ACTIVE PASSIVE OS CLUSTER WINDOWS

Hello Gurus
I am setting up data guard in sap on windows with active passive OS clustering.
Please clear below 3 confusions.
1)I have same database name and sid of standby database as primary.Now to have different service i am just using it in setting parameters and tns_alias like
Listener file for primary and standby same as sid same
SID_LIST_LISTENER=
(SID_LIST=
(SID_DESC=
(GLOBAL_DBNAME=PROD)
(ORACLE_HOME=/oracle/product/11.2.0)
(SID_NAME=PROD)
tNSNAMES adding entry on primary as
PROD2
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=dev-db2)
(port=1521)
(connect_data=
(service_name=prod2
server=dedicated)))
tnsnames added entry on standby of primary
PROD
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)(HOST=dev-db2)
(port=1521)
(connect_data=
(service_name=prod
server=dedicated)))
---->in parameter i am using service for standby as
alter system set log_archive_dest_2='service=PROD2 async valid_for=(online_logfile,primary_role) db_unique_name=prod2;
**But i have am not creating any service as such.Will THIS WORK and alright.
as i am having confusion that my SID is same so how service be differentiated.am i doing right way.
2)as my primary database having 2 node in OS cluster so like node1 having ip 192.68.2.22 node 2 ip 192.68.2.23..They are in active passive clusten.the datafiles and other oracle files can be shifted to any node as per requirement.So they are using a virtual ip 192.68.2.20.. Now i need to create standby for this primary....standby ip is 192.68.2.40
So in tnsnames i am giving all ips the virtual ip 192.68.2.20 and host ips of both nodes on standby tnsnames and on primary adding entry of standby ip 192.68.2.40.Means i am doing entries of virtual ip and host of node1 and node2.
So i am able to ping the virtual ip from standby but not able to ping 192.68.2.22 and 192.68.2.23.
So is it fine .Would i be able to create standby database as only virtual will be needed or i am going on wrong path.
3)Can i just create the standby database by using duplicate command without taking backup in 11g.(means without physical copy of data files etc from primary to standby)
likewise
On the primary server, connect to Primary database(ORCL) as target and standby database(ORCL_DTGD) as auxiliary.
$ rman target sys/sys@ORCL auxiliary sys/sys@ORCL_DTGD
RMAN>DUPLICATE TARGET DATABASE FOR STANDBY FROM ACTIVE DATABASE DORECOVER
SPFILE SET DB_UNIQUE_NAME='ORCL_DTGD' SET LOG_ARCHIVE_DEST_2='service=ORCL LGWR SYNC REGISTER VALID_FOR=(online_logfile,primary_role)' Set STANDBY_FILE_MANAGEMENT='AUTO' SET FAL_SERVER='ORCL' SET FAL_CLIENT='ORCL_DTGD' SET CONTROL_FILES='/data/oracle/app/oracle/oradata/ORCL/control01.ctl’,'/data/oracle/app/oracle/fast_recovery_area/ORCL/control02.ctl’ NOFILENAMECHECK;
after configuring tns,listener etc
Regards
thanks for ur time..please reply as i am really looking for ur great ideas and need them.

For Question 1:
The SERVICE attribute, which is a mandatory attribute for a redo transport
destination, must be the first attribute specified in the attribute list. The SERVICE
attribute is used to specify the Oracle Net service name used to connect to the redo
transport destination. The service name must be resolvable through an Oracle Net
naming method to an Oracle Net connect descriptor that matches the Oracle Net
listener(s) at the redo transport destination.
Source - 6.2.2 Configuring an Oracle Database to Send Redo Data
Concepts and Administration 11g Release 2 (11.2) E10700-02
For Question 2:
I would DNS if possible. If you cannot see IP's you can add them the the HOSTs file on most OS's as a work around.
Not sure what you are trying to do exactly.
For Question 3:
Yes.
Duplicate for Standby using active duplicate.
Example
http://www.visi.com/~mseberg/data_guard/standby_creation_from_active_database_using_rman.html
Best Regards
mseberg

Data Guard configuration for RAC database disappeared from Grid control

Primary Database Environment - Three node cluster
RAC Database 10.2.0.1.0
Linux Red Hat 4.0 2.6.9-22 64bit
ASM 10.2.0.1.0
Management Agent 10.2.0.2.0
Standby Database Environment - one Node database
Oracle Enterprise Edition 10.2.0.1.0 Single standby
Linux Red Hat 4.0 2.6.9-22 64bit
ASM 10.2.0.1.0
Management Agent 10.2.0.2.0
Grid Control 10.2.0.1.0 - Node separate from standby and cluster environments
Oracle 10.1.0.1.0
Grid Control 10.2.0.1.0
Red Hat 4.0 2.6.9-22 32bit
After adding a logical standby database through Grid Control for a RAC database, I noticed sometime later the Data Guard configuration disappeared from Grid Control. Not sure why but it is gone. I did notice that something went wrong with the standby creation but i did not get much feedback from Grid Control. The last thing I did was to view the configuration, see output below.
Initializing
Connected to instance qdcls0427:ELCDV3
Starting alert log monitor...
Updating Data Guard link on database homepage...
Data Protection Settings:
Protection mode : Maximum Performance
Log Transport Mode settings:
ELCDV.qdx.com: ARCH
ELXDV: ARCH
Checking standby redo log files.....OK
Checking Data Guard status
ELCDV.qdx.com : ORA-16809: multiple warnings detected for the database
ELXDV : Creation status unknown
Checking Inconsistent Properties
Checking agent status
ELCDV.qdx.com
qdcls0387.qdx.com ... OK
qdcls0388.qdx.com ... OK
qdcls0427.qdx.com ... OK
ELXDV ... WARNING: No credentials available for target ELXDV
Attempting agent ping ... OK
Switching log file 672.Done
WARNING: Skipping check for applied log on ELXDV : disabled
Processing completed.
Here are the steps followed to add the standby database in Grid Control
Maintenance tab
Setup and Manage Data Guard
Logged in as sys
Add standby database
Create a new logical standby database
Perform a live backup of the primary database
Specify backup directory for staging area
Specify standby database name and Oracle home location
Specify file location staging area on standby node
At the end am presented with a review of the selected options and then the standby database is created
Has any body come across a similar issue?
Thanks,

Any resolution on this?
I just created a Logical Standby database and I'm getting the same warning (WARNING: No credentials available for target ...) when I do a 'Verify Configuration' from the Data Guard page.
Everything else seems to be working fine. Logs are being applied, etc.
I can't figure out what credentials its looking for.

Grid Control and Data Guard Setup

Hi,
I have 4 PCs on which I wish to test the following:
1. OEM Grid Control 10.2 - Console + Service + Agent
2. Data Guard feature with Broker
3. Standby Setup for a Primary Database.
I will create the Primary DB on one Linux PC.
Standby DB using Grid Control & DataGuard on second Linux PC.
The Third PC is also Linux but the fourth PC is Windows XP.
Please guide me in understanding the following:
1. On which PCs should I install OEM Grid Control 10.2 - Console + Service + Agent?
2. On which PC should I setup DB Broker?
Please assume that I will use Oracle 10.2 Softwares and Linux x86 version.
Regards

well why don't you go ahead and test?!
Test and see whether you want to put oms, console all one machine, or whether you want to separate out the componests (you'll need an agent on each box regardless). I have no idea what the specs of your machines are, so why don't read the documentation on Grid and dataguard, see what the recommended settings are and then plan what you want to do.
Bazza

Oracle Data Guard 9i

This is a quote from an Oracle publication on Oracle Data Guard 9i.
"Oracle Data Guard's new SQL Apply feature creates a "logical standby" that enables continuous access to a working copy of your primary database. With SQL Apply, the standby database is continuously available for reporting and other operations, while always at-the-ready for unplanned failovers. Data Guard provides log shipping, remote mirroring, zero-data-loss disaster protection, and a single point of control and automation. "
My question is: Is the standby database open in read-write or read-only mode?
If, its only read, is there ANY other way read-write version of a database could be created at a remote site besides:
a) Complete copying - duplicate database at remote site open in read-write.
b) Distributed database - replication - remote users access their own version and the two keep themselves in sync.
c) Parallel server - one database - two instances.

Data Guard is available for Linux (within Oracle9i).
It's a tool to make it much more easier to create a standby
database, but I don't think it's required!
Regards,
Thomas.
Is Oracle 9i data guard for Linux available??
Well, my real question is, I need to setup 9i standby database
on Linux. Do I need data guard installed in order to setup
standby database??

Cloud 12.1.0.4: Creating a Data Guard Configuration asymetric

Hello,
I'd like to créate a Data Guard from Cloud Console.
The primary database is a RAC of two nodes, but the standby node is one node and I dont't like to use ASM.
The wizard , ask the target node , the Standby Instance Name, but in the step 3 show this error:
No ASM instance is being managed as an EM target on the selected standby host.
To create a standby database on the selected host, an ASM instance must be added as an EM target.
Is not posible to use from Cloud this mix of storage configuration?
Thanks
Arturo

Hi,
It is recommended to use ASM on both sides. Normally OEM Expects the Current DB structures on STBY OEM.
Please follow the bleow procedure will help you.
Data Guard – ASM primary to filesystem physical standby – using RMAN duplicate
https://pythianpang.wordpress.com/2009/07/07/data-guard-asm-primary-to-filesystem-physical-standby-using-rman-duplicate/
Regards
Krishnan

Oracle11g heterogenous data guard Linux-ASM primary, Windows-Filesystem standby

Similar Messages

Maybe you are looking for