Standby setup in 11g R2 RAC to single node

Hi,
How can we setup 11gR2 Standby Setup : Primary Database 2 Node RAC to Standalone Standby Database

ashish wrote:
Hi,
Our requirement is to create single node standby of a 11g R2 RAC 2 node database.To implement there is not much changes in functionality of dataguard, Except some new features like
1) Active dataguard
-- Where you can run MRP even in open status, so that it can be only readable.
2) password file on standby should not be created, it should copy from primary and rename it.
3) from 11g you can perform duplicate from active database without backup.
& so on.
To build a stand alone standby from 2-node RAC, MAA pdf is better one
http://www.oracle.com/technetwork/database/features/availability/maa-wp-10g-racprimaryracphysicalsta-131940.pdf
http://www.oracle.com/technetwork/database/features/availability/twp-dataguard-11gr2-1-131981.pdf
*How to create physical standby database with 11g RMAN DUPLICATE FROM ACTIVE DATABASE [ID 747250.1]*

Similar Messages

Creating DR standby from RAC to single NODE

OS and Database versions Primary:
node1:- OEL 5.7
node2:- OEL 5.7
inst1:- prod1 Oracle 11.2.0.3
inst2:- prod2 Oracle 11.2.0.3
Standby:
OEL 5.7
Oracle 11.2.0.3
NOTE:- Creating Standby on Single node.
My scenario:
============
node1:- linuxdb1
node2:- linuxdb2
inst1:- prod1
inst2:- prod2
Point1:- We have 2 node RAC with ASM disk and database is okay. Now i want to make DR on single node with ASM disk created already.
Point2:- grid and oracle users are on RAC prod database & also same grid and oracle users on SINGLE node DR
Point3:- Took RMAN backup from prod database ( 2 node RAC ) and copied to DR as shown below:
RMAN>backup device type disk format '/u02/stby/%U' database plus archivelog;
RMAN>backup device type disk format '/u02/stby/%U' current controlfile for standby;
scp -rp /u02/stby/* [email protected]:/u02/stby/
Point4:- Now when i run below command on DR ( oracle@linuxdr2 )
[oracle@linuxdr2 stby]$ rman target sys/pwd@prod1 auxiliary /
Recovery Manager: Release 11.2.0.3.0 - Production on Sun Mar 10 13:18:20 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: PROD (DBID=220323208)
connected to auxiliary database: PROD (not mounted)
RMAN> duplicate target database for standby;
Starting Duplicate Db at 10-MAR-13
using target database control file instead of recovery catalog
configuration for DISK channel 2 is ignored
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=1142 device type=DISK
contents of Memory Script:
restore clone standby controlfile;
executing Memory Script
Starting restore at 10-MAR-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /u02/stby/33o464m6_1_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/10/2013 13:19:22
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred
Can you please help me to resolve the issue.
Thanks,
Vikhar

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/10/2013 13:19:22
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred Any errors in alert log file?
Have you tried once again ?
Why cant you go for RMAN duplicate from active database, If you have any concerns then enable trace of RMAN and share the information
rman target / log=/u01/test/rman_log.txt trace=/u01/test/rmantrace.log

2 Node RAC with Single Node Standby Help

Hello Everyone -
I'm preparing to set up a 2 node RAC and use a single-node standby database.
I'm a bit confused on how to set up the Standby Redo Logs on the standby to use the LGWR functionality from the RAC instances.
Should I just create a set of standby redo logs (alter database add standby logfile...) like on a single-instance environment or do I need to create standby logfile threads (alter database add standby logfile thread. . . ) one for each cooresponding thread on the RAC?
It just seems odd that 2 RAC redo threads are able to write to one standby redo logfile at the same time (or maybe each RAC redo thread picks the first available standby redo log and writes to it??)
If anyone has some advice or insight, I'd appreciate it.
Andy

Hello Andy,
Did you get answer to your question about RAC with single standby?
Could you please share with me your experience if you have done so.
Thanks
Amit

RAC to Single node cloing

Hi all,
We have our production running on 2 node RAC and its in ASM cluster and AppsTier on single node
Node 1 - AppsTier
Node 2 - RAC 1
Node 3 - RAC 2
Now I would like to do a cloning for the production from RAC to Single Instance
Is there any doc or steps to be followed for the RAC to single instance cloning ??..
Regards,
Mahesh

Hi Makesh;
This topic discussed here many times, Just check below links which u can find all notes and also see general search link
CLONE-RAc to nonrac
RAC -> NON RAC ebiz clone
Re: Clone Oracle Apps 11.5.10.2 RacDB to Non-RAC DB
General search:
http://forums.oracle.com/forums/search.jspa?threadID=&q=rac+to+nonrac+clone&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Regard
Helios

2 Node RAC to single node clonning

Hello,
We have 2 Node RAC database for R12 EBS on production now we want to refresh developement enviorenment which is single node so now can anybody tell me process to follow this or any documentaion for same.
Regards
Saransh Soni

Hi Saransh,
Please refer to similar threads in past :
convert RAC to single instance ebs R12
Re: Clone Oracle Apps 11.5.10.2 RacDB to Non-RAC DB
Regards
Rajesh

Resizing redo log files on a 3 node RAC with single node standby database

Hi
On a 3 node 11g RAC system,I have to resize the redo logs on primary database from 50M to 100M. I was planning to do the following steps:
SQL> select group#,thread#,members,status from v$log;
GROUP# THREAD# MEMBERS STATUS
1 1 3 INACTIVE <-- whenefver INACTIVE, logfile group can be dropped
2 1 3 CURRENT & resized, switch logfile can change logfile group
3 1 3 INACTIVE
4 2 3 INACTIVE
5 2 3 INACTIVE
6 2 3 CURRENT
7 3 3 INACTIVE
8 3 3 INACTIVE
9 3 3 CURRENT
9 rows selected.
SQL> alter database drop logfile group 1;
Database altered.
SQL> ALTER DATABASE ADD LOGFILE THREAD 1
GROUP 1 (
'/PROD/redo1/redo01a.log',
'/PROD/redo2/redo01b.log',
'/PROD/redo3/redo01c.log'
) SIZE 100M reuse; 2 3 4 5 6
Database altered.
However I am not sure what needs to be done for the standby. The standby_file_management is set to auto and it is single instance standby.
SQL> select group#,member from v$logfile where type='STANDBY';
GROUP#
MEMBER
10
/PROD/flashback/PROD/onlinelog/o1_mf_10_7b44gy67_.log
11
/PROD/flashback/PROD/onlinelog/o1_mf_11_7b44h7gy_.log
12
/PROD/flashback/PROD/onlinelog/o1_mf_12_7b44hjcr_.log
Please let me know.
Thanks
Sumathy

Hello;
For Redo and Standby redo this won't help :
standby_file_management is set to auto
On the Standby cancel recovery, then drop and recreate the redo and or Standby redo.
Then start recovery again.
Example ( I have a habit of removing the old file at the OS to avoid REUSE and conflicts )
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='MANUAL';
alter database add standby logfile group 4
('/u01/app/oracle/oradata/orcl/standby_redo04.log') size 100m;
ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT='AUTO'
Notes worth reviewing :
Online Redo Logs on Physical Standby [ID 740675.1]
Error At Standby Database Ora-16086: Standby Database Does Not Contain Available Standby Log Files [ID 1155773.1]
Example of How To Resize the Online Redo Logfiles [ID 1035935.6]
Best Regards
mseberg

Best way to move from RAC to single node database.

Hi,
One of my customer is having RAC setup with EBS R12. Due to some other issues, customer is looking to switch back to Standalone database. What could be the best approach for this?
I am thinking to perform the following approach. Could any body comment on the same?
1) create a new oracle_home on the same server.
2) Modify the cluster_database to false.
3) start the database from new oracle_home.
4) Create a new listener with same port#(off course i will stop all RAC services including listener).
Version details are :- 11gR2 on Solaris.
EBS is :- R12.
Is this approach sounds good or any better method.
Thanks in-advance.
Regards
DBA.

Hello DBA,
You can follow these steps...
a) Stop database using srvctl
srvctl stop database -d mydb
b) Remove the database entry from crs
$ srvctl remove instance -d mydb -i mydb1
$ srvctl remove instance -d mydb -i mydb2
$ srvctl remove database -d mydb
c) Start the database on first instance
SQL> startup
SQL> alter system set cluster_database=false scope=spfile;
System altered.
SQL> alter system set cluster_database_instances=1 scope=spfile;
System altered.
SQL> alter database disable thread 2;
Database altered.
d) Delete the unwanted thread and redo logfiles
e) Drop the unwanted undo tablespace
f) Create pfile from spfile
g) Remove second instance references from the pfile and start the instance
h) create spfile from pfile.
Regards,
Alex Alvarenga
SP - Brasil

Oracle 11g R2 RAC installation on AIX

hi,
I wana setup Oracle 11g R2 RAC on Ibm with AIX. Is there any good document or cookbook explaining step by step procedure for the installation...I'll be thankful
thanx

Hi;
Please check below links which is mention about 11gR2 Rac installation on AIX
11gR2 RAC installation in AIX help urgent
Re: 11gR2 RAC installation in AIX help urgent...!!!!
11gR2 RAC Installation Manual (with ASM+Rawdevice)
http://www.goodus.com/knowledge_pds/%EA%B8%B0%EC%88%A0%EB%85%B8%ED%8A%B8_11gR2_RAC_Guide.pdf
Regard
Helios

Moving from Oracle RAC to single instance

Hi,
We are running EBS R12 on windows 2008 R2. Its a 2 node setup, we want to move it to single instance.
I heard that moving from RAC to single instance is not supported by oracle is it true?
Can someone kindly guide me documentation for the same.

user10243788 wrote:
Hi,
We are running EBS R12 on windows 2008 R2. Its a 2 node setup, we want to move it to single instance.
I heard that moving from RAC to single instance is not supported by oracle is it true?
Can someone kindly guide me documentation for the same.Its totally possible technically to move from RAC to single node and its even documented. I dont know where you have heard that its not supported.
See the process of removing node from rac
http://docs.oracle.com/cd/B28359_01/rac.111/b28254/adddelunix.htm
http://docs.oracle.com/cd/B19306_01/rac.102/b14197/adddelunix.htm
http://www.idevelopment.info/data/Oracle/DBA_tips/Oracle10gRAC/CLUSTER_23.shtml
For performance related
Moving RAC to single instance

Db context file creation for rac to single instance cloning

DOC ID: 559518.1 Section 6: RAC to Single Instance Cloning mentions that the context file creation should be done as in the case of Single Instance cloning
what would be the command syntax?

Thanks Hussein. However, section 6 of doc 559518.1 mentions that part 5.1.3 when cloning from rac to single node should be done as in the case of Single Instance cloning.
the syntax for rac to rac cloning (which is in 5.1.3) is
perl adclonectx.pl \
contextfile=[PATH to OLD Source RAC contextfile.xml] \
template=[NEW ORACLE_HOME]/appsutil/template/adxdbctx.tmp \
pairsfile=[NEW ORACLE_HOME]/appsutil/clone/pairsfile.txt \
initialnode
so what is the syntax for rac to single instance? I reckon I will still use adclonectx.pl, but now what would be the complete sysntax for single instance cloning?

Upgradation of Primary (RAC) two node database and single node standby DB

We have our primary setup in Oracle RAC in 10g R2 (10.2.0.1.0) in HP UX 11i 64bit (PA RISC). It is a two node RAC.
And we have a single node standby database (DR).
Both the primary and standby database are existing in 10.2.0.1.0
We need to upgrade the primary and standby database from 10.2.0.1.0 to 10.2.0.4.0
Am planning to go through the DBUA method for upgrading the database.
I like to know is there any special cases for upgrading both the primary and standby database.
since as i mentioned i will upgrade the database through dbua method, and if i upgrade my standby database as same as primary,
will it forcefully open the database, because while we upgrade the database through dbua it will open the database at the end of installation.
Is it possible to upgrade the standby database with DBUA method even when my standby database is in Mount state.
I will be helpfull if anyone has done this earlier, are there any know issues and is there any good document which i can refer.
with regards
A.Aravind

hi,
thanks for your reply, and i was following the document.
I like to know that is it mandatory to create a new Oracle Home for upgrading from 10.2.0.1.0 to 10.2.0.4.0
or i can proceed the installation of software in the same oracle home.
I will list out my action plan, please correct me if am wrong,
In Primary RAC,
a) Shutdown the database
b) Shutdown the asm instance
c) Stop the nodeapps services
d) Stop the cluster ready services.
e) Stop the enterprise manager
f) Stop the isqlplus
In Standby single node database,
1)Cancel the managed Recovery process
2) shutdown the database
3) Shutdown the asm instance.
PATCHING Process
g) Apply the oracle clusterware patch 10.2.0.4.0 in the same old existing ORA_CRS_HOME
h) Apply the oracle database software patch 10.2.0.4.0 in the same old existing ORACLE_HOME
Note: In my case both the ORACLE_HOME and ASM_HOME are in the same location.
i) Execute dbua to update the database in the primary database.
j) Apply the 10.2.0.4.0 patch in standby database ORACLE_HOME where as ORACLE_HOME and ASM_HOME are in the same location
k) Copy the recently generated archive logs from primary to standby manually and apply in standby database.
l) Mount the database in standby
m) Start the Managed recovery process.
with regards
A.Aravind

Snapshot standby database in oracle 11g r2 RAC

Folks,
i am just wondering if the process is same for standalone and RAC snapshot standby database.
We have a DR test
1 / I just converted the standalone DR on 11g to snapshot standby database for users to do some testing and reverted back to physical standby after test was done. i folllowed metalink note ID 443720.1
2/ now there is anotherDR test where we have 2 node prod and 2 node DR on oracle 11g rel2 RAC, so not sure we can follow the same process that i used for 11g standalone database. If somebody have done this on RAC, would you please provide the steps ?
Thanks in advance
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL> !uname -a
Linux 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

I haven't done a Snapshot Standby (RAC or non-RAC). But I see no reason why it shouldn't work with a RAC Standby either.
The command is a Database level command, not an Instance level command.
Hemant K Chitale

Streams Setup from RAC to Single instance

Does anyone have a document to setup streams from RAC to Non RAC. I successfully setup streams on 2 single instances but I am having issues in replicating, Streams is setup on node1 or Rac and Apply process is also setup on single node. but data is not replicating.
Appreciate any suggestions.

From Metalink Note 418755.1:
Additional Configuration for RAC Environments for a Source Database Archive Logs
The archive log threads from all instances must be available to any instance
running a capture process. This is true for both local and downstream capture.
Queue Ownership
When Streams is configured in a RAC environment, each queue table has an
"owning" instance. All queues within an individual queue table are owned by
the same instance. The Streams components (capture/propagation/apply) all
use that same owning instance to perform their work. This means that
+ a capture process is run at the owning instance of the source queue.
+ a propagation job must run at the owning instance of the queue
+ a propagation job must connect to the owning instance of the target queue.
Ownership of the queue can be configured to remain on a specific instance,
as long as that instance is available, by setting the PRIMARY _INSTANCE
and/or SECONDARY_INSTANCE parameters of DBMS_AQADM.ALTER_QUEUE_TABLE.
If the primary_instance is set to a specific instance (ie, not 0), the queue
ownership will return to the specified instance whenever the instance is up.
Capture will automatically follow the ownership of the queue.If the ownership
changes while capture is running, capture will stop on the current instance
and restart at the new owner instance.
For queues created with Oracle Database 10g Release 2, a service will be
created with the service name= schema.queue and the network name
SYS$schema.queue.global_name for that queue. If the global_name of the
database does not match the db_name.db_domain name of the database, be sure
to include the global_name as a service name in the init.ora.
For propagations created with the Oracle Database 10g Release 2 code with
the queue_to_queue parameter to TRUE, the propagation job will deliver only
to the specific queue identified. Also, the source dblink for the target
database connect descriptor must specify the correct service (global name of
the target database ) to connect to the target database. For example, the
tnsnames.ora entry for the target database should include the CONNECT_DATA
clause in the connect descriptor for the target database. This claus should
specify (CONNECT_DATA=(SERVICE_NAME='global_name of target database')).
Do NOT include a specific INSTANCE in the CONNECT_DATA clause.
For example, consider the tnsnames.ora file for a database with the global name
db.mycompany.com. Assume that the alias name for the first instance is db1 and
that the alias for the second instance is db2. The tnsnames.ora file for this
database might include the following entries:
db.mycompany.com=
(description=
(load_balance=on)
(address=(protocol=tcp)(host=node1-vip)(port=1521))
(address=(protocol=tcp)(host=node2-vip)(port=1521))
(connect_data=
(service_name=db.mycompany.com)))
db1.mycompany.com=
(description=
(address=(protocol=tcp)(host=node1-vip)(port=1521))
(connect_data=
(service_name=db.mycompany.com)
(instance_name=db1)))
db2.mycompany.com=
(description=
(address=(protocol=tcp)(host=node2-vip)(port=1521))
(connect_data=
(service_name=db.mycompany.com)
(instance_name=db2)))
Use the italicized tnsnames.ora alias in the target database link USING clause.
DBA_SERVICES lists all services for the database. GV$ACTIVE_SERVICES identifies
all active services for the database In non_RAC configurations, the service
name will typically be the global_name. However, it is possible for users to
manually create alternative services and use them in the TNS connect_data
specification . For RAC configurations, the service will appear in these views
as SYS$schema.queue.global_name.
Propagation Restart
Use the procedures START_PROPAGATION and STOP_PROPAGATION from
DBMS_PROPAGATION_ADM to enable and disable the propagation schedule.
These procedures automatically handle queue_to_queue propagation.
Example:
exec DBMS_PROPAGATION_ADM.stop_propagation('name_of_propagation'); or
exec DBMS_PROPAGATION_ADM.stop_propagation('name_of_propagation',force=>true);
exec DBMS_PROPAGATION_ADM.start_propagation('name_of_propagation');
If you use the lower level DBMS_AQADM procedures to manage the propagation schedule,
be sure to explicitly specify the destination_queue name when queue_to_queue propagation has been configured.
Example:
DBMS_AQADM.UNSCHEDULE_PROPAGATION('source_queue_name','destination',destination_queue=>'specific_queue');
DBMS_AQADM.SCHEDULE_PROPAGATION('source_queue_name','destination',destination_queue=>'specific_queue');, DBMS_AQADM.ENABLE_PROPAGATION_SCHEDULE('source_queue_name','destination',destination_queue=>'specific_queue');,
DBMS_AQADM.DISABLE_PROPAGATION_SCHEDULE('source_queue_name','destination',destination_queue=>'specific_queue');, DBMS_AQADM.ALTER_PROPAGATION_SCHEDULE('source_queue_name','destination',destination_queue=>'specific_queue');
Changing the GLOBAL_NAME of the Source Database
See the OPERATION section on Global_name below. The following are some
additional considerations when running in a RAC environment.
If the GLOBAL_NAME of the database is changed, ensure that any propagations
are dropped and recreated with the queue_to_queue parameter set to TRUE.
In addition, if the GLOBAL_NAME does not match the db_name.db_domain of the
database, include the global_name for the queue (NETWORK_NAME in DBA_QUEUES)
in the list of services for the database in the database parameter
initialization file.
Section 4. Target Site Configuration
The following recommendations apply to target databases, ie, databases in which
Streams apply is configured.
1. Privileges
Grant Explicit Privileges to APPLY_USER for the user tables
Examples:
Privileges for table level DML: INSERT/UPDATE/DELETE,
Privileges for table level DDL: CREATE (ANY) TABLE , CREATE (ANY) INDEX,
CREATE (ANY) PROCEDURE
2. Instantiation
Set Instantiation SCNs manually if not using export/import. If manually
configuring the instantiation scn for each table within the schema, use the
RECURSIVE=>TRUE option on the DBMS_STREAMS_ADM.SET_SCHEMA_INSTANTIATION_SCN
procedure
For DDL Set Instantiation SCN at next higher level(ie,SCHEMA or GLOBAL level).
3. Conflict Resolution
If updates will be performed in multiple databases for the same shared
object, be sure to configure conflict resolution. See the Streams
Replication Administrator's Guide Chapter 3 Streams Conflict Resolution,
for more detail.
To simplify conflict resolution on tables with LOB columns, create an error
handler to handle errors for the table. When registering the handler using
the DBMS_APPLY_ADM.SET_DML_HANDLER procedure, be sure to specify the
ASSEMBLE_LOBS parameter as TRUE.
In Streams Concepts manual 10.2 chapter 22: Monitoring Apply
Displaying detailed information about Apply errors.
4. Apply Process Configuration
A. Rules
If the maintain_* procedures are not suitable for your environment,
please use the ADD_RULES procedures (ADDTABLE_RULES , ADD_SCHEMA_RULES ,
ADD_GLOBAL_RULES (for DML and DDL), ADD_SUBSET_RULES (DML only).
These procedures minimize the number of steps required to configure Streams
processes. Also, it is possible to create rules for non-existent objects,
so be sure to check the spelling of each object specified in a rule carefully.
APPLY can be configured with or without a ruleset. The ADD_GLOBAL_RULES can
be used to apply all changes in the queue for the database. If no ruleset is
specified for the apply process, all changes in the queue are processed by the apply process.
A single Streams apply can process rules for multiple tables or schemas
located in a single queue that are received from a single source database .
For best performance, rules should be simple. Rules that include LIKE clauses are
not simple and will impact the performance of Streams.
To eliminate changes for particular tables or objects, specify the
include_tagged_lcr clause along with the table or object name in the
negative rule set for the Streams process. Setting this clause will
eliminate all changes, tagged or not, for the table or object.
B. Parameters
Set the following parameters after a apply process is created:
+ DISABLE_ON_ERROR=N Default: Y
If Y, then the apply process is disabled on the first unresolved error,
even if the error is not fatal.
If N, then the apply process continues regardless of unresolved errors.
+ PARALLELISM=3* Number of CPU Default: 1
Apply parameters can be set using the SET_PARAMETER procedure from the
DBMS_APPLY_ADM package. For example, to set the DISABLE_ON_ERROR parameter
of the streams apply process named APPLY_EX, use the following syntax while
logged in as the Streams Administrator:
exec dbms_apply_adm.set_parameter('apply_ex','disable_on_error','n');
Change the apply parallelism parameter recommendation to a lower number.
In general, try 4 or 8 and increase or decrease as necessary for your workload.
In some cases, performance can be improved by setting the following hidden
parameter. This parameter should be set when the major workload is UPDATEs
and the updates are performed on just a few columns of a many-column table.
+ DYNAMICSTMTS=Y Default: N
If Y, then for UPDATE statements, the apply process will optimize the
generation of SQL statements based on required columns.
CHECKPOINTFREQUENCY=1000
Increase the frequency of logminer checkpoints especially in a
database with significant LOB or DDL activity.
exec dbms_capture_adm.set_parameter('capture_ex','_checkpoint_frequency','1000');
5. Additional Configuration for RAC Environments for a Apply Database
Queue Ownership
When Streams is configured in a RAC environment, each queue table has an
"owning" instance. All queues within an individual queue table are owned
by the same instance. The Streams components (capture/propagation/apply)
all use that same owning instance to perform their work. This means that
the database link specified in the propagation must connect to the owning
instance of the target queue. the apply process is run at the owning instance
of the target queue
Ownership of the queue can be configured to remain on a specific instance,
as long as that instance is available, by setting the PRIMARY _INSTANCE and
SECONDARY_INSTANCE parameters of DBMS_AQADM.ALTER_QUEUE_TABLE. If the
primary_instance is set to a specific instance (ie, not 0), the queue
ownership will return to the specified instance whenever the instance is up.
Apply will automatically follow the ownership of the queue. If the ownership
changes while apply is running, apply will stop on the current instance and
restart at the new owner instance.
Changing the GLOBAL_NAME of the Database
See the OPERATION section on Global_name below. The following are some
additional considerations when running in a RAC environment.
If the GLOBAL_NAME of the database is changed, ensure that the queue is
empty before changing the name and that the apply process is dropped and
recreated with the apply_captured parameter = TRUE. In addition, if the
GLOBAL_NAME does not match the db_name.db_domain of the database, include
the GLOBAL_NAME in the list of services for the database in the database
parameter initialization file.

Can I use data guard to create a RAC standby database for a non RAC primary

Hi,
we need to RAC our production database but the normal methods will mean a long outage. It is possible to create a standby as a single node RAC database and when ready do a graceful failover to the standby database and open it for business. The next step would be to create another RAC node from this on the original server.
servers are already cluster aware, using ASM etc
Oracle 10.2

Yes, you will be able to setup RAC stnadby for a non-RAC Primary. For primary it just needs a available destination for redo shipping it doesn't matter whether it's RAC enabled or not. And ofcourse you are using 10.2 anyway only one node will be running MRP and that is too in standby mount mode.
However since you have are using You may follow below sequence.
1. Setup a new standby as RAC enabled.
2. Perform a switchover.
3. Shutdown the Old primary (which is standby now).
4. Install CRS and RDBMS on the old primary and it's new node.
5. Modify the cluster_database=TRUE and cluster_database_instances=<required number of instances>.
With above modification mount the standby database in standby mode and start MRP.
6. Introduce the database and instances to the OCR using SRVCTL add command.
7. Once you your database is synchronized with Primary do a switchover.
9. Now you can repeat step 3 to 6 on the other site too. <- if you need your secondary site to be RAC enabled too
10. Finally both the sites should be RAC enabled.
Hope this is helpful!!!
Thanks,
Asif Haliyal

Convert 11.1.0.7 EBS 12.1.3 single node to RAC with ASM on 11.2.0.3 cluster

Hi
I am trying to convert a single node 11.1.0.7 database with EBS 12.1.3 version from single to 2-node RAC ASM on Oracle clusterware 11.2.0.3 on AIX 6.1 - 64 bit
I am following Oracle metalink document note id 466649.1 . My 11.2.0.3 clusterware is already setup correctly and working fine as per document E24614-03.
However I am currently stuck in section 3.3:Configure TNS listener (Doc id : 466649.1) . The netca is unable to start the listener and failing with error as below.
However when I start the same locally from lsnrctl command listener starts.
trace_OraDb11g_home1-1212159AM174.log
====================================
[AWT-EventQueue-0] [18:34:31:887] [RuntimeExec.runCommand:144] runCommand: process returns 123
[AWT-EventQueue-0] [18:34:31:887] [RuntimeExec.runCommand:161] RunTimeExec: output>
[AWT-EventQueue-0] [18:34:31:887] [RuntimeExec.runCommand:164] Attempting to start `ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr
` on member `jxn-ux-ebs1d1q`
[AWT-EventQueue-0] [18:34:31:887] [RuntimeExec.runCommand:164] Start of `ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr` on member
`jxn-ux-ebs1d1q` failed.
[AWT-EventQueue-0] [18:34:31:888] [RuntimeExec.runCommand:164] Attempting to stop `ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr`
on member `jxn-ux-ebs1d1q`
[AWT-EventQueue-0] [18:34:31:888] [RuntimeExec.runCommand:164] Stop of `ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr` on member
`jxn-ux-ebs1d1q` succeeded.
[AWT-EventQueue-0] [18:34:31:888] [RuntimeExec.runCommand:164] CRS-2632: There are no more servers to try to place resource 'ora.jxn-ux-e
bs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr' on that would satisfy its placement policy
[AWT-EventQueue-0] [18:34:31:888] [RuntimeExec.runCommand:170] RunTimeExec: error>
[AWT-EventQueue-0] [18:34:31:889] [RuntimeExec.runCommand:173] CRS-0223: Resource 'ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr'
has placement error.
[AWT-EventQueue-0] [18:34:31:889] [RuntimeExec.runCommand:173]
[AWT-EventQueue-0] [18:34:31:889] [RuntimeExec.runCommand:192] Returning from RunTimeExec.runCommand
[AWT-EventQueue-0] [18:34:31:890] [HAOperationImpl.runCommand:1221] signed exit value = 123
[AWT-EventQueue-0] [18:34:31:890] [HAOperationImpl.runCommand:1258] set status HA_RES_RELOCATE_ERR
[AWT-EventQueue-0] [18:34:31:891] [HAStartOperation.run:84] Returned from executing the HA Operation
[AWT-EventQueue-0] [18:34:31:891] [HAStartOperation.run:89] OUTPUT> Attempting to start `ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q
.lsnr` on member `jxn-ux-ebs1d1q`
[AWT-EventQueue-0] [18:34:31:891] [HAStartOperation.run:89] OUTPUT> Start of `ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr` on m
ember `jxn-ux-ebs1d1q` failed.
[AWT-EventQueue-0] [18:34:31:891] [HAStartOperation.run:89] OUTPUT> Attempting to stop `ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.
lsnr` on member `jxn-ux-ebs1d1q`
[AWT-EventQueue-0] [18:34:31:892] [HAStartOperation.run:89] OUTPUT> Stop of `ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr` on me
mber `jxn-ux-ebs1d1q` succeeded.
[AWT-EventQueue-0] [18:34:31:892] [HAStartOperation.run:89] OUTPUT> CRS-2632: There are no more servers to try to place resource 'ora.jxn
-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr' on that would satisfy its placement policy
[AWT-EventQueue-0] [18:34:31:893] [HAStartOperation.run:95] ERROR> CRS-0223: Resource 'ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.l
snr' has placement error.
[AWT-EventQueue-0] [18:34:31:893] [LocalCommand.execute:56] LocalCommand.execute: Returned from run method
[AWT-EventQueue-0] [18:34:31:893] [HAOperationResult.getOutputAll:114] outLine is [CRS-2632: There are no more servers to try to place re
source 'ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr' on that would satisfy its placement policy]
[AWT-EventQueue-0] [18:34:31:894] [HAOperationResult.getOutputAll:115] errLine is [CRS-0223: Resource 'ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_
JXN-UX-EBS1D1Q.lsnr' has placement error.]
[AWT-EventQueue-0] [18:36:39:994] [ca.ConfigureListenerOPS.getNodeNameIndex:-1] getNodeNameIndex: Matching LISTENER_EBSQA_JXN-UX-EBS1D1Q
[AWT-EventQueue-0] [18:36:39:994] [ca.ConfigureListenerOPS.getListenerRootName:-1] ListenerName is LISTENER_EBSQA
The crsctl has details as below:
=====================
NAME TARGET STATE SERVER STATE_DETAILS
Cluster Resources
ora.LISTENER_SCAN1.lsnr
1 ONLINE ONLINE jxn-ux-ebs2d1q
ora.LISTENER_SCAN2.lsnr
1 ONLINE ONLINE jxn-ux-ebs1d1q
ora.LISTENER_SCAN3.lsnr
1 ONLINE ONLINE jxn-ux-ebs1d1q
ora.cvu
1 ONLINE ONLINE jxn-ux-ebs1d1q
ora.jxn-ux-ebs1d1q.LISTENER_EBSQA_JXN-UX-EBS1D1Q.lsnr
1 ONLINE OFFLINE
ora.jxn-ux-ebs1d1q.vip
1 ONLINE ONLINE jxn-ux-ebs1d1q
ora.jxn-ux-ebs2d1q.LISTENER_EBSQA_JXN-UX-EBS2D1Q.lsnr
1 ONLINE OFFLINE
Not sure how to fix this .
Regards
Ram

I am trying to convert a single node 11.1.0.7 database with EBS 12.1.3 version from single to 2-node RAC ASM on Oracle clusterware 11.2.0.3 on AIX 6.1 - 64 bit You don't need to create listeners, after installing 11203 cluster there will be LISTENER running from $GRID_HOME
along with SCAN_LISTENERS

Standby setup in 11g R2 RAC to single node

Similar Messages

Maybe you are looking for