Data Guard - Keeping same SID/Instance Name across both sites

Hello,
We are working on a project to move the databases from legacy to new servers. The migration plan is to use Data Guard option for our migration strategy. We would like to know followings.
1) Is it possible to build stand by databases with same instance name of legacy primary instances? If so, how it could be?
2) If not, we can build stand by database with different instance name (DB_UNIQUE_NAME). Do the switch over and cut off the replication with legacy primary database. Once done, What other alternative do we have to change the instance name same like legacy database instances?
The ultimate goal is to retain same DB name and instance name in new server with minimum downtime.
Database - 11.2.0.3.0
Database Type - Oracle restart and RAC
O.S. - RHEL 6.3
The requirement is have same DB name and instance name across sites.
Primary site - X node
Primary DB - EODSS
Primary DB instances - EODSS1, EODSS1
Standby Site - Y node
StandBy DB - EODS
StandBy instances - EODSS1, EODSS1
Thanks,
Pankaj
Edited by: user12025125 on Feb 22, 2013 12:33 PM

Hello;
1) Is it possible to build stand by databases with same instance name of legacy primary instances? If so, how it could be?
Yes. Not sure I understand the second part of the question. I like to think of a standby database and a primary database as the same database in different modes. RMAN treats them as the same. They have the same DBID.
2) If not, we can build stand by database with different instance name (DB_UNIQUE_NAME). Do the switch over and cut off the replication with legacy primary database. Once done, What other alternative do we have to change the instance name same like legacy database instances?
It should not matter what the database name is. Almost everything connects using an Alias. I find it easier to use a slightly different name for the Standby because then I know which site I'm working on. What I did was put an S in front of the name on the standby side to keep them apart in my mind. A tnsnames entry can handle the rest. So yes you can do that, but it might be harder to keep track that way.
ernie =
(DESCRIPTION =
    (ADDRESS_LIST =
       (ADDRESS = (PROTOCOL = TCP)(HOST = primary.server)(PORT = 1521))
       (ADDRESS = (PROTOCOL = TCP)(HOST = standby.server)(PORT = 1521))
       (CONNECT_DATA =
       (SERVICE_NAME = ernie)
)Best Regards
mseberg

Similar Messages

Configuring Data Guard on 2 different instance in same machine

Hi All,
I am new to the Data Guard concept. I am using Oracle 10g (Release 10.2.0.1.0) in Windows 7 environment . I have created 2 database instance its running fine.
For testing purpose, Is it possible to implement Data Guard concept between 2 instance in the same machine? whether it will impact any problem?
Thanks & Regards
Sami.

You would use the same one. That is, you would not have a separate tnsnames.ora and listener.ora.
What I was trying to say is you still need to add the SID_LIST_LISTENER lines that Data Guard uses
Example
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0)
(PROGRAM = extproc)
(SID_DESC =
(global_dbname = PRIMARY_DGMGRL.uservices.umn.edu)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0)
(sid_name = PRIMARY)
TNS Example
STANDBY =
(DESCRIPTION =
(SDU=32767)
(SEND_BUF_SIZE=2092500)
(RECV_BUF_SIZE=2092500)
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = HOSTNAME)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = STANDBY)
Best Regards
mseberg (Its very late here)

How to keep same sender file name for receiver mail attachement

Hi,
i am working with File to Mail scanario. There i want to pick a flat file from native file system and then send it as email attachment. Now i am able to send the file but the flat is getting converted as an xml file. is there any method to keep the same sender file name and type for receiver mail attachment. i am not using any mail package. i am using XI payload and keep attachments.
Thanks in advance.
-Siva

Hi,
Yes,With out using the mail package u can send the Mail Attachments to the receiver side,
In that case no need of Integration Repository objects.
Chck this links.
/people/prasad.ulagappan2/blog/2005/06/07/mail-adapter-scenarios-150-sap-exchange-infrastructure
/people/community.user/blog/2006/09/07/email-reporting
/people/community.user/blog/2006/09/08/email-report-as-attachment-excelword
/people/michal.krawczyk2/blog/2005/03/07/mail-adapter-xi--how-to-implement-dynamic-mail-address
/people/michal.krawczyk2/blog/2005/11/23/xi-html-e-mails-from-the-receiver-mail-adapter
If u dont get ur requirement then let me know ur Mail id i will send u a Doc.
Regards,
Phani
Reward points if Helpful

Data guard sid

