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

Similar Messages

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

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

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

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

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]*

Dataguard configuration from 2-node rac to single instance with out ASM

Hi Gurus,
Oracle Version : 11.2.0.1
Operating system:linux.
Here i am trying to configure data Guard from 2-node rac to a singled instance stanby database . I have done all the changes in the parameter file for both primary and stand by database and when i am trying to duplicate my target database it is giving error as shown below.
[oracle@rac1 dbs]$ rman target / auxiliary sys/qfundracdba@poorna
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jul 21 14:49:01 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: QFUNDRAC (DBID=3138886598)
connected to auxiliary database: QFUNDRAC (not mounted)
RMAN> duplicate target database for standby from active database;
Starting Duplicate Db at 21-JUL-11
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=63 device type=DISK
contents of Memory Script:
   backup as copy reuse
   targetfile '/u01/app/oracle/product/11.2.0/db_1/dbs/orapwqfundrac1' auxiliary format
'/u01/app/oracle/product/11.2.0/db_1//dbs/orapwpoorna'   ;
executing Memory Script
Starting backup at 21-JUL-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=10 instance=qfundrac1 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/21/2011 14:49:29
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/21/2011 14:49:29
ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-01017: invalid username/password; logon denied
ORA-17629: Cannot connect to the remote database serverHere i was able to connect to my auxiliary database as shown below
[oracle@rac1 dbs]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jul 21 15:00:10 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: QFUNDRAC (DBID=3138886598)
RMAN> connect auxiliary sys/qfundracdba@poorna
connected to auxiliary database: QFUNDRAC (not mounted)Can any one please help me .
Thanks & Regards
Poorna Prasad.S

Hi All,
Can any one please find out my both the parameters file and tell me if any thing is wrong.
Primary Database parameters.
qfundrac1.__db_cache_size=2818572288
qfundrac2.__db_cache_size=3372220416
qfundrac1.__java_pool_size=16777216
qfundrac2.__java_pool_size=16777216
qfundrac1.__large_pool_size=16777216
qfundrac2.__large_pool_size=16777216
qfundrac1.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
qfundrac2.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
qfundrac1.__pga_aggregate_target=4294967296
qfundrac2.__pga_aggregate_target=4294967296
qfundrac1.__sga_target=4294967296
qfundrac2.__sga_target=4294967296
qfundrac1.__shared_io_pool_size=0
qfundrac2.__shared_io_pool_size=0
qfundrac1.__shared_pool_size=1375731712
qfundrac2.__shared_pool_size=855638016
qfundrac1.__streams_pool_size=33554432
qfundrac2.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/qfundrac/adump'
*.audit_trail='db'
*.cluster_database=true
*.compatible='11.2.0.0.0'
*.control_files='+ASM_DATA2/qfundrac/controlfile/current.256.754410759'
*.db_block_size=8192
*.db_create_file_dest='+ASM_DATA1'
*.db_create_online_log_dest_1='+ASM_DATA2'
*.db_domain=''
*.DB_FILE_NAME_CONVERT='/u02/poorna/oradata/','+ASM_DATA1/','/u02/poorna/oradata','+ASM_DATA2/'
*.db_name='qfundrac'
*.db_recovery_file_dest_size=40770732032
*.DB_UNIQUE_NAME='qfundrac'
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=qfundracXDB)'
*.fal_client='QFUNDRAC'
*.FAL_SERVER='poorna'
qfundrac2.instance_number=2
qfundrac1.instance_number=1
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(qfundrac,poorna)'
*.LOG_ARCHIVE_DEST_1='LOCATION=+ASM_FRA VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=qfundrac'
*.LOG_ARCHIVE_DEST_2='SERVICE=boston ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=poorna'
*.LOG_ARCHIVE_DEST_STATE_1='ENABLE'
*.LOG_ARCHIVE_DEST_STATE_2='ENABLE'
*.LOG_ARCHIVE_FORMAT='%t_%s_%r.arc'
*.LOG_ARCHIVE_MAX_PROCESSES=30
*.LOG_FILE_NAME_CONVERT='/u02/poorna/oradata/','+ASM_DATA1/','/u02/poorna/oradata','+ASM_DATA2/'
*.open_cursors=300
*.pga_aggregate_target=4294967296
*.processes=300
*.remote_listener='racdb-scan.qfund.net:1521'
*.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'
*.sec_case_sensitive_logon=FALSE
*.sessions=335
*.sga_target=4294967296
*.STANDBY_FILE_MANAGEMENT='AUTO'
qfundrac2.thread=2
qfundrac1.thread=1
qfundrac1.undo_tablespace='UNDOTBS1'
qfundrac2.undo_tablespace='UNDOTBS2'and my standby database prameter file.
poorna.__db_cache_size=314572800
poorna.__java_pool_size=4194304
poorna.__large_pool_size=4194304
poorna.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
poorna.__pga_aggregate_target=343932928
poorna.__sga_target=507510784
poorna.__shared_io_pool_size=0
poorna.__shared_pool_size=176160768
poorna.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/poorna/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='/u01/app/oracle/oradata/poorna/control01.ctl','/u01/app/oracle/flash_recovery_area/poorna/control02.ctl'
*.db_block_size=8192
*.db_domain=''
#*.db_name='poorna'
#*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=4039114752
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=poornaXDB)'
*.local_listener='LISTENER_POORNA'
*.memory_target=849346560
*.open_cursors=300
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sec_case_sensitive_logon=FALSE
*.undo_tablespace='UNDOTBS1'
############### STAND By PARAMETERS ########
DB_NAME=qfundrac
DB_UNIQUE_NAME=poorna
LOG_ARCHIVE_CONFIG='DG_CONFIG=(poorna,qfundrac)'
#CONTROL_FILES='/arch1/boston/control1.ctl', '/arch2/boston/control2.ctl'
DB_FILE_NAME_CONVERT='+ASM_DATA1/','/u02/poorna/oradata/','+ASM_DATA2/','/u02/poorna/oradata'
LOG_FILE_NAME_CONVERT= '+ASM_DATA1/','/u02/poorna/oradata/','+ASM_DATA2/','/u02/poorna/oradata'
LOG_ARCHIVE_FORMAT=log%t_%s_%r.arc
LOG_ARCHIVE_DEST_1= 'LOCATION=/u02/ARCHIVE/poorna VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=poorna'
LOG_ARCHIVE_DEST_2= 'SERVICE=qfundrac ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=qfundrac'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
STANDBY_FILE_MANAGEMENT=AUTO
FAL_SERVER=qfundrac
FAL_CLIENT=poornaThanks & Regards,
Poorna Prasad.S

