SAN mirroring from RAC production to non-RAC DR

Hi Experts:
My client has a new project using 11gR2 and due to various reasons, they need to do the followings:
- Production Application #1 - 2 UNIX machines (likely AIX) running Oracle 11gR2 RAC, data residing on SAN
- Production Application #2 - 1 UNIX machine (AIX) running Oracle 11gR2 RAC, data residing on SAN
- DR site - Use 1 UNIX machine to host DBs (i.e. all non-RAC) for for both Applications #1 & #2.
Data are replicated from production to DR via SAN mirroring. (Clients decide not to use DataGuard for whatever reason).
I tried to find related info from Oracle website and Metalink with no luck.
Can anyone share there experiences on this , such as:
- Any restrictions or limitations ?
- Can we use only 1 Oracle binaries to host both DBs in DR site ?
- What about fallback from DR site back to the 2 production sites (1 RAC, 1 non-RAC) ?
Thanks and Regards
Airon

- Any restrictions or limitations ? Assuming you are using Same version & release. Of course you can have Different OS,
Here you can either have Normal FILE system, Lets suppose you have RAC on ASM even non-RAC(DR) you can have either on Normal file system (or) ASM file system.
Just take care of size of the mount point of where database resides & archives area size.
- Can we use only 1 Oracle binaries to host both DBs in DR site ?When standby is non-RAC, you have to use only one ORACLE_HOME, Here only Recovery will be in progress, No online threads will be active.
- What about fallback from DR site back to the 2 production sites (1 RAC, 1 non-RAC) ?What that mean? You mean switchover?
before switchover to a physical standby, all but one primary instances should be stopped; after switchover, started again.
http://docs.oracle.com/cd/E11882_01/server.112/e17022/rac_support.htm#i641732
Please describe more on it.
- For the production DB (application #1) with RAC, ASM will be used. So, what files from the 2 Unix servers / SAN must be replicated to DR?
- For the production DB (application #2) without RAC, ASM will not be used. So, what files from the 1 Unix server / SAN must be replicated DR ?I'm not sure for which application you are talking, All the database will be replicated to DR site either SAN or normal.
So you have to build standby database, Check below procedure to achieve this.
Here is document from MAA.
http://www.oracle.com/technetwork/database/features/availability/maa-wp-10g-racprimarysingleinstance-131970.pdf
- In the setup of DR DB server, what type of Oracle installation (need full install of grid + DB software , or just DB software) is needed.In standby you can have just Oracle Home. But cluster_database will be FALSE.
Let us know if any questions.

Similar Messages

How to restore (not duplicate) DB from RAC ASM to non ASM

Hello everybody,
i am trying to recover db from RAC+ASM to non ASM no RAC node. I am running Oracle 10g (10.2.0.4) on Win2003 Server. I have functional backup from my prod system.
Here are my steps:
*1. On prod server i make backup running this script in RMAN*
configure channel device type 'SBT_TAPE' parms'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=e:\backup)';
RUN {
backup device type SBT_TAPE database tag zal20081129;
SQL 'alter system archive log current';
backup device type SBT_TAPE archivelog ALL tag zal20081129;
*2. I prepared clon instance on another server (The same Oracle version) and start it to nomount mode.*
*3. I copied the backup from prod server to clon server to exactly the same path. (e:\backup)*
*4. I connect to RMAN on my new node and I use the DBID parameter and I restore controlfile.*
rman
connect target /
set DBID 3079749916
startup nomount
run {
allocate CHANNEL CTAPE DEVICE TYPE 'SBT_TAPE' PARMS'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=f:\backup)';
allocate channel CDISK DEVICE TYPE DISK;
restore controlfile from 'f:\backup\78k91lrn_1_1';
alter database mount;
*5.Then I check the backup, crosscheck etc.*
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
169 Full 42.78G SBT_TAPE 01:12:54 04-MAR-09
BP Key: 169 Status: AVAILABLE Compressed: NO Tag: DATAFILES
Handle: 75k91hcj_1_1 Media:
List of Datafiles in backup set 169
File LV Type Ckp SCN Ckp Time Name
1 Full 928460863 04-MAR-09 +DATA/agost/datafile/system.272.668509367
2 Full 928460863 04-MAR-09 +DATA/agost/datafile/undotbs1.273.668509387
3 Full 928460863 04-MAR-09 +DATA/agost/datafile/sysaux.263.668509393
4 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_archive_data.298.668509401
5 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_archive_index.258.668509401
6 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_blob.259.668509401
7 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_data.274.668509405
8 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_index.275.668509533
9 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_report_data.260.668509661
10 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_report_index.261.668509661
12 Full 928460863 04-MAR-09 +DATA/agost/datafile/undotbs2.264.668509661
13 Full 928460863 04-MAR-09 +DATA/agost/datafile/users.265.668509667
14 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_index.270.668510837
15 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_index.299.668510843
16 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_data.300.668510859
17 Full 928460863 04-MAR-09 +DATA/agost/datafile/ifsapp_data.301.668510865
BS Key Size Device Type Elapsed Time Completion Time
171 1.98G SBT_TAPE 00:02:54 04-MAR-09
BP Key: 171 Status: AVAILABLE Compressed: NO Tag: ARCHIVE_LOGS
Handle: 77k91lm2_1_1 Media:
List of Archived Logs in backup set 171
Thrd Seq Low SCN Low Time Next SCN Next Time
1 790 927018133 03-MAR-09 927379509 03-MAR-09
1 791 927379509 03-MAR-09 927635333 03-MAR-09
1 792 927635333 03-MAR-09 927804715 03-MAR-09
1 793 927804715 03-MAR-09 928438198 04-MAR-09
1 794 928438198 04-MAR-09 928496353 04-MAR-09
1 795 928496353 04-MAR-09 928496667 04-MAR-09
2 941 927018173 03-MAR-09 927414357 03-MAR-09
2 942 927414357 03-MAR-09 927725821 03-MAR-09
2 943 927725821 03-MAR-09 927747874 03-MAR-09
2 944 927747874 03-MAR-09 927804436 03-MAR-09
2 945 927804436 03-MAR-09 928375778 03-MAR-09
2 946 928375778 03-MAR-09 928460503 04-MAR-09
2 947 928460503 04-MAR-09 928496341 04-MAR-09
2 948 928496341 04-MAR-09 928496660 04-MAR-09
*6. Then I run this script to restore and recover db.*
run {
SET UNTIL SEQUENCE 795 THREAD 1;
SET UNTIL SEQUENCE 948 THREAD 2;
restore database;
switch datafile all;
recover database;
*7. Everything goes well see under.*
RMAN> 2> 3> 4> 5> 6> 7>
executing command: SET until clause
executing command: SET until clause
Starting restore at 04-MAR-09
using channel ORA_DISK_1
using channel ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: starting datafile backupset restore
channel ORA_SBT_TAPE_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DATA/agost/datafile/system.272.668509367
restoring datafile 00002 to +DATA/agost/datafile/undotbs1.273.668509387
restoring datafile 00003 to +DATA/agost/datafile/sysaux.263.668509393
restoring datafile 00004 to +DATA/agost/datafile/ifsapp_archive_data.298.668509401
restoring datafile 00005 to +DATA/agost/datafile/ifsapp_archive_index.258.668509401
restoring datafile 00006 to +DATA/agost/datafile/ifsapp_blob.259.668509401
restoring datafile 00007 to +DATA/agost/datafile/ifsapp_data.274.668509405
restoring datafile 00008 to +DATA/agost/datafile/ifsapp_index.275.668509533
restoring datafile 00009 to +DATA/agost/datafile/ifsapp_report_data.260.668509661
restoring datafile 00010 to +DATA/agost/datafile/ifsapp_report_index.261.668509661
restoring datafile 00012 to +DATA/agost/datafile/undotbs2.264.668509661
restoring datafile 00013 to +DATA/agost/datafile/users.265.668509667
restoring datafile 00014 to +DATA/agost/datafile/ifsapp_index.270.668510837
restoring datafile 00015 to +DATA/agost/datafile/ifsapp_index.299.668510843
restoring datafile 00016 to +DATA/agost/datafile/ifsapp_data.300.668510859
restoring datafile 00017 to +DATA/agost/datafile/ifsapp_data.301.668510865
channel ORA_SBT_TAPE_1: reading from backup piece 75k91hcj_1_1
channel ORA_SBT_TAPE_1: restored backup piece 1
piece handle=75k91hcj_1_1 tag=DATAFILES
channel ORA_SBT_TAPE_1: restore complete, elapsed time: 01:25:12
Finished restore at 04-MAR-09
Starting recover at 04-MAR-09
using channel ORA_DISK_1
using channel ORA_SBT_TAPE_1
starting media recovery
channel ORA_SBT_TAPE_1: starting archive log restore to default destination
channel ORA_SBT_TAPE_1: restoring archive log
archive log thread=1 sequence=794
channel ORA_SBT_TAPE_1: restoring archive log
archive log thread=2 sequence=947
channel ORA_SBT_TAPE_1: reading from backup piece 77k91lm2_1_1
channel ORA_SBT_TAPE_1: restored backup piece 1
piece handle=77k91lm2_1_1 tag=ARCHIVE_LOGS
channel ORA_SBT_TAPE_1: restore complete, elapsed time: 00:02:26
archive log filename=E:\ORADATA\AGOST\FLASHBACK\AGOST\ARCHIVELOG\2009_03_04\O1_MF_1_794_4TX5D7RD_.ARC thread=1 sequence=794
archive log filename=E:\ORADATA\AGOST\FLASHBACK\AGOST\ARCHIVELOG\2009_03_04\O1_MF_2_947_4TX5D7OY_.ARC thread=2 sequence=947
channel default: deleting archive log(s)
archive log filename=E:\ORADATA\AGOST\FLASHBACK\AGOST\ARCHIVELOG\2009_03_04\O1_MF_2_947_4TX5D7OY_.ARC recid=1563 stamp=680629925
channel default: deleting archive log(s)
archive log filename=E:\ORADATA\AGOST\FLASHBACK\AGOST\ARCHIVELOG\2009_03_04\O1_MF_1_794_4TX5D7RD_.ARC recid=1562 stamp=680629925
media recovery complete, elapsed time: 00:00:13
Finished recover at 04-MAR-09
*8. Then when i want to open database*
using command 'Alter system open resetlogs;' I got this error:
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 03/05/2009 07:26:03
RMAN-06003: ORACLE error from target database:
ORA-00600: internal error code, arguments: [kgeade_is_0], [|http://forums.oracle.com/forums/], [], [|http://forums.oracle.com/forums/], [], [|http://forums.oracle.com/forums/], [], [|http://forums.oracle.com/forums/]
In the alert log I have got this error: (for every log group)
ORA-00313: open failed for members of log group 4 of thread 2
ORA-00312: online log 4 thread 2: '+FLASHBACK/agost/onlinelog/group_4.260.668510637'
ORA-17503: ksfdopn:2 Failed to open file +FLASHBACK/agost/onlinelog/group_4.260.668510637
ORA-15001: diskgroup "FLASHBACK" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
ORA-00312: online log 4 thread 2: '+DATA/agost/onlinelog/group_4.268.668510633'
ORA-17503: ksfdopn:2 Failed to open file +DATA/agost/onlinelog/group_4.268.668510633
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ORA-15077: could not locate ASM instance serving a required diskgroup
ORA-29701: unable to connect to Cluster Manager
So obviouslly database wants to open online logs in the path like ASM. Which is wrong. What should I do to tell database to open it according to init.ora parameters
*.db_create_file_dest='e:\oradata\agost'
*.db_create_online_log_dest_1='e:\oradata\agost'
Any suggestions???
Thanks

Hi,
thanks for you quick answer. But I do restore to the local file system, even if the log says:
restoring datafile 00001 to +DATA/agost/datafile/system.272.668509367
restoring datafile 00002 to +DATA/agost/datafile/undotbs1.273.668509387 .....
all the datafiles are correctly restored. I think oracle uses the parameter db_create_file_dest and creates the files there.
I tried also the script with SET NEW NAME:
run {
Set newname for datafile 1 to 'e:\oradata\AGOST\system.272.668509367';
Set newname for datafile 2 to 'e:\oradata\AGOST\undotbs1.273.668509387';
Set newname for datafile 3 to 'e:\oradata\AGOST\sysaux.263.668509393';
Set newname for datafile 4 to 'e:\oradata\AGOST\ifsapp_archive_data.298.668509401';
Set newname for datafile 5 to 'e:\oradata\AGOST\ifsapp_archive_index.258.668509401';
Set newname for datafile 6 to 'e:\oradata\AGOST\ifsapp_blob.259.668509401';
Set newname for datafile 7 to 'e:\oradata\AGOST\ifsapp_data.274.668509405';
Set newname for datafile 8 to 'e:\oradata\AGOST\ifsapp_index.275.668509533';
Set newname for datafile 9 to 'e:\oradata\AGOST\ifsapp_report_data.260.668509661';
Set newname for datafile 10 to 'e:\oradata\AGOST\ifsapp_report_index.261.668509661';
Set newname for datafile 12 to 'e:\oradata\AGOST\undotbs2.264.668509661';
Set newname for datafile 13 to 'e:\oradata\AGOST\users.265.668509667';
Set newname for datafile 14 to 'e:\oradata\AGOST\ifsapp_index.270.668510837';
Set newname for datafile 15 to 'e:\oradata\AGOST\ifsapp_index.299.668510843';
Set newname for datafile 16 to 'e:\oradata\AGOST\ifsapp_data.300.668510859';
Set newname for datafile 17 to 'e:\oradata\AGOST\ifsapp_data.301.668510865';
Set newname for tempfile 1 to 'e:\oradata\AGOST\temp.276.668509397';
SQL "ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_1.256.668509345'' TO ''e:\oradata\AGOST\REDO01.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+FLASHBACK/agost/onlinelog/group_1.257.668509351'' TO ''e:\oradata\AGOST\REDO02.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_2.257.668509357'' TO ''e:\oradata\AGOST\REDO03.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+FLASHBACK/agost/onlinelog/group_2.258.668509361'' TO ''e:\oradata\AGOST\REDO04.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_3.266.668510623'' TO ''e:\oradata\AGOST\REDO05.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+FLASHBACK/agost/onlinelog/group_3.259.668510627'' TO ''e:\oradata\AGOST\REDO06.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_4.268.668510633'' TO ''e:\oradata\AGOST\REDO07.LOG'' ";
SQL "ALTER DATABASE RENAME FILE ''+FLASHBACK/agost/onlinelog/group_4.260.668510637'' TO ''e:\oradata\AGOST\REDO08.LOG'' ";
SET UNTIL SEQUENCE 795 THREAD 1;
SET UNTIL SEQUENCE 948 THREAD 2;
restore database;
switch datafile all;
recover database;
But it gives me this error in RMAN:
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
sql statement: ALTER DATABASE RENAME FILE ''+DATA/agost/onlinelog/group_1.256.668509345'' TO ''e:\oradata\AGOST\REDO01.LOG''
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 03/06/2009 10:48:55
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: ALTER DATABASE RENAME FILE '+DATA/agost/onlinelog/group_1.256.668509345' TO 'e:\oradata\AGOST\REDO01.LOG'
RMAN-11001: Oracle Error:
ORA-00600: internal error code, arguments: [kgeade_is_0], [], [], [], [], [], [], []
and in alert log i have got this:
Errors in file c:\oracle\product\10.2.0\admin\agost\udump\agost_ora_3200.trc:
ORA-00600: internal error code, arguments: [kgeade_is_0], [], [], [], [], [], [], []
Fri Mar 06 10:48:55 2009
ORA-600 signalled during: ALTER DATABASE RENAME FILE '+DATA/agost/onlinelog/group_1.256.668509345' TO 'e:\oradata\AGOST\REDO01.LOG' ...
dont know what to do.
There must be way how to recover it. I think my first try (without SET NEWNAME) is closer to the end, there is only need to "repair" the online logs.
Any other suggestions?
thanks

How to create a standby redolog from rac to non rac ??

Hi,
How to create a standby redolog from rac to non rac DR setup..???
in rac we can create with specifying thread number for each instances..... but this will be replicating to standby ....so how this will act/create on single DR??
pls help

854393 wrote:
Thanks Shivanandha,
(maximum number of logfiles for each thread + 1) * maximum number of threads
Using this equation reduces the likelihood that the primary instance's log writer (LGWR) process will be blocked because a standby redo log file cannot be allocated on the standby database. For example, if the primary database has 2 log files for each thread and 2 threads, then 6 standby redo log file groups are needed on the standby database.In maximum performance mode you can keep same number of redo logs but having one more redo log member for each thread is recommended and mandtory for other protection modes.
How to create a standby redolog from rac to non rac DR setup..???
in rac we can create with specifying thread number for each instances..... but this will be replicating to standby ....so how this will act/create on single DR??pls help
Yes, even your DR is RAC or non-RAC, you must have both threads, because each instance information exist on own thread, So to perform redo transition from both the instances, you must have both standby redo log threads even though if it is non an RAC DR.
Hope This helps.

R12 DB clone from RAC - ASM DB to Non RAC DB

Dear Friends,
I am using E-Biz- R12 PROD with 11g R2 RAC database.
I have an R12 DEV Instance (single node with Non RAC).
I want to perform DB clone from RAC - ASM DB (PROD) to Non RAC DB (TEST)
I am using RMAN backup on PROD database.
Please provide me the Metalink Note / steps to perform the same.
Regards,
DB

Please provide me the Metalink Note / steps to perform the same.Certified RAC Scenarios for E-Business Suite Cloning [ID 783188.1]
Cloning Oracle Applications Release 12 with Rapid Clone [ID 406982.1]
Rapid Clone Documentation Resources For Release 11i and 12 [ID 799735.1]
Cloning Oracle E-Business Suite Release 12 RAC-Enabled Systems with Rapid Clone [ID 559518.1]
Thanks,
Hussein

RMAN cloning from RAC to Non-RAC

Hi Gurus,
I had successfully cloned my DB from RAC to Non-RAC environment via RMAN. Below was the configuration
RAC
- 2 nodes
- 11gR2 (Compatible 11.0.1.6 as per Application Requirement)
- ASM (2 diskgroups DATA and FRA)
- OS RHEL 6.3
Non - RAC
- 1 node
- Stand alone11gR2 (Compatible 11.0.1.6 as per Application Requirement)
- ASM (2 diskgroups DATA and FRA)
- OS RHEL 6.3
My approach was to clone DB and then change SID with nid utility. My understanding was that nid utility will also replace ASM file paths from CRAMPRD to CRAMSIT but that didnt happen.
So issue is when I am checking my file paths on CRAMSIT it still refelect CRAMPRD eg - +DATA1/CRAMPRD. Is there any way to rename this directory paths in ASM so that it should reflect my SID.
Regards,
Nikhil Mehta.

No, NID wouldn't change the ASM paths.
I presume that you did set the ORACLE_SID to CRAMSIT on the non-RAC server before the restore.
What you should have done is to set DB_UNIQUE_NAME='CRAMSIT' (even with DB_NAME='CRAMPRD') on the non-RAC server before the restore. Oracle would have used the DB_UNIQUE_NAME to set the ASM PAth (note that during the restore it would have shown "restoring to +DATA1/CRAMPRD" but would have actually been restoring to "+DATA1/CRAMSIT").
You will now have to use Oracle Support Note
How to rename/move a datafile in the same ASM diskgroup [ID 564993.1]
to rename the paths in ASM.
Hemant K Chitale

Cloning of Database from RAC to non-RAC

We have 9i RAC database with Oracle 11.5.9 application,
Our management wants one new non-rac instance for Reporting purpose. They want Reporting instance should be re-fresh every night with automated process. I am looking for the help is there any way we can refresh the databse from RAC enviornement to non-rac enviornment. Please help us.
Thanks
Regards
Raj Sachdeva
Oracle Certified Master.

Hi;
Presently we are following RMAN duplicate database cloning from RAC asm to (non RAC)non asm database of size 1TB.
If suppose if our databse is 3TB or More. then is there method that we can minimize the cloning time. If so please let me know.We have 4 Tb RAC+ASM and we also follow same method. I belive there is no faster method, at least we can not find :)
Regard
Helios

Datagaurd swithover from rac to non rac.

Hello Team,
1.we have created single DR db for the RAC primary database, and we need to perform a swithover to the DR from RAC by DGMGRL, in this case how can we place an entry for both listeners for automatic restart by DGMGRL during the switchover activity ?
2.in this case which one better performing maunal switchover on sql prompt or by DGMGRL ?
3.do we need shutdown one instance during switchover to non rac or will be automatically taken care of DGMGRL???
4. once the non rac converted to primary which rac instance will be applying the logs on RAC standby from non rac?? No oracle docs saying this clearly pls help.
Thanks in advance.

Thanks victor,,,
almost 400GB,
one more, we did a switchover in sql from rac to Non rac (test setup), so after switching over the single node DR start using/following a thread1 redo's and log sequence, in such a case the rac become standby now and we started only instance 2 on rac and placed it on recover mode now, and its start applying logs from the single DR now,so can we start a another rac node also and place it on recover mode? is it possible,or do we need to disable any online log thread or standby log thread on new primary (single DR node) ???
also we can see the new primary control file says still some of archived log not applied, also the rac standby control file says now, there are two log file still not applied but those are in disk now... but during a switchover we followed below method and all completed successfully. the way only we confusing rac to single. all online log file and stand by redo on use for both the threads, pls help. why its showing below not applied.
from new Primary.(non rac)
SQL> select SEQUENCE#,thread#,APPLIED,ARCHIVED,DELETED,STATUS from v$archived_log;
SEQUENCE# THREAD# APPLIED ARC DEL S
15 2 YES YES YES D
35 1 YES YES NO A
17 2 YES YES NO A
16 2 YES YES NO A
19 2 YES YES NO A
23 2 YES YES NO A
20 2 YES YES NO A
18 2 YES YES NO A
21 2 YES YES NO A
22 2 YES YES NO A
38 1 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
36 1 YES YES NO A
39 1 YES YES NO A
37 1 YES YES NO A
24 2 YES YES NO A
25 2 YES YES NO A
26 2 YES YES NO A
27 2 YES YES NO A
28 2 YES YES NO A
29 2 YES YES NO A
30 2 YES YES NO A
31 2 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
32 2 YES YES NO A
33 2 YES YES NO A
35 2 YES YES NO A
34 2 YES YES NO A
36 2 YES YES NO A
37 2 YES YES NO A
38 2 YES YES NO A
39 2 YES YES NO A
40 2 YES YES NO A
41 2 YES YES NO A
42 2 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
43 2 YES YES NO A
44 2 YES YES NO A
45 2 NO YES NO A
40 1 NO YES NO A
46 2 NO YES NO A
47 2 NO YES NO A
41 1 NO YES NO A
42 1 NO YES NO A
43 1 NO YES NO A
44 1 NO YES NO A
45 1 NO YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
46 1 NO YES NO A
42 1 YES YES NO A
40 1 YES YES NO A
45 2 NO YES NO A
46 2 NO YES NO A
43 1 YES YES NO A
44 1 YES YES NO A
41 1 YES YES NO A
45 1 YES YES NO A
47 2 NO YES NO A
46 1 NO YES NO A
55 rows selected.
SQL>
=======================================================================
*From new standby rac --below*
SQL> /
SEQUENCE# THREAD# APPLIED ARC DEL S
13 2 YES YES NO A
14 2 YES YES NO A
25 1 YES YES NO A
26 1 YES YES NO A
27 1 YES YES NO A
28 1 YES YES NO A
29 1 YES YES NO A
30 1 YES YES NO A
31 1 YES YES NO A
32 1 YES YES NO A
33 1 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
34 1 YES YES NO A
35 1 YES YES NO A
15 2 YES YES NO A
16 2 YES YES NO A
17 2 YES YES NO A
36 1 YES YES NO A
18 2 YES YES NO A
19 2 YES YES NO A
37 1 YES YES NO A
20 2 YES YES NO A
38 1 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
39 1 YES YES NO A
21 2 YES YES NO A
22 2 YES YES NO A
23 2 YES YES NO A
17 2 YES YES NO A
16 2 YES YES NO A
19 2 YES YES NO A
23 2 YES YES NO A
18 2 YES YES NO A
20 2 YES YES NO A
21 2 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
22 2 YES YES NO A
24 2 YES YES NO A
36 1 YES YES NO A
38 1 YES YES NO A
39 1 YES YES NO A
37 1 YES YES NO A
24 2 YES YES NO A
25 2 YES YES NO A
25 2 YES YES NO A
26 2 YES YES NO A
26 2 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
27 2 YES YES NO A
27 2 YES YES NO A
28 2 YES YES NO A
28 2 YES YES NO A
29 2 YES YES NO A
29 2 YES YES NO A
30 2 YES YES NO A
30 2 YES YES NO A
31 2 YES YES NO A
31 2 YES YES NO A
32 2 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
32 2 YES YES NO A
33 2 YES YES NO A
33 2 YES YES NO A
34 2 YES YES NO A
35 2 YES YES NO A
36 2 YES YES NO A
35 2 YES YES NO A
34 2 YES YES NO A
36 2 YES YES NO A
37 2 YES YES NO A
37 2 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
38 2 YES YES NO A
38 2 YES YES NO A
39 2 YES YES NO A
39 2 YES YES NO A
40 2 YES YES NO A
40 2 YES YES NO A
41 2 YES YES NO A
41 2 YES YES NO A
42 2 YES YES NO A
42 2 YES YES NO A
43 2 NO YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
43 2 YES YES NO A
44 2 YES YES NO A
44 2 NO YES NO A
42 1 YES YES NO A
40 1 YES YES NO A
45 2 YES YES NO A
46 2 YES YES NO A
43 1 YES YES NO A
44 1 YES YES NO A
41 1 YES YES NO A
45 1 YES YES NO A
SEQUENCE# THREAD# APPLIED ARC DEL S
47 2 YES YES NO A
46 1 IN-MEMORY YES NO A
90 rows selected.
SQL>

After Cloning from RAC to non-RAC, how can convert PCP to Non PCP?

After Cloning 11i E-bussiness suit from RAC to non-RAC, how can convert PCP to Non PCP?

Hi Hussein
Please clear me if am wrong.
1.Say my applications release is 11.5.10.2 with RAC and PCP enabled and cloning to multi node[Apps on one node and db on one side] and disable PCP
1.I wil clone my db to db node.
2.Copy the applications file system to target node and run adcfgclone and provide the values accordingly and it would complete successfully.
Now i have multi node target system.
To disable PCP
1.do i need to disable :Change the site level system profile 'Concurrent:GSM_Enabled' to have a value of 'Y' and make it 'N'.[because GSM is enabled by default after 11.5.7 ]. If the profile option is SET Y will be get any errors while bringing up CM.
2.As per previous note you have given, APPLDCP is set to ON by default when GSM is enabled [Considering i m above the file version [afpcsq.lpc ] ]
and also is GSM neccessary for single node applications.
In this case will changing the profile value is enough to disable the PCP or do i need to change APPLDCP also.
Regards,
Mannu

Partial Restoration of Tablespace from RAC instance to non-RAC instance

when i am trying to restore tablespace from RAC environment to Non-RAC i got below error in my log
channel aux1: starting datafile backup set restore
channel aux1: restoring control file
channel aux1: reading from backup piece c-1840232663-20110405-01
channel aux1: ORA-19870: error while restoring backup piece c-1840232663-20110405-01
ORA-19507: failed to retrieve sequential file, handle="c-1840232663-20110405-01", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
sbtrestore: Job[0] thread[18841]: InitializeCLRestore() failed.
kindly revert,
Thanks & Regards,
MJ

I am not sure what you mean by "OS replication".
Whether you use RAC or a Failover Cluster, the database has to be on Shared Storage (which requires no "replication").
RAC licence costs are higher than that for a Failover Cluster because both instances have to licenced and the RAC option has to be purchased.
Of course, if the two nodes together are limited to 4 CPUs, you could consider Standard Edition to reduce the licencing costs.
DBA skills requirements are also higher for RAC.
With respect to your question "...will be sufficient for the avaialability purposes" it really depends on what your requirements are. People use RAC for Avaialability when it really is better positioned for Scalability. If you want only availability and can afford a few minutes downtime, and each node in the cluster can individually handle the user/batch loads, a Failover Cluster would suffice.
I suggest that you raise this question in the "Database - General" forum : General Database Discussions
or the "Real Application Clusters" forum : Real Application Clusters
"Replication" is the wrong forum for such a question.
When you do re-raise your question, please clarify your understinding of "OS replication".
Hemant K Chitale
Hemant K Chitale

Help needed in deleting nodes from RAC database

Our DB is 10g RAC database and the servers are Window 2003 server. Initially the database was configured to have 4 nodes. For some reason we stopped the instances in the first two nodes and the current database is running on node3 and node4. I queried the v$thread view and it shows 3 records. Thread 2 is closed and disabled. Thread 3 is open and public and thread 4 is open and private. Now we need to disconnect nodes 1 and 2 from RAC db and cluster ware (We use Oracle cluster ware) and plan to use those two servers for other purposes. Although I read through the Oracle doc regarding deleting node from RAC “11 Adding and Deleting Nodes and Instances on Windows-Based Systems” and wrote down the steps we need to take but I am still not comfortable in doing it since it is production env and we don’t have any dev env to practice those steps. So I would like to borrow your experiences and your lessons learned while you were doing those. Please share your thoughts and insights with us.
Thank you so much for your help,
Shirley

what's your full version? I can warn about specific issues in 10.1.0.3 and 10.2.0.1 - for example, in some cases (depending on how the listener was configured), it will be impossible to delete the listener for the deleted node. Known bug.
To avoid many many known bugs, you may want to upgrade to at least 10.2.0.2 before removing a node (from my experience, this is the first stable RAC version).
In any case, deleting a node is a rather delicate process. I really really recommend practicing. Take any pc/laptop, install VMWARE, define two virtual machines, install RAC and remove one node. It will take you an extra day or two, and could save your production.

Restore a database from RAC to standalone oracle server

Hi,
I wanted to know whether we can restore a RAC database to a standalone machine. Steps which i am planning to do
1) Create a stand alone server
2) Install oracle in the same path as that in RAC
3) Create a database of the same name
4) Re direct Restore to this location from RAC database
The database is non asm. Can any one let me know whether RAC database support redirect restore.
Amith

This is possible.You won't have to create the new database though. Rman will do this for you (after all, you restore/recover a full database). It is much easier when you also use ASM on the destination but is you do not want to use asm, you can still use rman to rename/relocate all datafiles to a non-asm location.
Bjoern

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.

RMAN duplicate from RAC with ASM to RAC with ASM

I'm still reading and trying to figure out how to duplicate...and I'm finding that there are some extra considerations you have to work with with doing a RAC system.
Does anyone have any good links to articles/docs that spell out what to do in this scenario?
I'm wanting to duplicate from tape backups, using NO connectivity to the source/target....
My tape backups do include the spfile and control files (autobackup) from the source.
Thank you in advance,
cayenne

damorgan wrote:
Possibly you are confusing a database with a database.
A RAC database is a just a database. What is different is the instances, the clusterware, and the storage: For example ASM.
A backup is a backup is a backup.
Can you be more specific about what you are trying to do, on what hardware, operating system, version, and edition.
RMAN can not create an instance either RAC or stand-alone.Thank you for the reply.
I have my source system, OS = RHEL5, running Oracle 11Gr2...5 node RAC cluster.
I'm doing RMAN backups to tape...hourly arch. logs, Daily incremental lvl=1 backups and weekly incremental lvl=0
None of the tape backups have ever been tested for restoring...and I've never restored a database myself before, total noob here.
I have a test area I've set up. I have a 2 node RAC cluster, running 11Gr2 and OS=RHEL5.
The tape is accessible from both systems.
I am wanting to test the tape backups...and thought the RMAN DUPLICATE process would be the way to go.
I am wanting to NOT connect to the source database...trying to simulate somewhat of a disaster recovery scenario. I'm only wanting to use tape backup, and the test area for the auxiliary instance.
So far what I've seen I need to learn to do is something like:
1. Create a password file for new aux database to be duplicated to
2. Establish Net connectivity...
3. Create initial parameter file for aux instance
Due to a bug in note:334899.1, add this (because of RAC system)
norecovery_through_resetlogs=TRUE
4. Start aux instance NOMOUNT
Everything I'm reading though...is basically doing this from single instance to single instance...and what little info I've seen on doing it from RAC, indicates there are some differences. The "_no_recovery_through_resetlogs=TRUE" is one thing I found...but wondering what else.
Also, so many of the examples I'm finding...are doing the duplication connecting to the target/source...and also doing backups to disk rather than tape...
Right now, I'm at #1...trying to figure what to put into an init pfile...I'm seeing DB_name, which will be the same as the one I'm cloning from.
I'm not sure what else....
I'm wondering if this is necessary..since on the tape backups from the source...I backup the SPFILE...can that not be used somehow in this?
I'm seeing for the init file, examples show that I need to put in entries for control files and redo logs....if the source system was down and gone...how would I know where these were on the old system? This isn't documented anywhere....is there a way to do this if you didn't know.
If not..guess I need to go through all systems and document the layouts of where everything is located.
Also...most examples I'm finding, in addition to being single instance backup and restore/duplication...they are all using regular file systems....not much to go on with using ASM.
Anyway, I'm trying to learn here...and am having trouble finding examples to go from that match my setup.
Thank you in advance,
cayenne

Restoring from rac to standalone

We have a production oracle database 9.2.0.4 (RAC) on AIX 5.0 with datafiles inplemented as raw devices. How can I restore it to a standalone AIX 5.0 machine with oracle 9.2.0.1 installed on it alongwith datafiles as raw devices with same names by using the hotbackup taken from RAC (using manual scripts not RMAN).

I want to bring my database to the state of 31July. After getting some information I need it to extend further to 10Aug. I have controlfiles backed up using 'alter database backup controlfile' of 31July and 10Aug and hot backup of datafiles as on 27July.

Failover from RAC to Single Instance db

Hi
i know that i can have a single instance db , as the failover option in my dataguard system
do i need to change some parameters while i am failing over from Rac DB to Single Instance DB
something like cluster_db = false
Thanks

RonHeeb wrote:
thanks for the response. i have been regularly taking current sizes of each SGA from gv$sgastat to see what's being allocated. my thinking is that this is a minimum and that i should add to it for peak loads, ensuring that it's not set below any minimum that RACOne requires.
beyond that going to RACOne seems to be a direction for virtualized DB servers and for us 24 by 7 is not needed (although more than a few minutes outage would be an issue). in any case if needed we could go RAC on our most critical environments. I'm attracted to how patching/server maintenance can be achieved with RACOne.Okay, you either need high availability or you don't. if having a db go down "for more than a few minutes" is a problem then, don't you really need 24x7 ? And in that case, isn't the high availability offered by RAC is your only option? For me, having a mission critical database (and it looks like this qualifies) on anything "vitualized" is a disaster waiting to happen. I find it lunacy to have, say, 4 virtual failover servers (RACOne) on the same physical hardware. When that server crashes so does your entire failover scenario.
>
Edited by: user10489842 on Sep 13, 2012 2:04 PM

SAN mirroring from RAC production to non-RAC DR

Similar Messages

Maybe you are looking for