Dear Gurus
I need to implemement data guard in sap.client is asking that on standby its required that sid be same as primary because sap uses it.
So is it possible to configure data guard with same sid's on primary and standby.
also as i keep sid same the directory structure would be same in that case like
on primary --E:\oracle\db\ppm
on standby- E:\oracle\db\ppm
so no need to use parameter db_file_name_convert and log_file_name_convert
so would it be a fine configuration of data guard
OS--Windows2008
Oracle 11g

user11221081 wrote:
Dear Gurus
I need to implemement data guard in sap.client is asking that on standby its required that sid be same as primary because sap uses it.
So is it possible to configure data guard with same sid's on primary and standby.
also as i keep sid same the directory structure would be same in that case like
on primary --E:\oracle\db\ppm
on standby- E:\oracle\db\ppm
so no need to use parameter db_file_name_convert and log_file_name_convert
so would it be a fine configuration of data guard
OS--Windows2008
Oracle 11g
i already updated in earlier thread, see my post here Re: Data guard in sap

Multiple instances single data guard

Hello everyone,
I am a newbie to this site . I wanted to know whether we can configure single data guard for multiple database (instances), has this been done anytime in the past .
I know this sounds weird but we are a small business and growing at rapid rate. we want to cut down the cost at the same time.
Besides this do you know any other method or approach that is practical and economical to synchronise database between multiple production system into centralised DR system
Sorry, If I posted it in the wrong section.
Thanks in advance for your help and time.
-N
Edited by: 960081 on Oct 17, 2012 12:36 PM

Hi,
A standby database cannot behave as both physical and logical standby at the same time. As I said earlier, a primary database can have multiple standby databases, you can have both logical and physical standby databases for your single primary provided the logical and physical standby databases are 2 databases and not just 1 database

Two nodes ASM has same instance name

Hi,
I created a two nodes ASM grid , when the grid installation(11.2.0.1) finished it created the +ASM1 as the instance name for both my nodes.
I did setup the ORACLE_SID to +ASM1 and +ASM2 for the node1 and node2 respectively before the installation.
Whats wrong I am doing for the grid installation? Please suggest.
Thanks

Hi,
For installing the grid infrastructure for cluster, yes for sure you need a shareable disks, in case of failure of one node then your data (diskgroup) is accessible on the other node.
You can add a new "Oracle VM virtualBox" Machine that works like a SAN Server (iSCSI):
Step 1: On SAN Server VM.
- Add for example 6 virtual disks (2 disks for OCR & Voting, 2 disks for DATA and 2 disks for FRA if you want).
- Install tgtd package.
- Configure the tgtd
Step 2: Then, on both Nodes:
- Install the iSCSI initiator.
- Install Device-Mapper-Multipath
- Start up the multipathd
I had written an article how to set up an SAN Server and Device-mapper-multipath.
I hope this can help you.
Best regards

Can the instance name of prod. database and standby database may be same

Hi all,
Actually I knew that while configuring Physical Standby
1> Database name should be same
2> Instance name should be different
But,today I saw a DR system where the database name and instance names are the same. So I came to know that it can be done.
I just wanted to know that what are the trade-offs of putting DB name and instance name same?

There isn't a tradeoff. By default, the instance_name is the same as the db_name unless if specified differently in teh pfile. What matters is the service name connecting to the instance.

Data Guard Broker connecting to standby database fails