How to find thead 2 archive log when i recover from 2-node RAC to single

I backup 2-ndoe RAC and restore to single - node
Control file created.
SQL> recover database iuckup controlfile
SQL> recover database using backup controlfIle;
ORA-00279: change 12100176131169 generated at 07/06/2013 16:36:57 needed for
thread 1
ORA-00289: suggestion : /arch/hop1_566085708_1_212692.dat -- Oracle suggest
ORA-00280: change 12100176131169 for thread 1 is in sequence #212692
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
arch/sch1_566085708_1_212692.dat --- I input
ORA-00279: change 12100176131169 generated at needed for thread 2
==> Oracle didn't suggest thread 2 archive log file/
How can I find ?

You have to query V$ARCHIVED_LOG for THREAD# 2 on the source database to find the first archivelog where 12100176131169 is less than the NEXT_CHANGE#
select SEQEUNCE# from V$ARCHIVED_LOG where THREAD#=2 and 12100176131169 between FIRST_CHANGE# and NEXT_CHANGE#
Once you provide the Sequence# and file name for the first Thread 2 file, the RECOVER command will automatically generate the expected file name for the subsequent archivelogs (of both threads).
Hemant K Chitale

Datagurad setup from 2 Node RAC to single instance (DR site)

Dear Expert,
I have request from management to setup the DR site from current production RAC database using active dataguard. I have two node rac database 11.2.0.3 running on sun solaris machine. I need proper step or good document can refer to setup between production RAC database to DR site single instance standby database. I only experience setup single instance to single instance .Apreciate expert can provide me some link
Regard
liang

