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

Similar Messages

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

RMAN backup restore from RAC to single instance ASM

Hi,
We are using oracle 11gR2 on AIX 6.1,
We need to restore RMAN backup from RAC to single instance ASM,
Im new to RAC & ASM, What will be the changes
What will be steps involved into it.
Thanks

Hello,
Refer this MOS doc *HowTo Restore RMAN Disk backups of RAC Database to Single Instance On Another Node [ID 415579.1]*
On the Single Instance ASM, you need to specify the diskgroup name for the parameters "control_files, db_create_file_dest"
Handle:      user10745179
Email:      [email protected]
Status Level:      Newbie (5)
Registered:      Feb 24, 2009
Total Posts:      168
Total Questions:      74 (52 unresolved)
Name      Devesh
Location      Mumbai If you feel that your questions have been answered, then please consider closing the threads by providing appropriate points. Please keep the forum clean !!
Regards,
Shivananda

Restore tablespace from rman

Hi everyone.
Im using a 11.0.6.0 database running on RHEL 5.
i have a full backup every saturday, and everyday a backup of archivelogs.
Could i restore a tablespace from 2 days ago with rman or i only can restore it from last saturday? how?
if i had 2 full backup, how to choose from wich one i want restore the tablespace?
Thanks in advance
Edited by: user13748341 on 14-jun-2011 6:52

user13748341 wrote:
Hi everyone.
Im using a 11.0.6.0 database running on RHEL 5.I don't think so. Where did you find an 11.ZERO? Oracle's first release at 11 was 11.1
>
i have a full backup every saturday, and everyday a backup of archivelogs.
Could i restore a tablespace from 2 days ago with rman or i only can restore it from last saturday? how?
if i had 2 full backup, how to choose from wich one i want restore the tablespace?
Thanks in advance
Edited by: user13748341 on 14-jun-2011 6:52You RESTORE the files from the backup of those files
You RECOVER the files to a point in time from the archivelogs since the backup from which you restored.
Go to tahiti.oracle.com and spend some time in the Backup and Recovery manuals to get clear on the concept of "backup", "recover", and "restore".

How to restore tablespace from backup

Dear all,
I need to restore my deleted tablespace from its backup. I backuped that tablespace with RMAN without catalog option. I connected the RMAN by the following way.
/home/oracle/db/bin/rman target / nocatalog
When I restoring the tablespace the following error occurs:
RMAN> run {
2> allocate channel ch1 type disk format '/disk6/backup/tek_backup/tek_bak1101';
3> restore tablespace tek_data;
4> }
Starting restore at 12-NOV-07
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/12/2007 17:13:48
RMAN-20202: tablespace not found in the recovery catalog
RMAN-06019: could not translate tablespace name "tek_data"
Please help

Here I am posting what I have done. Now I have the backuped tablespace by RMAN. I tried to restore it but couldn't.
Please help
##### 1. create tablespace & insert some data to it.
[oracle@localhost ~]$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Nov 12 19:14:50 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> conn /as sysdba
Connected.
SQL> CREATE SMALLFILE TABLESPACE "TS07" DATAFILE '/disk6/TS07_1' SIZE 100M LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;
Tablespace created.
SQL> create table MBS200710_1 tablespace TS07 as SELECT * FROM mediator.MBS200710 WHERE M105 = 3
2 ;
Table created.
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
##### 2. backup TS07 with RMAN
[oracle@localhost ~]$ /home/oracle/db/bin/rman target / nocatalog
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Nov 12 19:19:38 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: UCCS (DBID=1480994533)
using target database control file instead of recovery catalog
RMAN> run {
2> allocate channel c1 device type disk;
3> set command id to 'BBBackup';
4> configure backup optimization on;
5> sql "alter tablespace TS07 offline normal";
6> backup format '/disk6/backup/TS07_bak_%T_%U'
7> (tablespace TS07);
8> release channel c1;
9> sql "alter tablespace TS07 online";
10> }
allocated channel: c1
channel c1: sid=136 devtype=DISK
executing command: SET COMMAND ID
old RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters:
CONFIGURE BACKUP OPTIMIZATION ON;
new RMAN configuration parameters are successfully stored
sql statement: alter tablespace TS07 offline normal
Starting backup at 12-NOV-07
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00052 name=/disk6/TS07_1
channel c1: starting piece 1 at 12-NOV-07
channel c1: finished piece 1 at 12-NOV-07
piece handle=/disk6/backup/TS07_bak_20071112_0uj0srn6_1_1 tag=TAG20071112T193502 comment=NONE
channel c1: backup set complete, elapsed time: 00:00:01
Finished backup at 12-NOV-07
Starting Control File and SPFILE Autobackup at 12-NOV-07
piece handle=/disk6/backup/controlfile/c-1480994533-20071112-05 comment=NONE
Finished Control File and SPFILE Autobackup at 12-NOV-07
released channel: c1
sql statement: alter tablespace TS07 online
RMAN> quit
Recovery Manager complete.
##### 3. drop tablespace including data files
[oracle@localhost ~]$
[oracle@localhost ~]$
[oracle@localhost ~]$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Nov 12 19:37:38 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> conn /as sysdba
Connected.
SQL> drop tablespace TS07 including contents and datafiles;
Tablespace dropped.
SQL> commit;
Commit complete.
SQL> quit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
#####4. restore deleted tablespace from backup
[oracle@localhost ~]$ /home/oracle/db/bin/rman nocatalog target /
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Nov 12 19:39:59 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: UCCS (DBID=1480994533)
using target database control file instead of recovery catalog
RMAN> run {
2> allocate channel c1 type disk format '/disk6/backup/TS07_bak_20071112_0uj0srn6_1_1';
3> restore tablespace TS07;
4> release channel c1;
5> }
allocated channel: c1
channel c1: sid=76 devtype=DISK
Starting restore at 12-NOV-07
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/12/2007 19:41:48
RMAN-20202: tablespace not found in the recovery catalog
RMAN-06019: could not translate tablespace name "TS07"