Hello everybody
I checked lots of pages but I'm not able to find a solution für my problem. I already set up a primary and a standby database (prim = ALPHA1 / standby = ALPHA2).
After enabling my dgmgrl configuration I got two errors:
DGM-17016: failed to retrieve status for database "alpha2"
ORA-16664: unable to receive the result from a database
The dg log from ALPHA1 says:
06/04/2013 16:06:57
Site alpha2 returned ORA-16664.
Data Guard Broker Status Summary:
Type Name Severity Status
Configuration alphadgb Warning ORA-16607
Primary Database alpha1 Success ORA-00000
Physical Standby Database alpha2 Error ORA-16664
While the dg log from ALPHA2 (standby) says:
06/04/2013 16:43:28
SPFILE is missing value for property 'LogArchiveFormat' with sid='ALPHA2'
Warning: Property 'LogArchiveFormat' has inconsistent values:METADATA='arch_ALPHA2_%S_%t_%r.arc', SPFILE='(missing)', DATABASE='arch_ALPHA2_%S_%t_%r.arc'
Failed to connect to remote database alpha1. Error is ORA-12514
Failed to send message to site alpha1. Error code is ORA-12514.
How can I solve this issue? Every type of tnsping is successfull. The sqlplus login from the primary to the standby database works, the other way round works too! Therefore the tnsnames and listener data seems to be correct.
My configuration for ALPHA1 (primary db):
Listener
LISTENER_ALPHA1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
SID_LIST_LISTENER_ALPHA1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = ALPHA1_DGMGRL)
(ORACLE_HOME = /oracle/ALPHA1/orahome)
(SID_NAME = ALPHA1)
tnsnames.ora
ALPHA1.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(CONNECT_DATA =
(SID = ALPHA1)
ALPHA2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1522))
(CONNECT_DATA =
(SID = ALPHA2)
DG_ALPHA1.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = ALPHA1_DGMGRL)
DG_ALPHA2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1522))
(CONNECT_DATA =
(SERVICE_NAME = ALPHA2_DGMGRL)
Parameters
archive_lag_target integer 0
log_archive_config string DG_CONFIG=(ALPHA2,ALPHA1)
log_archive_dest string
log_archive_dest_1 string LOCATION=USE_DB_RECOVERY_FILE_DEST valid_for=(all_logfiles,all_roles) DB_UNIQUE_NAME=ALPHA2
log_archive_dest_2 string SERVICE=ALPHA1 SYNC valid_for=(online_logfiles,primary_role) DB_UNIQUE_NAME=ALPHA1
log_archive_format string arch_ALPHA2_%S_%t_%r.arc
log_archive_local_first boolean TRUE
log_archive_max_processes integer 4
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
standby_archive_dest string ?/dbs/arch
For the DG Broker configuration
DGMGRL>     connect sys/dgalpha42@DG_ALPHA1
DGMGRL>     create configuration ALPHADGB
DGMGRL>     primary database is ALPHA1
DGMGRL>     connect identifier is DG_ALPHA1
DGMGRL>     ;
DGMGRL>     add database ALPHA2
DGMGRL>     connect identifier is DG_ALPHA2
DGMGRL>     maintained as physical
DGMGRL>     ;
There were no errors.
DGMGRL> show database verbose ALPHA1
Database - alpha1
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
ALPHA1
Properties:
DGConnectIdentifier = 'dg_alpha1'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA2, ALPHA1'
LogFileNameConvert = 'ALPHA2, ALPHA1'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA1'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA1_DGMGRL)(INSTANCE_NAME=ALPHA1)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA1_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
SUCCESS
DGMGRL> show database verbose ALPHA2
Database - alpha2
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
ALPHA2
Properties:
DGConnectIdentifier = 'dg_alpha2'
ObserverConnectIdentifier = ''
LogXptMode = 'SYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA1, ALPHA2'
LogFileNameConvert = 'ALPHA1, ALPHA2'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA2'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA2_DGMGRL)(INSTANCE_NAME=ALPHA2)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA2_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DGM-17016: failed to retrieve status for database "alpha2"
ORA-16664: unable to receive the result from a database
Can anybody help me to find a solution for this?

Hey
thanks for the answer. I followed you recommendations but I got the same error again. I restored/recovered the old status and looked deeper into the dgmgrl configuration before enabling. I found an interesting point. (show database verbose ALPHAx)
Database - alpha1
Role: PRIMARY
Intended State: OFFLINE
Instance(s):
ALPHA1
Properties:
DGConnectIdentifier = 'dg_alpha1'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA2, ALPHA1'
LogFileNameConvert = 'ALPHA2, ALPHA1'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA1'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA1_DGMGRL)(INSTANCE_NAME=ALPHA1)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA1_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DISABLED
Database - alpha2
Role: PHYSICAL STANDBY
Intended State: OFFLINE
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
ALPHA2
Properties:
DGConnectIdentifier = 'dg_alpha2'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA1, ALPHA2'
LogFileNameConvert = 'ALPHA1, ALPHA2'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA2'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA2_DGMGRL)(INSTANCE_NAME=ALPHA2)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA2_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DISABLED
As the listener are configured ALPHA1 (prim) should be on port 1521 while ALPHA2 (stby) should work on 1522. In the configuration of DGMGRL only appears port 1521 (look at StaticConnectIdentifier). Is this maybe the reason of the networking problems with DG Broker? How can I fix this?
Regards Mirko
Edited by: 1009733 on 04.06.2013 09:22

Unique instance names in distributed environment

The 11.1.2.1 installation guide (http://download.oracle.com/docs/cd/E17236_01/epm.1112/epm_install_11121.pdf) says, on page 122 of the .pdf:
+"When you configure in a distributed environment, provide a new, unique instance name as you configure each server. For example, if you are using the default instance name epmsystem1 on the first server, and you keep the same naming convention on subsequent servers, you would create new, unique instance names on each subsequent server, such as epmsystem2, epmsystem3, and so on."+
No reason not to follow this advice, but wondering if it's really necessary. I feel sure I've seen installations where 'epmsystem1' was used on e.g. both a web application server and the Essbase server. Perhaps I'm remembering incorrectly.

Yes each server requires a unique name as it is registers the server with the shared services registry against the instance name, maybe it was on a 11.1.2.0 deployment that you saw the same instance name across the distributed environment.
Cheers
John
http://john-goodwin.blogspot.com/

Database issues after starting data guard

Hi. We run OEM12c in Linux. All is working well and we monitor several targets and DBs.
In our QA db server, sun solaris 11 running oracle 10g, we started to test data guard configuration for several instances we are running there. our standy server is called STDBY. All works fine, but now we have a problem managing some aspects of data guard with OEM12c.
First problem is that the instances appear as SID_IPaddress of server, as opposed as DB_UNIQUENAME.DB_DOMAIN. curiously enough, the std by copy, appears correctly (SID_sbyp.db_domain)... This is very puzzling...
Second problem is when we try to access the Data Guard performance pane, it fails showing (both in primary and secondary DBs)
Data Guard Internal Error : See the OMS log for details.
No clue where to look for this problem.
All other functions, TOP, performance home, etc... look fine.

Hi ,
Regarding "Data Guard Internal Error : See the OMS log for details"
Follow the below steps
On the Data Guard Page run the 'Verify Configuration'-Option twice. The first Execution will show an Output like
Initializing
Connected to instance test.oracle.com:mydb
Starting alert log monitor...
Updating Data Guard link on database homepage...
WARNING: Broker name (mytest) and target name (mydb) do not match.
WARNING: The broker name will be renamed to match the target name.
Skipping verification of fast-start failover static services check.
Data Protection Settings:
Protection mode : Maximum Performance
Redo Transport Mode settings:
pnjpcep1: ASYNC
cnjpcep1: ASYNC
Checking standby redo log files.....not checked due to broker name mismatch. Run verify again.
Checking Data Guard status
mydb : Normal
my11g : Normal
Tthe second Execution does not show this Warning any more, ie. it got fixed during the first Execution. Now it's possible to access the Data Guard Performance Page without Errors and you can see the Statistics.
Ref
Cloud Control: "Data Guard Internal Error" raised on Data Guard Performance Page (Doc ID 1484028.1)
Regards,
Rahul

Important Data Guard informations

I'm reading some white papers on data guard and also the Oracle documentations, but I still don't have found what I'm searching...
I've two environments... a 3 nodes RAC (10gr2, 10.2.0.4.0) and a 2 nodes RAC (11g, still never patched).
I would like to realize a data guard configuration formed by 3 nodes as primary site and the 2 nodes as standby site.
This is what I've planned:
- upgrade 3 nodes from 10g to 11g
- apply latest oracle patches for 11g on 3 nodes and 2 nodes
- move current schema (there's only one schema) from 2 nodes to 3 nodes (there are only two schemas)
- prepare the 2 nodes to be used as standby database
- mode to data guard configuration
My questions are:
1) Is it possible to use 3 nodes as primary database and 2 nodes as standby database ? I mean... Is it possible to have two sites that are not identical ?
I just can image that 2 nodes as standby database don't provide for the same service performance profile in case of a failover, but for current traffic 2 nodes are really enough.
2) In case of a disaster on primary site, the failover starts automatically or I need to manually start the standby database ? If there's a way to automatically start the standby database, I'm expecting this is completely transparent to applications connected to the database, at least to the new connections... is it right ?
3) If there's a need to apply a patch at clusterware level, use of a data guard configuration allows me to have an "always available" database ?
I mean... some patches (especially those for clusterware level) are not available for "rolling upgrade" and I need to shutdown my instance: on a data guard configuration (formed by RAC sites) is this still true ?
Thanks.