Hello;
This will provide a good start and overview :
Creating a Single Instance Physical Standby for a RAC Primary : ( please note parameter changes for Oracle 11 )
http://www.oracle.com/technetwork/database/features/availability/maa-wp-10g-racprimarysingleinstance-131970.pdf
As will this :
http://oracleinstance.blogspot.com/2012/01/create-single-instance-standby-database.html
Oracle 11
Rapid Oracle RAC Standby Deployment: Oracle Database 11g Release 2
http://www.oracle.com/technetwork/database/features/availability/maa-wp-11g-rac-standby-133152.pdf
Best Regards
mseberg

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

Dbms_schduler job is not running on a 2 node rac when 1st node fails

Hi,
I want to create a dbms_scheduler job in a 2 node RAC and the job should always run on the node1 and if node1 is down then it should run on node2. This is Oracle 10gR2 (10.2.0.3 in WINDOWS) .In order to do the same I did following
-- First Step
Using DBCA- Service Managment - Created a service (BATCH_SERVICE) and given node1 as preferred and node2 as available. This created following entry in tnsnames.ora in both nodes.
BATCH_SERVICE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = node1-vip)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = node2-vip)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = BATCH_SERVICE)
(FAILOVER_MODE =
(TYPE = SELECT)
(METHOD = BASIC)
(RETRIES = 180)
(DELAY = 5)
--- Step 2
-- Created BATCH job classes.
BEGIN
DBMS_SCHEDULER.create_job_class(
job_class_name => 'BATCH_JOB_CLASS',
service => 'BATCH_SERVICE');
END;
-- Step 3 -- created a job using job_class as BATCH_JOB_CLASS
begin
dbms_scheduler.create_job(
job_name => 'oltp_job_test'
,job_type => 'STORED_PROCEDURE'
,job_action => 'schema1.P1'
,start_date => systimestamp at time zone 'US/Central'
,repeat_interval => 'FREQ=DAILY;BYHOUR=11;BYMINUTE=30;'
,job_class => 'BATCH_JOB_CLASS'
,enabled => TRUE
,comments => 'New Job.');
end;
Now when I monitor this job it runs on node1. Now I started testing for failover. I manually shutdown 1st instance. Then as per my understanding job should run on 2nd node. But job is not picking up.
when I run the followign command
srvctl status service -d db -s BATCH_SERVICE
service BATCH_SERVICE is running on instance node2.
Any help is really appreciated.

It does not show that whether job is running or broken.

2 node RAC: one 10gR2 node and one 11.2.0.3 node on Solaris 10.

Is it possible to have a mixed Oracle version 2 node RAC with 10gR2 database on one machine and 11.2.0.3 database installed on the other machine. Has anyone done this?

Hi,
if you are talking about setting up a RAC, and having a database 10g running on one node, and a different database 11g running on the other node this is possible.
You will have to use the newest clusterware/GI (11.2.0.3) and multiple Oracle Homes (One for 10g and one for the 11.2.0.3).
If however you want one database with 2 instances running different versions: Then No.
Regards
Sebastian

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

Single instance standby for 2-node RAC

Hi,
Oracle Version:11.2.0.1
Operating system:Linux
Here i am planing to create single instance standby for my 2-node RAC database.Here i am creating my single instance standby database on 1-node of my 2-node RAC DB.
1.) Do i need to configure any separate listener for my single instance standby in $ORACLE_HOME/network/admin in ORACLE user or need to change in Grid user login.
2.) Below is the error when i am duplicating my primary 2-Node RAC to single instance DB. And it is shutting down my auxiliary instance.
[oracle@rac1 ~]$ rman target / auxiliary sys/racdba123@stand
Recovery Manager: Release 11.2.0.1.0 - Production on Sun Aug 28 13:32:29 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RACDB (DBID=755897741)
connected to auxiliary database: RACDB (not mounted)
RMAN> duplicate database racdba to stand
2> ;
Starting Duplicate Db at 28-AUG-11
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=6 device type=DISK
contents of Memory Script:
   sql clone "create spfile from memory";
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
   shutdown clone immediate;
   startup clone nomount;