Rman backup and restore from ASM env to Non ASM Environment

Hi,
I got a situation where i need to take RMAN Backup from ASM RAC environment and Restore that back to Non ASM standalone database.
Please let me know the procedure.
would appreciate your quick response

874152 wrote:
Hi,
I got a situation where i need to take RMAN Backup from ASM RAC environment and Restore that back to Non ASM standalone database.
Please let me know the procedure.
would appreciate your quick response
Hi,
You can follow this procedure
1. take the backup to destination host
2. restore spfile and controlfile
3. catalog the backup with command 'catalog start with <location of backup>'
4. use "set newname for datafile" to restore the datafile to non asm disk
5. restore database
6. recover database until point in time
7. rename redolog and tempfile
8. open database with resetlogs
9. remove redolog group from another instance
10. you might want to drop undo tablespace from another instance too
11. task complete
Cheers

How does a RAC DB 'spread' from single instance to multiple instances ?

GI/RDBMS Version: 11.2.0.3
OS: Oracle Linux 6.3
Filesystem : ASM
When a RAC database is created using dbca , Manually , or RMAN restore, the DB is created in the Node1 first with cluster_Database=FALSE .
Then you run the following commands (for 3-node RAC) from Node1
srvctl add database -d lmnprod -o $ORACLE_HOME -p +LMNPROD_DATA01/lmnprod/spfilelmnprod.ora
srvctl add instance -d lmnprod -i lmnprod1 -n hwcarser290
srvctl add instance -d lmnprod -i lmnprod2 -n hwcarser291
srvctl add instance -d lmnprod -i lmnprod3 -n hwcarser292
Once the DB is created,mounted and opened in Node1 and the above commands are executed , you set cluster_Database=TRUE and startup the Instance2 and Instance 3 in Node2 and Node3.
I just want to know how does Node2 and Node3 becomes aware of the DB and joins the DB cluster ? What happens internally ?

Generally speaking, registering in OCR is not required for database to be a cluster database.
Migration from single-instance database to cluster consists of creating redo logs and undo tablespace for new instance and enabling this instance (thread). If database is policy-managed, this is done automatically for new node.

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

Migrate from single instance to RAC manually

Hi,
I have a 10g database running in single instance.I have installed grid 11.2.0.2 in two nodes including the node where current instance is running,I have installed 10g again in a seperate mount point in both the nodes .It has the same patches as single instance 10g home.Now how to migrate from single instance to RAC manually.
Thanks,
Sekar

-restore this database into 11g ASM if its not already on ASM.
-upgrade this database to 11g from 10g on single instance.
-Now Converting Single Instance on a Cluster to Oracle RAC ,here you have different option to perform this once its 11g database after upgrade.
using rconfig
using dbca or manually.
see detail here
http://docs.oracle.com/cd/E11882_01/install.112/e24660/cvrt2rac.htm#autoId9

Restore a single tablespace from full backup erroring out