I don't know all the answers but here is some to get the thread started:
My questions are:
1) Yes, it is possible to have different number of nodes for your primary and standby sites...meaning a 3 node primary can have a dataguard configuration to a 2 node.
2) Yes, you can configure something labeled fast-start failover and I beleive it is incorporated in with dataguard broker. I'm not sure about this being transparent to the user, if they use apps. that rely on clusterware service availabillty will see a temporary suspension of service during the role change.
3) This I'm unsure of but want to say that it should be possible to do a role switch and bring a site down to patch and then resume operation, resolve the gap and do another role switch. I say I think it should be possible because it is possible to have dataguard from a rac database to a standalone so in that instance you are running differently.

Data guard setup using 11g R2.

Hi,
It is possible to setup data guard between Amazon ec2 (primary db) and standby will be on local data center- (Non Amazon) using 11g R2.

Hi,
When I tried to create data guard between amazon ec2 instance and local server using 11g R2 64 bit on linux server I am getting the below mention error.I Need some pointers on this issue.
Thanks in advance
Starting backup at 08-JUN-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile file number=00005 name=/oracle/app/oradata/abs/abs.dbf
ORACLE error from target database:
ORA-03114: not connected to ORACLE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-03114: not connected to ORACLE
RMAN-03002: failure of Duplicate Db command at 06/08/2012 19:01:22
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 06/08/2012 19:01:22
RMAN-10038: database session for channel ORA_DISK_1 terminated unexpectedly