executing Memory Script
Oracle instance shut down
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 08/28/2011 13:33:55
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptorAlso find my listener services.
[oracle@rac1 ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 29-AUG-2011 10:56:24
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date                18-AUG-2011 10:35:07
Uptime                    11 days 0 hr. 21 min. 17 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/11.2.0/grid/network/admin/listener.ora
Listener Log File         /u01/app/oracle/diag/tnslsnr/rac1/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.8.123)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.8.127)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "RACDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
Service "RACDBXDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
Service "stand" has 2 instance(s).
Instance "stand", status UNKNOWN, has 1 handler(s) for this service...
Instance "stand", status BLOCKED, has 1 handler(s) for this service...
Service "testdb" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
Service "testdb1" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
The command completed successfully
[oracle@rac1 ~]$ lsnrctl services
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 29-AUG-2011 10:56:35
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0 state:ready
         LOCAL SERVER
Service "RACDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:3 refused:0 state:ready
         LOCAL SERVER
Service "RACDBXDB" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "D000" established:0 refused:0 current:0 max:1022 state:ready
         DISPATCHER <machine: rac1.qfund.net, pid: 3975>
         (ADDRESS=(PROTOCOL=tcp)(HOST=rac1.qfund.net)(PORT=43731))
Service "stand" has 2 instance(s).
Instance "stand", status UNKNOWN, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0
         LOCAL SERVER
Instance "stand", status BLOCKED, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:669 refused:0 state:ready
         LOCAL SERVER
Service "testdb" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:3 refused:0 state:ready
         LOCAL SERVER
Service "testdb1" has 1 instance(s).
Instance "RACDB1", status READY, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:3 refused:0 state:ready
         LOCAL SERVER
The command completed successfully
[oracle@rac1 ~]$Tnsnames.ora file content.
RACDB =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = racdb-scan.qfund.net)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = RACDB)
#QFUNDRAC =
stand =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST= racdb-scan.qfund.net)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = stand)
      (UR = A)
)Please help me how to solve this problem.
Thanks & Regards,
Poorna Prasad.S