Hi,
I have backed up the full database using RMAN:
$ rman catalog rman/rman@catdb target /
RMAN> run {
backup as compressed backupset
format '<Full Path>/databkp/DATA_%d_%s_%p'
database
plus archivelog format '<Full Path>/arcbkp/ARC_%d_%s_%p';
Backup was successful.
Now dropped the tablespaces:
SQL> alter tablespace rtestusr offline;
SQL> drop tablespace RTESTUSR including contents and datafiles;
Now trying to restore the tablespace RTESTUSR
$ rman catalog rman/rman@catdb target /
RMAN> restore tablespace rtestusr;
Starting restore at 25-FEB-11
starting full resync of recovery catalog
full resync complete
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/25/2011 14:28:47
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20202: tablespace not found in the recovery catalog
RMAN-06019: could not translate tablespace name "RTESTUSR"
Also performed the Tablespace Point-in-time recovery:
RMAN> run {
2> set until time "to_date('2011-02-25:12:44:00','yyyy-mm-dd:hh24:mi:ss')";
3> restore tablespace RTESTUSR;
4> }
executing command: SET until clause
Starting restore at 25-FEB-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=46 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=45 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=44 devtype=DISK
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00006 to /dev2db/rmantst/db/oradata/rtest/rtestusr01.dbf
channel ORA_DISK_1: reading from backup piece /dev2db/rmantst/archrtst/databkp/DATA_RTEST_76_1
channel ORA_DISK_1: restored backup piece 1
piece handle=/dev2db/rmantst/archrtst/databkp/DATA_RTEST_76_1 tag=TAG20110225T114341
channel ORA_DISK_1: restore complete, elapsed time: 00:00:02
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/25/2011 15:07:42
ORA-19654: must use backup control file to switch file incarnations
Please help.
Thanks in advance.
Regards,
Bikram

I think you misunderstand some concepts.
1) drop tablespace RTESTUSR including contents and datafiles;
is a valid command, it removes the named tablespace from the database. There's nothing wrong with the database (although it may be a logical (human) error). Restore/recovery is used to repair media failures. RMAN is right: 'RMAN-06019: could not translate tablespace name "RTESTUSR"', since there's no such tablespace in the actual database, the restore/recover process fails.
2) Unfortunately you hide your database version. Up to 10gR2 tablespace point-in-time recovery cannot be used to recover dropped tablespaces, in 11gR1 and higher it's possible.
And - TSPITR - requires a little bit more than 'set until ...'. Refer to the doumentation for your unknown database version.
Werner

Restoring only the tablespace from the database

How do we restore only a 'tablespace' from a Terabyte database without restoring the entire database.
ie... if a particular tablespace has been dropped from the database and we have the backup available for the database.
So, how do we go about it for restoring only that tablespace.
Version:10.2.0.4
OS : solaris 10
Edited by: user13364377 on Sep 29, 2010 3:49 AM
Edited by: user13364377 on Sep 29, 2010 3:51 AM

If you have a RMAN backup before dropping the tablespace then we can restore the tablespace by below method
It is a tablespace point in time recovery ,here we need to create a auxillary DB.
Recover a table/tablespace from Rman backup on same server:
===============================================
Here we have to create the auxillary database.
1.u should have valid backup of the database before dropping the tablespace.
2.create the password file of target database.
orapwd file=$ORACLE_HOME\dbs\PWDORCL2.ORA password=oracle
3.Take backup of the control file to trace for creating the new control file for new
auxillary database/
SQL> alter database backup controlfile to trace;
sample control file:
STARTUP NOMOUNT
CREATE CONTROLFILE SET DATABASE "aux1" RESETLOGS FORCE LOGGING ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 454
LOGFILE
GROUP 1 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\aux1\REDO01.LOG' SIZE 10M,//make sure here to change the location of of redo
GROUP 2 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\aux1\REDO02.LOG' SIZE 10M, logs to new location or change the location name before
GROUP 3 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\aux1\REDO03.LOG' SIZE 10M //starating the database at the end.
-- STANDBY LOGFILE
DATAFILE
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\prafulla\SYSTEM01.DBF',
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\prafulla\UNDOTBS01.DBF',
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\prafulla\SYSAUX01.DBF',
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\prafulla\USERS01.DBF',
'D:\ORACLE\PRODUCT\10.1.0\ORADATA\prafulla\USERS02.DBF'
CHARACTER SET WE8MSWIN1252
4.create the password file of auxillary database.
orapwd file=$ORACLE_HOME\dbs\PWDORCL2.ORA password=oracle
5.create the control file
sqlplus "/as sysdba"
SQL>@create.sql
6 catalog all the backuppiece to the newly created database;
catalog backuppiece 'D:\oracle\product\10.1.0\LOG_707656915_50P1';
7.We have to restore system,sysaux,undo and the tablespace which was dropped
run
set newname for datafile 1 to 'D:\oracle\product\10.1.0\oradata\aux1\system01.dbf';
set newname for datafile 2 to 'D:\oracle\product\10.1.0\oradata\aux1\undotbs01.dbf';
set newname for datafile 5 to 'D:\oracle\product\10.1.0\oradata\aux1\users02.dbf';
set newname for datafile 3 to 'D:\oracle\product\10.1.0\oradata\aux1\sysaux01.dbf';
set newname for datafile 4 to 'D:\oracle\product\10.1.0\oradata\aux1\users01.dbf';
restore tablespace SYSTEM;
restore tablespace UNDOTBS1;
restore tablespace users;
restore tablespace sysaux;
switch datafile all;
8.Take the other tablespace offline
sqlplus>alter tablespace tablespace_name offline drop;
9.recover the database prior to the time when tha table/tablespace was dropped.
RMAN> run{
2> set until time "to_date('07-01-2010 14:00:00','dd-mm-yyyy hh24:mi:ss')";
3> recover database;
4> }
10.open the database in resetlog mode.
take a transpotable tablespace backup of that tablespace and import it on the database where you dropped it.