Data Guard Broker configuration in oracle10g r2

Hi,
I am facing difficulties while configuring data guard broker. Our setup is RAC primary and single standby database. Show configuration is raising the following error...
ORA-16607: one or more databases have failed
on dcSTANDBY.log file it shows below messages....
NSV0: Failed to connect to remote database ajmprod. Error is ORA-12545
NSV0: Failed to send message to site ajmprod. Error code is ORA-12545.
I have checked listener.ora and tnsnames.ora are fine. It's fine with tnsping and sqlplus conection. I am confused where is the problem.
Aprreciate your suggestions.

Here is how I would look into this issue.
1. check the password file is setup for both and the password is common between them and matches the password of the sys user in the database.
2. check that listener(s) are up and running and status checks out.
3. check that you hosts file or DNS sees this hosts, you can check this with a ping command do from each host to the other
4. check that tnsnames.ora has the proper connect setup for both instances in you data guard configuration.
5. check tnsping to both instances from both hosts.
6. check all TNS connectivity to both instances using the SYS as sysdba, Use the TNS sqlplus sys@db as sysdba. Do this connection from both hosts if using more then one host.
If you have verified all this and it is still not working let me know and we can move on to next steps.

Data Guard Vs Golden Gate

Hi Experts,
I am looking for High Availability and Disaster Recovery architecture for my data layer i.e. Oracle Database 11g R2
We have two physical locations and the distance between two sites is around 20 miles.
Site 1:
We already implemented RAC setup with two node in site 1.
Site 2:
We are going to implement standalone database. (Not RAC)
My requirements:
1. Both databases at Site 1 & Site 2 should be replica of each other.
2. Both databases should be in sync always.
3. Site 1 is active and Site 2 is stand by.
4. Client applications on Site 1 & Site 2 should always talk to RAC database on Site1.
5.. If RAC at site 1 goes down completely, then ONLY client apps should connect to Site2 database without human intervention.
How can acheive my requirement ? I was doing some research & found two solutions. 1. Active Data Guard 2. Golden Gate.
Questions:
1. Do Data Guard and Golden Gate offers same features ?
2. Which products offers solutions to all my requirements or Do I need to use both ?
3. If Data Guard and Golden Gate are different from each other then What is the difference between them and what are the overlapping features among them ?
Thanks