Hi,
Please find the output from v$dataguard_status from primary and standby
Primary
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARCH: LGWR is scheduled to archive destination LOG_ARCHIVE_DEST_2 after log swit
ch
ARCH: Beginning to archive thread 1 sequence 214 (4604093-4604095)
Error 12514 received logging on to the standby
ARCH: Error 12514 Creating archive log file to 'stand'
ARCH: Completed archiving thread 1 sequence 214 (4604093-4604095)
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
MESSAGE
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
MESSAGE
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
MESSAGE
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC2: Becoming the heartbeat ARCH
ARC7: Beginning to archive thread 1 sequence 215 (4604095-4604191)
ARC7: Completed archiving thread 1 sequence 215 (4604095-4604191)
ARC5: Beginning to archive thread 1 sequence 216 (4604191-4604471)
ARC5: Completed archiving thread 1 sequence 216 (4604191-4604471)
ARCt: Archival started
MESSAGE
ARC3: Beginning to archive thread 1 sequence 217 (4604471-4605358)
ARC3: Completed archiving thread 1 sequence 217 (4604471-4605358)
LNS: Standby redo logfile selected for thread 1 sequence 217 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 217
LNS: Completed archiving log 1 thread 1 sequence 217
LNS: Standby redo logfile selected for thread 1 sequence 218 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 218
MESSAGE
LNS: Completed archiving log 2 thread 1 sequence 218
ARC4: Beginning to archive thread 1 sequence 218 (4605358-4625984)
ARC4: Completed archiving thread 1 sequence 218 (4605358-4625984)
LNS: Standby redo logfile selected for thread 1 sequence 219 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 219
LNS: Completed archiving log 1 thread 1 sequence 219
ARC5: Beginning to archive thread 1 sequence 219 (4625984-4641358)
ARC5: Completed archiving thread 1 sequence 219 (4625984-4641358)
LNS: Standby redo logfile selected for thread 1 sequence 220 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 220
LNS: Completed archiving log 2 thread 1 sequence 220
ARC6: Beginning to archive thread 1 sequence 220 (4641358-4644757)
ARC6: Completed archiving thread 1 sequence 220 (4641358-4644757)
LNS: Standby redo logfile selected for thread 1 sequence 221 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 221
LNS: Completed archiving log 1 thread 1 sequence 221
MESSAGE
ARC7: Beginning to archive thread 1 sequence 221 (4644757-4648306)
ARC7: Completed archiving thread 1 sequence 221 (4644757-4648306)
LNS: Standby redo logfile selected for thread 1 sequence 222 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 222
LNS: Completed archiving log 2 thread 1 sequence 222
ARC8: Beginning to archive thread 1 sequence 222 (4648306-4655287)
ARC8: Completed archiving thread 1 sequence 222 (4648306-4655287)
LNS: Standby redo logfile selected for thread 1 sequence 223 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 223
LNS: Completed archiving log 1 thread 1 sequence 223
ARC9: Beginning to archive thread 1 sequence 223 (4655287-4655307)
ARC9: Completed archiving thread 1 sequence 223 (4655287-4655307)
LNS: Standby redo logfile selected for thread 1 sequence 224 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 224
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
MESSAGE
Error 3135 for archive log file 2 to 'stand'
LNS: Failed to archive log 2 thread 1 sequence 224 (3135)
ARC3: Beginning to archive thread 1 sequence 224 (4655307-4660812)
ARC3: Completed archiving thread 1 sequence 224 (4655307-4660812)
LNS: Standby redo logfile selected for thread 1 sequence 224 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 224
LNS: Completed archiving log 2 thread 1 sequence 224
LNS: Standby redo logfile selected for thread 1 sequence 225 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 225
LNS: Completed archiving log 1 thread 1 sequence 225
ARC4: Beginning to archive thread 1 sequence 225 (4660812-4660959)
ARC4: Completed archiving thread 1 sequence 225 (4660812-4660959)
LNS: Standby redo logfile selected for thread 1 sequence 226 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 226
LNS: Completed archiving log 2 thread 1 sequence 226
ARC5: Beginning to archive thread 1 sequence 226 (4660959-4664925)
MESSAGE
LNS: Standby redo logfile selected for thread 1 sequence 227 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 227
ARC5: Completed archiving thread 1 sequence 226 (4660959-4664925)
LNS: Completed archiving log 1 thread 1 sequence 227
LGWR: Error 1089 closing archivelog file 'stand'
ARC6: Beginning to archive thread 1 sequence 227 (4664925-4668448)
ARC6: Completed archiving thread 1 sequence 227 (4664925-4668448)
ARC5: Beginning to archive thread 1 sequence 228 (4668448-4670392)
ARC5: Completed archiving thread 1 sequence 228 (4668448-4670392)
MESSAGE
LNS: Standby redo logfile selected for thread 1 sequence 228 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 228
LNS: Completed archiving log 2 thread 1 sequence 228
ARC4: Standby redo logfile selected for thread 1 sequence 227 for destination LO
G_ARCHIVE_DEST_2
LNS: Standby redo logfile selected for thread 1 sequence 229 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 229
LNS: Completed archiving log 1 thread 1 sequence 229
ARC3: Beginning to archive thread 1 sequence 229 (4670392-4670659)
ARC3: Completed archiving thread 1 sequence 229 (4670392-4670659)
LNS: Standby redo logfile selected for thread 1 sequence 230 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 230
LNS: Completed archiving log 2 thread 1 sequence 230
ARC4: Beginning to archive thread 1 sequence 230 (4670659-4670679)
ARC4: Completed archiving thread 1 sequence 230 (4670659-4670679)
MESSAGE
LNS: Standby redo logfile selected for thread 1 sequence 231 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 231
LNS: Completed archiving log 1 thread 1 sequence 231
ARC5: Beginning to archive thread 1 sequence 231 (4670679-4690371)
ARC5: Completed archiving thread 1 sequence 231 (4670679-4690371)
LNS: Standby redo logfile selected for thread 1 sequence 232 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 232
MESSAGE
LNS: Completed archiving log 2 thread 1 sequence 232
ARC6: Beginning to archive thread 1 sequence 232 (4690371-4712566)
ARC6: Completed archiving thread 1 sequence 232 (4690371-4712566)
LNS: Standby redo logfile selected for thread 1 sequence 233 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 233
LNS: Completed archiving log 1 thread 1 sequence 233
ARC7: Beginning to archive thread 1 sequence 233 (4712566-4731626)
LNS: Standby redo logfile selected for thread 1 sequence 234 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 2 thread 1 sequence 234
ARC7: Completed archiving thread 1 sequence 233 (4712566-4731626)
LNS: Completed archiving log 2 thread 1 sequence 234
ARC8: Beginning to archive thread 1 sequence 234 (4731626-4753780)
LNS: Standby redo logfile selected for thread 1 sequence 235 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 235
ARC8: Completed archiving thread 1 sequence 234 (4731626-4753780)
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
MESSAGE
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3135 for archive log file 1 to 'stand'
LNS: Failed to archive log 1 thread 1 sequence 235 (3135)
ARC9: Beginning to archive thread 1 sequence 235 (4753780-4765626)
ARC9: Completed archiving thread 1 sequence 235 (4753780-4765626)
LNS: Standby redo logfile selected for thread 1 sequence 235 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 235
LNS: Completed archiving log 1 thread 1 sequence 235
LNS: Standby redo logfile selected for thread 1 sequence 236 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 236
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3135 for archive log file 2 to 'stand'
LNS: Failed to archive log 2 thread 1 sequence 236 (3135)
ARCa: Beginning to archive thread 1 sequence 236 (4765626-4768914)
ARCa: Completed archiving thread 1 sequence 236 (4765626-4768914)
LNS: Standby redo logfile selected for thread 1 sequence 236 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 2 thread 1 sequence 236
LNS: Completed archiving log 2 thread 1 sequence 236
LNS: Standby redo logfile selected for thread 1 sequence 237 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 237
LNS: Completed archiving log 1 thread 1 sequence 237
ARCb: Beginning to archive thread 1 sequence 237 (4768914-4770603)
ARCb: Completed archiving thread 1 sequence 237 (4768914-4770603)
LNS: Standby redo logfile selected for thread 1 sequence 238 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 238
LNS: Completed archiving log 2 thread 1 sequence 238
ARCc: Beginning to archive thread 1 sequence 238 (4770603-4770651)
ARCc: Completed archiving thread 1 sequence 238 (4770603-4770651)
LNS: Standby redo logfile selected for thread 1 sequence 239 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 239
LNS: Completed archiving log 1 thread 1 sequence 239
MESSAGE
ARCd: Beginning to archive thread 1 sequence 239 (4770651-4773918)
ARCd: Completed archiving thread 1 sequence 239 (4770651-4773918)
LNS: Standby redo logfile selected for thread 1 sequence 240 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 240
LNS: Completed archiving log 2 thread 1 sequence 240
ARCe: Beginning to archive thread 1 sequence 240 (4773918-4773976)
ARCe: Completed archiving thread 1 sequence 240 (4773918-4773976)
LNS: Standby redo logfile selected for thread 1 sequence 241 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 241
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Error 3135 for archive log file 1 to 'stand'
LNS: Failed to archive log 1 thread 1 sequence 241 (3135)
ARC3: Beginning to archive thread 1 sequence 241 (4773976-4774673)
ARC3: Completed archiving thread 1 sequence 241 (4773976-4774673)
LNS: Standby redo logfile selected for thread 1 sequence 241 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 241
LNS: Completed archiving log 1 thread 1 sequence 241
LNS: Standby redo logfile selected for thread 1 sequence 242 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 242
LNS: Completed archiving log 2 thread 1 sequence 242
ARC4: Beginning to archive thread 1 sequence 242 (4774673-4776045)
ARC4: Completed archiving thread 1 sequence 242 (4774673-4776045)
LNS: Standby redo logfile selected for thread 1 sequence 243 for destination LOG
_ARCHIVE_DEST_2
MESSAGE
LNS: Beginning to archive log 1 thread 1 sequence 243
LNS: Completed archiving log 1 thread 1 sequence 243
ARC5: Beginning to archive thread 1 sequence 243 (4776045-4776508)
ARC5: Completed archiving thread 1 sequence 243 (4776045-4776508)
LNS: Standby redo logfile selected for thread 1 sequence 244 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 244
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
MESSAGE
Error 3135 for archive log file 2 to 'stand'
LNS: Failed to archive log 2 thread 1 sequence 244 (3135)
ARC6: Beginning to archive thread 1 sequence 244 (4776508-4778741)
ARC6: Completed archiving thread 1 sequence 244 (4776508-4778741)
ARC7: Beginning to archive thread 1 sequence 245 (4778741-4778781)
ARC7: Completed archiving thread 1 sequence 245 (4778741-4778781)
ARC8: Beginning to archive thread 1 sequence 246 (4778781-4778787)
ARC8: Completed archiving thread 1 sequence 246 (4778781-4778787)
ARC9: Standby redo logfile selected for thread 1 sequence 244 for destination LO
G_ARCHIVE_DEST_2
MESSAGE
ARC3: Beginning to archive thread 1 sequence 247 (4778787-4778934)
LNS: Standby redo logfile selected for thread 1 sequence 247 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 247
ARC3: Completed archiving thread 1 sequence 247 (4778787-4778934)
LNS: Completed archiving log 1 thread 1 sequence 247
LNS: Standby redo logfile selected for thread 1 sequence 248 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 248
MESSAGE
ARC4: Beginning to archive thread 1 sequence 248 (4778934-4781018)
LNS: Completed archiving log 2 thread 1 sequence 248
ARC4: Completed archiving thread 1 sequence 248 (4778934-4781018)
LNS: Standby redo logfile selected for thread 1 sequence 249 for destination LOG
_ARCHIVE_DEST_2
LNS: Beginning to archive log 1 thread 1 sequence 249
LNS: Completed archiving log 1 thread 1 sequence 249
ARC5: Beginning to archive thread 1 sequence 249 (4781018-4781033)
ARC5: Completed archiving thread 1 sequence 249 (4781018-4781033)
LNS: Standby redo logfile selected for thread 1 sequence 250 for destination LOG
MESSAGE
_ARCHIVE_DEST_2
LNS: Beginning to archive log 2 thread 1 sequence 250
233 rows selected.
SQL>Standby
SQL> select message from v$dataguard_status;
MESSAGE
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC8: Archival started
ARC9: Archival started
ARCa: Archival started
MESSAGE
ARCb: Archival started
ARCc: Archival started
ARCd: Archival started
ARCe: Archival started
ARCf: Archival started
ARCg: Archival started
ARCh: Archival started
ARCi: Archival started
ARCj: Archival started
ARCk: Archival started
ARCl: Archival started
MESSAGE
ARCm: Archival started
ARCn: Archival started
ARCo: Archival started
ARCp: Archival started
ARCq: Archival started
ARCr: Archival started
ARCs: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC2: Becoming the heartbeat ARCH
Error 1017 received logging on to the standby
FAL[client, ARC2]: Error 16191 connecting to RACDB for fetching gap sequence
MESSAGE
ARCt: Archival started
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery starting Real Time Apply
Media Recovery Log /u02/stand/archive/1_119_758280976.arc
Media Recovery Waiting for thread 2 sequence 183
RFS[1]: Assigned to RFS process 30110
RFS[1]: Identified database type as 'physical standby': Client is ARCH pid 25980
RFS[2]: Assigned to RFS process 30118
RFS[2]: Identified database type as 'physical standby': Client is ARCH pid 26008
RFS[3]: Assigned to RFS process 30124
MESSAGE
RFS[3]: Identified database type as 'physical standby': Client is ARCH pid 26029
RFS[4]: Assigned to RFS process 30130
RFS[4]: Identified database type as 'physical standby': Client is ARCH pid 26021
ARC4: Beginning to archive thread 1 sequence 244 (4776508-4778741)
ARC4: Completed archiving thread 1 sequence 244 (0-0)
RFS[5]: Assigned to RFS process 30144
RFS[5]: Identified database type as 'physical standby': Client is LGWR ASYNC pid
26128
Primary database is in MAXIMUM PERFORMANCE mode
ARC5: Beginning to archive thread 1 sequence 247 (4778787-4778934)
MESSAGE
ARC5: Completed archiving thread 1 sequence 247 (0-0)
ARC6: Beginning to archive thread 1 sequence 248 (4778934-4781018)
ARC6: Completed archiving thread 1 sequence 248 (0-0)
ARC7: Beginning to archive thread 1 sequence 249 (4781018-4781033)
ARC7: Completed archiving thread 1 sequence 249 (0-0)
58 rows selected.
SQL>also find the output for the primary alertlog file.
Tue Aug 30 10:45:41 2011
LNS: Attempting destination LOG_ARCHIVE_DEST_2 network reconnect (3135)
LNS: Destination LOG_ARCHIVE_DEST_2 network reconnect abandoned
Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
ORA-03135: connection lost contact
Error 3135 for archive log file 2 to 'stand'
Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
ORA-03135: connection lost contact
LNS: Failed to archive log 2 thread 1 sequence 244 (3135)
Errors in file /u01/app/oracle/diag/rdbms/racdb/RACDB1/trace/RACDB1_nsa2_26128.trc:
ORA-03135: connection lost contact
Tue Aug 30 10:50:25 2011
Thread 1 advanced to log sequence 245 (LGWR switch)
Current log# 1 seq# 245 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 245 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Tue Aug 30 10:50:25 2011
Archived Log entry 612 added for thread 1 sequence 244 ID 0x2d0e0689 dest 1:
Thread 1 cannot allocate new log, sequence 246
Checkpoint not complete
Current log# 1 seq# 245 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 245 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Thread 1 advanced to log sequence 246 (LGWR switch)
Current log# 2 seq# 246 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 246 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Tue Aug 30 10:50:27 2011
Archived Log entry 613 added for thread 1 sequence 245 ID 0x2d0e0689 dest 1:
Thread 1 cannot allocate new log, sequence 247
Checkpoint not complete
Current log# 2 seq# 246 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 246 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Thread 1 advanced to log sequence 247 (LGWR switch)
Current log# 1 seq# 247 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 247 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Tue Aug 30 10:50:30 2011
Archived Log entry 614 added for thread 1 sequence 246 ID 0x2d0e0689 dest 1:
Tue Aug 30 10:51:37 2011
ARC9: Standby redo logfile selected for thread 1 sequence 244 for destination LOG_ARCHIVE_DEST_2
Tue Aug 30 10:51:39 2011
Thread 1 advanced to log sequence 248 (LGWR switch)
Current log# 2 seq# 248 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 248 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Tue Aug 30 10:51:39 2011
Archived Log entry 620 added for thread 1 sequence 247 ID 0x2d0e0689 dest 1:
Tue Aug 30 10:51:39 2011
LNS: Standby redo logfile selected for thread 1 sequence 247 for destination LOG_ARCHIVE_DEST_2
LNS: Standby redo logfile selected for thread 1 sequence 248 for destination LOG_ARCHIVE_DEST_2
Tue Aug 30 11:08:27 2011
Thread 1 advanced to log sequence 249 (LGWR switch)
Current log# 1 seq# 249 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 249 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Tue Aug 30 11:08:27 2011
Archived Log entry 622 added for thread 1 sequence 248 ID 0x2d0e0689 dest 1:
Tue Aug 30 11:08:27 2011
LNS: Standby redo logfile selected for thread 1 sequence 249 for destination LOG_ARCHIVE_DEST_2
Thread 1 cannot allocate new log, sequence 250
Checkpoint not complete
Current log# 1 seq# 249 mem# 0: +ASM_DATA1/racdb/onlinelog/group_1.268.758280977
Current log# 1 seq# 249 mem# 1: +ASM_DATA2/racdb/onlinelog/group_1.265.758280979
Thread 1 advanced to log sequence 250 (LGWR switch)
Current log# 2 seq# 250 mem# 0: +ASM_DATA1/racdb/onlinelog/group_2.269.758280979
Current log# 2 seq# 250 mem# 1: +ASM_DATA2/racdb/onlinelog/group_2.266.758280981
Tue Aug 30 11:08:31 2011
Archived Log entry 624 added for thread 1 sequence 249 ID 0x2d0e0689 dest 1:
LNS: Standby redo logfile selected for thread 1 sequence 250 for destination LOG_ARCHIVE_DEST_2Thanks & Regards,
Poorna Prasad.S

How to apply archivelogs from 2 node rac to non-rac

Is there any way to apply the archivelogs from 2 node RAC to sinlge node non-rac instance while migrating RAC to non-rac.
Could anyone clarify it?
-Shanlee

There's no "different way".
Each instance in RAC write's to it's own Redo Thread -- so each has it's own set of ArchiveLogs. In the log_archive_format specification %t is the thread identifier.
Oracle needs the ArchiveLogs from both Threads of the 2 node RAC. When you issue a RECOVER DATABASE, it applies them in the correct (interleaved) sequence.
What you have to do is to ensure that the ArchiveLogs of both threads are available on the new server.
Hemant K Chitale
Edited by: Hemant K Chitale on Jun 1, 2011 5:09 PM

2 Node RAC to single node clonning

Similar Messages

Maybe you are looking for