Restoring all archivelogs from a backuppiece for RAC DB?

Is there any way to tell rman to restore all archivelogs from a backuppiece (or backupset, which are equivalent in my case)?
Why I want to do this:
I want to restore quite large number of archivelogs (to recovering a standby database) from multiple backuppieces. I don't have enough space to restore them all together, so I need to restore the archivelogs, apply and delete. I know that RMAN allows to selectively restore archivelogs. However, I am facing problem as follows
- from scn ... until scn ... (or timestamp): The SCNs (or timestamps) of the archivelogs in different threads do not aligned well. As a result, in order to cover all archivelogs in a thread, RMAN will read another backppiece for the archivelogs across the boundary for other thread, doubling the time for the restore.
- from sequence ... until sequence ... thread ...: It seems impossible to specify both threads and make RMAN read once only.
It seems to me the solution is to restore all archivelogs from a backuppiece (or backupset), or the option to specify archivelogs one by one in single restore command, but both options are not available.
Oracle: 11.2.0.3 SE RAC
OS: RHEL 5

thtsang wrote:
Just found that it is possible to specific both threads in a single restore statement. However, it is still reading the backuppiece twice.
RMAN> restore archivelog sequence 10883 thread 1 archivelog sequence 6643 thread 2;
Starting restore at 2013-06-03:17:48:25
using channel ORA_DISK_1
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=1 sequence=10883
channel ORA_DISK_1: reading from backup piece /oracle/backupset/mydb/MYDB_al_20130602_1791_1_817002638
channel ORA_DISK_1: piece handle=/oracle/backupset/mydb/MYDB_al_20130602_1791_1_817002638 tag=TAG20130602T011037
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting archived log restore to default destination
channel ORA_DISK_1: restoring archived log
archived log thread=2 sequence=6643
channel ORA_DISK_1: reading from backup piece /oracle/backupset/mydb/MYDB_al_20130602_1791_1_817002638
channel ORA_DISK_1: piece handle=/oracle/backupset/mydb/MYDB_al_20130602_1791_1_817002638 tag=TAG20130602T011037
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
Finished restore at 2013-06-03:17:48:32It seems the best I can do is to specify a SCN range as large as possible, so that only the first & last backuppieces need to be read twice.
I also checked DBMS_BACKUP_RESTORE (though I am not sure whether RMAN use this), and seems there is no procedure to do what I want.It is good you restore 2 archived log sequence 10883 thread 1 and archived log sequence 6643 thread 2.
You can try
begin
dbms_backup_restore.restorearchivedlog(1,10883);
dbms_backup_restore.restorearchivedlog(2,6643);
end;Regards
Mahir M. Quluzade

Adjust parameters from single instance to RAC

Hi
I am carrying out a migration from single instance to RAC. I know there are a list of parameters that We have to adjust to keep the same or better performance moving from single instance to RAC. Can you post any link or something like that, that help to adjust the parameters ?
Thanks

user2931261 wrote:
Thanks
All is runing fine and the instaces are started. I set major of parameters of single instance but now I am getting a message that some of the parameters I set are DEPRECATED. How can I know what parameters are deprecated ?
ThanksORA-32004 obsolete and/or deprecated parameter(s) specified
Cause
One or more obsolete and/or parameters were specified in the SPFILE or the PFILE on the server side.
Action
See alert log for a list of parameters that are obsolete. or deprecated. Remove them from the SPFILE or the server side PFILE.
obsolete and/or deprecated parameter(s) in initDB.ora file. To find out which you could from SQL*PLUS, issue the following statement, to find the sinner.
SQL> select name, isspecified from v$obsolete_parameter where isspecified='TRUE';
refer:-http://oracleinstance.blogspot.com/2009/12/04-obsolete-andor-deprecated-parameters.html

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.

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

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

Similar Messages

Maybe you are looking for