1. Do Data Guard and Golden Gate offers same features ?No, there's simple compare here :
http://www.oracle.com/technetwork/database/features/availability/dataguardgoldengate-096557.html
2. Which products offers solutions to all my requirements or Do I need to use both ?Data Guard will work and you don't need anything else. I cannot speak to Golden Gate.
3. If Data Guard and Golden Gate are different from each other then
What is the difference between them and what are the overlapping features among them ?Again this document :
http://www.oracle.com/technetwork/database/features/availability/dataguardgoldengate-096557.html
1. Both databases at Site 1 & Site 2 should be replica of each other.
Data Guard can do this.
2. Both databases should be in sync always.
Data Guard can do this.
3. Site 1 is active and Site 2 is stand by.
Data Guard can do this.
4. Client applications on Site 1 & Site 2 should always talk to RAC database on Site1.
You can set your tnsnames to handle this and more. Using DBMS_SERVICE you can create an alias
to handle this.
Ex.
ernie =
(DESCRIPTION =
    (ADDRESS_LIST =
       (ADDRESS = (PROTOCOL = TCP)(HOST = primary.host)(PORT = 1521))
       (ADDRESS = (PROTOCOL = TCP)(HOST = standby.host)(PORT = 1521))
       (CONNECT_DATA =
       (SERVICE_NAME = ernie)
)5. If RAC at site 1 goes down completely, then ONLY client apps should connect to Site2 database without human intervention.
You can set your tnsnames to handle this and more.
Best Regards
mseberg

Setting up the standby side after a crash (Data Guard)

Hi,
I hope this is the right area to publish my problem...
I can't find something like codetags for the system output - so I'm sorry for the bad looking
I have a problem. I use Oracle 11.2.0.3.0 with a dataguard environment. My primary database crashed and I activate the standby to be the new primary.
After the old primary gets repaired I want to define them as the ney standby. This didn't work because we have disabled flashback logging.
We created the new standby:
rman target sys/password@prim auxiliary sys/password@stby
duplicate target database for standby from active database;
After this we do this on the new standby:
alter database recover managed standby database disconnect from session;
It looks the now there is a working physical standby.
Now I look on the primary dataguard:
DGMGRL> show database verbose stby;
Database - stby
Role:            PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag:   (unknown)
Apply Lag:       (unknown)
Real Time Query: OFF
Instance(s):
    dbuc4
Properties:
    DGConnectIdentifier             = 'stby'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '900'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName                         = 'dbuc4'
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=stby)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=stby_DGMGRL.blubb.de)(INSTANCE_NAME=stby)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.arc'
    TopWaitEvents                   = '(monitor)'
Database Status:
ORA-16795: the standby database needs to be re-created
DGMGRL> show database verbose prim;
Database - prim
Role:            PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
    dbuc4
    dbuc4stby
Properties:
    DGConnectIdentifier             = 'prim'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'OPTIONAL'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName(*)
    StaticConnectIdentifier(*)
    StandbyArchiveLocation(*)
    AlternateLocation(*)
    LogArchiveTrace(*)
    LogArchiveFormat(*)
    TopWaitEvents(*)
    (*) - Please check specific instance for the property value
Database Status:
SUCCESS
DGMGRL> show database verbose dbuc4stby;
Database - dbuc4stby
Role:            PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
    dbuc4
    dbuc4stby
Properties:
    DGConnectIdentifier             = 'dbuc4stby'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'OPTIONAL'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = ''
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName(*)
    StaticConnectIdentifier(*)
    StandbyArchiveLocation(*)
    AlternateLocation(*)
    LogArchiveTrace(*)
    LogArchiveFormat(*)
    TopWaitEvents(*)
    (*) - Please check specific instance for the property value
Database Status:
SUCCESS
DGMGRL> show configuration
Configuration - dg
Protection Mode: MaxPerformance
Databases:
    prim - Primary database
    stby     - Physical standby database (disabled)
      ORA-16795: the standby database needs to be re-created
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
On the stby side it looks like:
DGMGRL> show configuration
ORA-16795: Die Standby-Datenbank muss neu erstellt werden (The standby database needs to be recreated)
Did I have to create a new dataguard configuration?
I didn't know how I get this to work.
Thx fuechsin

Hi,
first of all: big thanks for your answer!
I think, this was a bad idea, too. But there was not enough space, so we decided to turn it off without thinking of consequences. :/
When the new hardware arrive I will enable flashback and never turn it off
The dataguard-log on the stby says:
01/23/2014 11:56:13
>> Starting Data Guard Broker bootstrap <<
Broker Configuration File Locations:
      dg_broker_config_file1 = "/Daten/stby/stby_dgbroker1.dat"
      dg_broker_config_file2 = "/Daten/stby/stby_dgbroker2.dat"
01/23/2014 11:56:17
Database needs to be reinstated or re-created, Data Guard broker ready
I want to try to delete the configuration on the prim and stby side and reconfigure it. But I don't know if there are side-effects on the working prim side - it is a productive system.
Best regards,
fuechsin

Data Guard - Keeping same SID/Instance Name across both sites

Similar Messages

Maybe you are looking for