ASM restore

11g ASM RAC, whole data raw disk group lost as SA mount raw disks to anther file system,
rebuild +data raw disk group.
rebuild spfile, restore controlfile.
do rman restore database
RMAN> restore database;
Starting restore at 02-OCT-08
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to +DATA/tester/datafile/system.260.662163575
channel ORA_DISK_1: restoring datafile 00002 to +DATA/tester/datafile/sysaux.266.662163575
channel ORA_DISK_1: restoring datafile 00003 to +DATA/tester/datafile/undotbs1.264.662163577
channel ORA_DISK_1: restoring datafile 00004 to +DATA/tester/datafile/users.263.662163577
channel ORA_DISK_1: restoring datafile 00005 to +DATA/tester/datafile/example.258.662163761
channel ORA_DISK_1: restoring datafile 00006 to +DATA/tester/datafile/undotbs2.256.662163961
channel ORA_DISK_1: reading from backup piece +DG1/tester/backupset/2008_08_15/nnndf0_tag20080815t112016_0.265.662815237
channel ORA_DISK_1: ORA-19870: error while restoring backup piece +DG1/tester/backupset/2008_08_15/nnndf0_tag20080815t112016_0.265.662815237
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15041: diskgroup space exhausted
I have 3 20gb raw disk +data group, tester is a small sample db<1gb,
ASMCMD> cd data
ASMCMD> du
Used_MB Mirror_used_MB
4407 4407
Q1. where did space go?
ASMCMD> ls -l
Type Redund Striped Time Sys Name
N CONTROLFILE/
N datafile/
N spfiletester.ora => +DATA/DB_UNKNOWN/PARAMETERFILE/SPFILE.327.6670637
Q2. the directory I manually created with " N " sign on it under sys column, while dbca created dir had a " Y" sign, what is step to restore db to asm storage?
Thanks.

'N' means these are user-created, but not system-generated ASM entries. Normally that happens when directories are created via 'alter diskgroup add directory ...' or mkdir statement inside asmcmd. User-created entries are aliases and ASM cannot resolve filenames to system names like '+DATA/tester/datafile/system.260.662163575'. Exactly that RMAN wants to do. Because you lost all your metadata you have to recreate your whole ASM environment (by the way 11g makes it possible to backup the metadata itself,which makes restore/recovery much easier). Follow the instructions from this metalink note:
Steps to Re-Create ASM Diskgroups
Doc ID: NOTE:268481.1
Werner

Similar Messages

Non-asm to asm restore using duplicate

oracle version 11.2.0.2.0
hello guys a quick question, I am trying to restore a database from non-asm to asm. I want to know if the following will work with the duplicate database.
SET NEWNAME for DATAFILE '/clu15/oracle/database/PROD/dbf/NDX_PROD.dbf' to '+DGDEV1DBDATA03/database/DEV/dbf/NDX_PROD.dbf';
SET NEWNAME for DATAFILE '/clu15/oracle/database/PROD/dbf/NDX_PROD_01.dbf' to '+DGDEV1DBDATA03/database/DEV/dbf/NDX_PROD_01.dbf';
SET NEWNAME for DATAFILE '/clu15/oracle/database/PROD/dbf/NDX_PROD_02.dbf' to '+DGDEV1DBDATA03/database/DEV/dbf/NDX_PROD_02.dbf';
SET NEWNAME for DATAFILE '/clu15/oracle/database/PROD/dbf/NDX_PROD_03.dbf' to '+DGDEV1DBDATA03/database/DEV/dbf/NDX_PROD_03.dbf';
Thank You

This above will work.
If you want to use OFA architecture, you can just give
SET NEWNAME for DATAFILE '/clu15/oracle/database/PROD/dbf/NDX_PROD.dbf' to '+DGDEV1DBDATA03';
You can also set the parameter db_file_name_convert and log_file_name_convert.

Cluster / ASM restore

All,
I've just come into a place and they have an issue in that i need to fix. Basically they have had disk corruption and have lost all the binaries etc for the Cluster and ASM ie everything under /u01/asm and /u01/crs on one of the nodes. They have an RMAN backup of the database (which is still running happily on the other node), but that's all. Am i correct in thinking that the easiest / quickest way to fix this would be to drop the faulty node and then re-add it etc or is there a better way ?
Oracle 10.2.0.4, AIX 6.1, 2 node RAC cluster.
Many thanks,
graham

Easiest way is to restore from backup.
If you do not have a backup, then go through the process to remove the node from inventory, CRS etc, then go through the process to add the node back to the cluster.

Recreating ASM & Restoring database

I have an Oracle 10g R2 server with 2 disk volumes. 1st one is for the OS and the Oracle install and the 2nd one is for the database managed by Oracle ASM. I have a full backup of the database I took using OEM.
I'm having to rebuild the 2nd disk volume therefore loosing everything on it, but will still have the Oracle install unaffected.
My question is after rebuilding the disk would it be OK to just create a new ASM group and create a new database. Then just restore the backup on to it using OEM?
Thanks for your help.

We're restoring a database from tape using Oracle 10.2.0.5. We explcitely specify the location for every single file with SET NEWNAME FOR DATAFILE X. The files that get restored don't match the NEWNAME format we set it to even though the log says it restored the file to that name. I don't know what's occuring under the hood of ASM, but it appears OMF is coming into play and generating names for the files. it's becoming a problem because when we restart the restore (which occurs often due to size of the database, length of time it takes, and drives going down) we start all over because RMAN doesn't know of the existing files. This doesn't seem to be normal behavior, and I know it's not like this during file based restores.
Does anyone know what's going on within ASM itself? It appears to be normal behavior when restoring to ASM and the names are later set appropriately after the SWITCH DATAFILE ALL. That's what I think would happen. It's currently a problem restarting restores.Have you enabled OMF? as db_create_file_dest = '+data'
then if you restore database from tape/disk, it will place all the datafiles as '+data/db_unique_name/datafiles';

OCR/Votting disk change location

Hi,
I need to move my 2 nodes RAC (Solaris 10 / Oracle 10g (10.2.0.3)) to a new data center.
My OCR and Votting disks are on a SAN (x) and on the new datacenter I want to put them on a new SAN (y).
How can I perform this server movement without losing the current RAC/Clusterware configuration?
I was planning to do the following:
- Backup current databases
- Backup spfile
- Backup Diskgroups/ASM configuration
- Delete databases
- Delete Diskgroups/ASM
- Shutdown CRS (crsctl stop crs)
- Backup OCR disks (ocrconfig -export export_filename)
- Backup Votting disks (dd if=voting_disk_name of=backup_file_name)
- Turn off the servers
- Move them to the new Datacenter
- Attch the new SAN
- Restore Votting disks (dd if=backup_file_name of=voting_disk_name)
- Restore OCR disks ( ocrconfig -import export_filename)
- Then recreate Diskgroups/ASM
- Restore databases
Is this the right procedure/commands to accomplish it without losing the RAC configuration?
I am trying to avoid rebuilding the whole RAC from scratch.
Thanks,
AShum

I forgot to mention that there is no connection between the old and new datacenter. If there would, I would just present the new SAN space from the new datacenter to the old one, so I can just add the new OCR/Votting disk to the current ones (mirror) and then remove the old disks.
Same for the ASM and databases, but unfortunally, there is no connection between this two datacenter.
It is like moving the servers from one state to another.
Thanks,

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

ORA-19870: error while restoring backup piece -- file exists in ASM

[oracle@rs1pre92dvdbsa01 ~]$ rman target sys/c9nv9sd9t9f11e@mdm11 auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Oct 29 10:41:38 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: MDM (DBID=1485385044)
connected to auxiliary database: MDM (not mounted)
RMAN> duplicate target database for standby;
Starting Duplicate Db at 29-OCT-10
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=13 device type=DISK
contents of Memory Script:
restore clone standby controlfile;
executing Memory Script
Starting restore at 29-OCT-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece +MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607
channel ORA_AUX_DISK_1: ORA-19870: error while restoring backup piece +MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607
ORA-19505: failed to identify file "+MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607"
ORA-17503: ksfdopn:2 Failed to open file +MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607
ORA-15012: ASM file '+MDMDG2/mdm1/autobackup/2010_10_29/s_733654605.283.733654607' does not exist
failover to previous backup
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/29/2010 10:42:00
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
RMAN>
ASMCMD [+mdmdg2] > cd mdm1
ASMCMD [+mdmdg2/mdm1] > ls
CONTROLFILE/
FLASHBACK/
ONLINELOG/
arch/
autobackup/
ASMCMD [+mdmdg2/mdm1] > cd autobackup
ASMCMD [+mdmdg2/mdm1/autobackup] > ls
2010_10_29/
ASMCMD [+mdmdg2/mdm1/autobackup] > cd 2010_10_29
ASMCMD [+mdmdg2/mdm1/autobackup/2010_10_29] > ls
s_733654605.283.733654607
As seen in asmcmd "s_733654605.283.733654607" file exists in +mdmdg2/mdm1/autobackup/2010_10_29 then why it is complaning that it can't find the file.
and also How to open/view file in asmcmd

[oracle@rs1pre91dvdbaa01 utl]$ sqlplus / as sysasm
SQL*Plus: Release 11.2.0.1.0 Production on Fri Oct 29 13:11:44 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup;
ORA-01078: failure in processing system parameters
ORA-29701: unable to connect to Cluster Synchronization Service
I have rebooted both the RAC servers and I can't start database?
I was under the impression that Database should be automatically started as part of Clusterware
Please help urgent.

Restore Database to non-ASM Storage - Issue with Bigfile Tablespace

I have been testing a restore of my prod database that uses ASM (and oracle managed files) for storage to a different server and non-ASM storage. Oracle version is 10g EE. My database has one bigfile tablespace and it's datafile is about 250GB. The restore fails and it has something to do with the bigfile tablespace.
Here is the rman restore script:
run
set newname for datafile 1 to '/ora01/db/ehr/system01.dbf';
set newname for datafile 2 to '/ora01/db/ehr/undotbs01.dbf';
set newname for datafile 3 to '/ora01/db/ehr/sysaux01.dbf';
set newname for datafile 4 to '/ora01/db/ehr/undotbs02.dbf';
set newname for datafile 5 to '/ora01/db/ehr/users01.dbf';
set newname for datafile 6 to '/ora01/db/ehr/apolloaud01.dbf';
set newname for datafile 7 to '/ora01/db/ehr/apollohist01.dbf';
set newname for datafile 8 to '/ora01/db/ehr/apolloidx01.dbf';
set newname for datafile 9 to '/ora01/db/ehr/apollotab01.dbf';
set newname for datafile 10 to '/ora01/db/ehr/apollotab02.dbf';
set newname for datafile 11 to '/ora02/db/ehr/apollolob01.dbf';
set newname for datafile 12 to '/ora01/db/ehr/apollofdb01.dbf';
set newname for datafile 13 to '/ora01/db/ehr/apolloidx02.dbf';
set newname for datafile 14 to '/ora01/db/ehr/apolloidx03.dbf';
set newname for datafile 15 to '/ora01/db/ehr/apolloaud02.dbf';
set newname for datafile 16 to '/ora01/db/ehr/apollotab03.dbf';
set until sequence 60298 thread 2;
restore database;
switch datafile all;
recover database;
Datafile 11 is the datafile in the bigfile tablespace. Here are the weird things about the restore:
1. The restore output shows this:
creating datafile fno=11 name=/ora02/db/ehr/apollolob01.dbf
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /ora01/db/ehr/system01.dbf
restoring datafile 00002 to /ora01/db/ehr/undotbs01.dbf
restoring datafile 00003 to /ora01/db/ehr/sysaux01.dbf
restoring datafile 00004 to /ora01/db/ehr/undotbs02.dbf
restoring datafile 00005 to /ora01/db/ehr/users01.dbf
restoring datafile 00006 to /ora01/db/ehr/apolloaud01.dbf
restoring datafile 00007 to /ora01/db/ehr/apollohist01.dbf
restoring datafile 00008 to /ora01/db/ehr/apolloidx01.dbf
restoring datafile 00009 to /ora01/db/ehr/apollotab01.dbf
restoring datafile 00010 to /ora01/db/ehr/apollotab02.dbf
restoring datafile 00012 to /ora01/db/ehr/apollofdb01.dbf
restoring datafile 00013 to /ora01/db/ehr/apolloidx02.dbf
restoring datafile 00014 to /ora01/db/ehr/apolloidx03.dbf
restoring datafile 00015 to /ora01/db/ehr/apolloaud02.dbf
restoring datafile 00016 to /ora01/db/ehr/apollotab03.dbf
Why at the beginning is it "creating" datafile 11? Then it doesnt even say it is "restoring" that datafile. Only restoring datafiles 1,2,3,4,5,6,7,8,9,10,12,13,14,15, and 16.
When it creates datafile 11 it is only 26GB, that is much smaller than it should be according to v$datafile view on source prod database. Also even though it says it is creating datafile 11 as /ora02/db/ehr/apollolob01.dbf it actually creates it as an oracle managed file at /ora02/db/ehr/EHR/datafile/o1_mf_apollolo_6crxyqs2_.dbf
After the datafiles are restored the "switch datafile all" command fails:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of switch command at 10/18/2010 13:58:37
ORA-19625: error identifying file /ora02/db/ehr/apollolob01.dbf
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
So my question is how do I get this database restored to non-ASM (and non omf)?

So I tried using a different scn with my "set until scn #####" then the restore created 2 datafiles. The datafile for apollolob and apollotab02.dbf. So I think I have narrowed the problem to be that I am not using the correct scn number so RMAN can successfully restore those datafiles and recreates them instead. How do I find the correct scn to use to do a successful restore of the entire database? I have seen different methods on the web, but cant figure it out. Ive used "select archivelog_change#-1 from v$database;" and I also did "list backup of archivelog all" and used the latest sequence number. How can I find the correct scn to use so the entire database will restore?
Here is the output of "list backup":
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
19724 41.12M DISK 00:00:10 14-OCT-10
BP Key: 65840 Status: AVAILABLE Compressed: YES Tag: TAG20101014T210022
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113195_piece1_copy1_20101014
List of Archived Logs in backup set 19724
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50439 3230234843 14-OCT-10 3230268282 14-OCT-10
1 50440 3230268282 14-OCT-10 3230286806 14-OCT-10
2 60280 3230234852 14-OCT-10 3230251419 14-OCT-10
2 60281 3230251419 14-OCT-10 3230268263 14-OCT-10
2 60282 3230268263 14-OCT-10 3230286809 14-OCT-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
19725 Full 126.40G DISK 09:11:51 15-OCT-10
List of Datafiles in backup set 19725
File LV Type Ckp SCN Ckp Time Name
1 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/system.625.609259453
2 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs1.620.609259461
3 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/sysaux.768.609259463
4 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/undotbs2.632.609259467
5 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/users.257.609259471
6 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.316.619537285
7 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollohist.629.619538155
8 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.312.619538169
9 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.276.619538487
10 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.576.619539331
11 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollolob.570.619539593
12 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollofdb.750.645974339
13 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.429.651171265
14 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloidx.705.688680793
15 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apolloaud.747.699632315
16 Full 3230287009 14-OCT-10 +DATA/ehr/datafile/apollotab.330.715622123
Backup Set Copy #1 of backup set 19725
Device Type Elapsed Time Completion Time Compressed Tag
DISK 09:11:51 20-OCT-10 YES TAG20101014T210039
List of Backup Pieces for backup set 19725 Copy #1
BP Key Pc# Status Piece Name
65851 1 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece1_copy1_20101014
65862 2 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece2_copy1_20101014
65873 3 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece3_copy1_20101014
65884 4 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece4_copy1_20101014
65895 5 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece5_copy1_20101014
65901 6 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece6_copy1_20101014
65902 7 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece7_copy1_20101014
65903 8 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece8_copy1_20101014
65904 9 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece9_copy1_20101014
65841 10 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece10_copy1_20101014
65842 11 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece11_copy1_20101014
65843 12 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece12_copy1_20101014
65844 13 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece13_copy1_20101014
65845 14 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece14_copy1_20101014
65846 15 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece15_copy1_20101014
65847 16 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece16_copy1_20101014
65848 17 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece17_copy1_20101014
65849 18 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece18_copy1_20101014
65850 19 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece19_copy1_20101014
65852 20 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece20_copy1_20101014
65853 21 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece21_copy1_20101014
65854 22 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece22_copy1_20101015
65855 23 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece23_copy1_20101015
65856 24 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece24_copy1_20101015
65857 25 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece25_copy1_20101015
65858 26 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece26_copy1_20101015
65859 27 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece27_copy1_20101015
65860 28 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece28_copy1_20101015
65861 29 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece29_copy1_20101015
65863 30 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece30_copy1_20101015
65864 31 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece31_copy1_20101015
65865 32 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece32_copy1_20101015
65866 33 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece33_copy1_20101015
65867 34 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece34_copy1_20101015
65868 35 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece35_copy1_20101015
65869 36 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece36_copy1_20101015
65870 37 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece37_copy1_20101015
65871 38 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece38_copy1_20101015
65872 39 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece39_copy1_20101015
65874 40 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece40_copy1_20101015
65875 41 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece41_copy1_20101015
65876 42 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece42_copy1_20101015
65877 43 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece43_copy1_20101015
65878 44 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece44_copy1_20101015
65879 45 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece45_copy1_20101015
65880 46 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece46_copy1_20101015
65881 47 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece47_copy1_20101015
65882 48 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece48_copy1_20101015
65883 49 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece49_copy1_20101015
65885 50 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece50_copy1_20101015
65886 51 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece51_copy1_20101015
65887 52 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece52_copy1_20101015
65888 53 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece53_copy1_20101015
65889 54 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece54_copy1_20101015
65890 55 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece55_copy1_20101015
65891 56 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece56_copy1_20101015
65892 57 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece57_copy1_20101015
65893 58 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece58_copy1_20101015
65894 59 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece59_copy1_20101015
65896 60 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece60_copy1_20101015
65897 61 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece61_copy1_20101015
65898 62 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece62_copy1_20101015
65899 63 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece63_copy1_20101015
65900 64 AVAILABLE /mnt/migrate/rman/EHR_dbid3632734257_set113196_piece64_copy1_20101015
BS Key Size Device Type Elapsed Time Completion Time
19726 228.10M DISK 00:00:49 15-OCT-10
BP Key: 65905 Status: AVAILABLE Compressed: YES Tag: TAG20101015T061242
Piece Name: /mnt/migrate/rman/EHR_dbid3632734257_set113197_piece1_copy1_20101015
List of Archived Logs in backup set 19726
Thrd Seq Low SCN Low Time Next SCN Next Time
1 50441 3230286806 14-OCT-10 3230331993 14-OCT-10
1 50442 3230331993 14-OCT-10 3230401945 14-OCT-10
1 50443 3230401945 14-OCT-10 3230469794 15-OCT-10
1 50444 3230469794 15-OCT-10 3230555010 15-OCT-10
1 50445 3230555010 15-OCT-10 3230618396 15-OCT-10
1 50446 3230618396 15-OCT-10 3230695020 15-OCT-10
2 60283 3230286809 14-OCT-10 3230304858 14-OCT-10
2 60284 3230304858 14-OCT-10 3230330891 14-OCT-10
2 60285 3230330891 14-OCT-10 3230354275 14-OCT-10
2 60286 3230354275 14-OCT-10 3230366292 14-OCT-10
2 60287 3230366292 14-OCT-10 3230399805 14-OCT-10
2 60288 3230399805 14-OCT-10 3230423577 14-OCT-10
2 60289 3230423577 14-OCT-10 3230446176 15-OCT-10
2 60290 3230446176 15-OCT-10 3230469756 15-OCT-10
2 60291 3230469756 15-OCT-10 3230496786 15-OCT-10
2 60292 3230496786 15-OCT-10 3230524710 15-OCT-10
2 60293 3230524710 15-OCT-10 3230554981 15-OCT-10
2 60294 3230554981 15-OCT-10 3230583802 15-OCT-10
2 60295 3230583802 15-OCT-10 3230610465 15-OCT-10
2 60296 3230610465 15-OCT-10 3230617887 15-OCT-10
2 60297 3230617887 15-OCT-10 3230673207 15-OCT-10
2 60298 3230673207 15-OCT-10 3230695022 15-OCT-10

RMAN restore from active database, ASM

I'm attempting to refresh a stage database from a prod database using RMAN restore from active database. Both are on ASM. After working through various hurdles, I've got one issue I'm a bit stuck on. I've got a handful of data files that do NOT have OMF names (ie MSTRDATA/mstrmdpd/datafile/gsa_indx instead of MSTRDATA/mstrmdpd/datafile/gsa_indx.351.714779777) and these are failing when I do the restore. The syntax I'm using in RMAN is as follows:
duplicate target database to dwstage
from active database
spfile parameter_value_convert 'dwprod','dwstage'
SET DB_FILE_NAME_CONVERT '+DWPROD','+DWSTAGE'
SET LOG_FILE_NAME_CONVERT '+DWPROD','+DWSTAGE';
The error message I'm getting is this:
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 04/21/2011 13:26:24
ORA-17628: Oracle error 19505 returned by remote Oracle server
continuing other job steps, job failed will not be re-run
Normally from what I've seen/read this error can be traced back to needing to pre-create the directories for the controlfiles etc, but since 90% of the datafiles copied correctly...
Any suggestions as to a way around this, or am I going to be forced to restore from a backupset?

This fails saying that "ORA-12528: TNS:listener: all appropriate instances are blocking new connections" which is quite normal given that the listener is havig a handle in BLOCKED state for this AUXDB as it is in NOMOUNT state.
Could you please help me on how to proceed?
One option can be to create the controlfile manually and mount the instance before doing the duplicate. I hope Rman can continue from there.
Another option is to go for backup based duplicate.
Is there any other way to go?
Provide static registration on AUXILIARY side for your auxiliary instance and try again.For example change listener.ora file as
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = AUXDB)
      (ORACLE_HOME = <your oracle home>)
      (SID_NAME = AUXDB)
LISTENER =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = <auxiliary host/ip>)(PORT = 1521))
)And restart listener on auxiliary host then try again

Create guaranteed restore point in oracle 10g RAC ASM

Hi DBAs,
In our production environment we have 2 node master RAC database (Oracle 10.2.0.5) (node1 name=master1 and node2 name=master2)
for which there is going to be a release tonight so want to create a guaranteed restore point for this RAC database.
I have googled many and found some ways, but before I implement it wanted a reviews from experts here.
Note: We already have db_recovery_file_dest set up in ASM...db_flashback_retention_target=1440 and db_recovery_file_dest_size=200GB with arch mode ON.
The steps are
STOP the RAC Database on Both Nodes...
Node1:
$srvctl stop database -d
$Srvctl stop database –d master1
Node2:
$srvctl stop database -d
$Srvctl stop database –d master2
And now start one instance only in mount state:
On node1:
SQL> startup mount
Now enable flashback on Node1...
SQL> alter database flashback on;
SQL> alter database open;
SQL>CREATE RESTORE POINT before_upgrade GUARANTEE FLASHBACK DATABASE;
Now start the second instance…
$srvctl start instance -d -i
$srvctl start instance –d master1 –d master2
Please let me know if there is something needs to be rectified.
Regards,
Ritz

The steps look fine.
Presumably you've already checked to see if the database is in flashback mode and it isn't...hence you putting it into flashbac mode?
Probably just typos but it looks like you have interchanged database names and instance names in your commands....you have the following commands. The srvctl commnds can be run from any node (ie you do not have to run it on node1 to shutdown instance1 and node2 to shutdown instance2).
Node1:    srvctl stop database –d master1
Node2:    srvctl stop database –d master2
You would run either:
Any node:    srvctl stop database -d master (assuming you database name is master...this will shut down both instances)
OR shutdown each instance individually
Any node:    srvctl stop instance -d master -i master1
Any node:    srvctl stop instance -d master -i master2
Same commnds as above to start using "srvctl start"...the following start commands do not look right to me:
srvctl start instance -d -i
srvctl start instance –d master1 –d master2

Using RMAN restore the database on a new host in ASM

Hello All,
I am trying to restore a database without using RMAN database duplicate. I want to do set new name for datafile and rename log file for online logs and change database name at last using NID.
here are details
source database - APSPROD / server - X
target database - EMERALD / Server -Y
Compressed backup is copied to destination server and I am trying to restore database using RMAN. Here is my init.ora file
cat initAPSPROD1.ora
DB_NAME=APSPROD
compatible=11.2.0.3
sga_target=8G
CONTROL_FILES='+DATA_DM01/EMERALD/controlfile/cntrl01.dbf','+RECO_DM01/EMERALD/controlfile/cntrl02.dbf','+DATA_DM01/EMERALD/controlfile/cntrl03.dbf'
DB_BLOCK_SIZE=8192
db_file_name_convert=(+DATA_DM01/APSPROD,+DATA_DM01/EMERALD)
log_file_name_convert=(+DATA_DM01/APSPROD,+DATA_DM01/EMERALD,+RECO_DM01/APSPROD,+RECO_DM01/EMERALD)
DB_RECOVERY_FILE_DEST='+RECO_DM01'
DB_RECOVERY_FILE_DEST_SIZE=5500G
So from above you can see that control file should be restored to +DATA_DM01/EMERALD and +RECO_DM01/EMERALD path.
Question -
when I am trying to restore control file. It creates an ASM alias name in +DATA_DM01/EMERALD/controlfile/cntrl01.dbf',+RECO_DM01/EMERALD/controlfile/cntrl02.dbf',' and +DATA_DM01/EMERALD/controlfile/cntrl03.dbf' but It creates fully Qualified ASM Filename under +DATA_DM01/APSPROD and +RECO_DM01/
Here is output
RMAN> restore controlfile from '/dbfs_direct/FS1/RMAN_APSPROD/cf_APSPROD_i4p4b62m_1_1
2> ;
Starting restore at 02-APR-14
using channel ORA_DISK_1
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
output file name=+DATA_DM01/emerald/controlfile/cntrl01.dbf
output file name=+RECO_DM01/emerald/controlfile/cntrl02.dbf
output file name=+DATA_DM01/emerald/controlfile/cntrl03.dbf
Finished restore at 02-APR-14
output at ASM level
SMCMD [+RECO_DM01/EMERALD/CONTROLFILE] > ls -l
Type         Redund Striped Time             Sys Name
                                               N    cntrl02.dbf => +RECO_DM01/APSPROD/CONTROLFILE/current.17006.843826701
ASMCMD [+RECO_DM01/EMERALD/CONTROLFILE] > cd +RECO_DM01/APSPROD/CONTROLFILE/
ASMCMD [+RECO_DM01/APSPROD/CONTROLFILE] > ls -l
Type         Redund Striped Time             Sys Name
CONTROLFILE HIGH    FINE     APR 02 12:00:00 Y    current.17006.843826701
ASMCMD [+RECO_DM01/APSPROD/CONTROLFILE] > cd +DATA_DM01
ASMCMD [+DATA_DM01] > cd EMERALD/CONTROLFILE
ASMCMD [+DATA_DM01/EMERALD/CONTROLFILE] > ls -l
Type         Redund Striped Time             Sys Name
                                               N    cntrl01.dbf => +DATA_DM01/APSPROD/CONTROLFILE/current.3678.843826699
                                               N    cntrl03.dbf => +DATA_DM01/APSPROD/CONTROLFILE/current.3679.843826701
ASMCMD [+DATA_DM01/EMERALD/CONTROLFILE] > cd +DATA_DM01/APSPROD/CONTROLFILE
ASMCMD [+DATA_DM01/APSPROD/CONTROLFILE] > ls -l
Type         Redund Striped Time             Sys Name
CONTROLFILE HIGH    FINE     APR 02 12:00:00 Y    current.3678.843826699
CONTROLFILE HIGH    FINE     APR 02 12:00:00 Y    current.3679.843826701
How can I ensure that every thing gets created in +DATA_DM01/EMERALD/ or [+RECO_DM01/EMERALD?? similary for datafile restore even I have used set new file name ASM fully quilified OMF datafile gets created under +DATA_DM01/APSPROD/
ASMCMD [+DATA_DM01/EMERALD/DATAFILE]
N    undots5_01.dbf => +DATA_DM01/APSPROD/DATAFILE/APPS_UNDOTS5.3669.843818269
Thanks
PV

Even If I explicitly say
rman target / nocatalog
RMAN> restore controlfile to '+DATA_DM01/emerald/controlfile/cntrl01.dbf' from '/dbfs_direct/FS1/RMAN_APSPROD/cf_APSPROD_i4p4b62m_1_1';
Starting restore at 02-APR-14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=64 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
Finished restore at 02-APR-14
It create as alias name +DATA_DM01/emerald/controlfile/cntrl01.dbf' pointing to +DATA_DM01/APSPROD/CONTROLFILE/
ASMCMD [+DATA_DM01/EMERALD/CONTROLFILE] > ls -l
Type         Redund Striped Time             Sys Name
                                               N    cntrl01.dbf => +DATA_DM01/APSPROD/CONTROLFILE/current.3679.843828927
ASMCMD [+DATA_DM01/EMERALD/CONTROLFILE] > cd +DATA_DM01/APSPROD
ASMCMD [+DATA_DM01/APSPROD] > cd CONTROLFILE
ASMCMD [+DATA_DM01/APSPROD/CONTROLFILE] > ls -l
Type         Redund Striped Time             Sys Name
CONTROLFILE HIGH    FINE     APR 02 12:00:00 Y    current.3679.843828927
ASMCMD [+DATA_DM01/APSPROD/CONTROLFILE] >

Restore 9i database from tape to 10g ASM

We have a plan to upgrade 9i database to 10g ASM. The current 9i database is using file systems on AIX5L. This is a VLDB of size >3TB. I want to restore production copy to test environment. There is no test environment for this database now. So, if I want to restore to test, we need 3TB for file systems and another 3TB for ASM disk groups for migration. Instead, Is there any way I can restore production Oracle 9i backup directly into Oracle 10g ASM disk groups. So that, we can save 3TB of space allocation for file systems. Also, it will save time instead restore 9i database to test, upgrade to 10g and then migrate to ASM.
I agree that this is the space to be allocated temporarily. But, as per our company standards, the project needs to procure temporary space too.

Boochi wrote:
We have a plan to upgrade 9i database to 10g ASM. The current 9i database is using file systems on AIX5L. This is a VLDB of size >3TB. I want to restore production copy to test environment. There is no test environment for this database now. So, if I want to restore to test, we need 3TB for file systems and another 3TB for ASM disk groups for migration. Instead, Is there any way I can restore production Oracle 9i backup directly into Oracle 10g ASM disk groups. So that, we can save 3TB of space allocation for file systems. Also, it will save time instead restore 9i database to test, upgrade to 10g and then migrate to ASM.
I agree that this is the space to be allocated temporarily. But, as per our company standards, the project needs to procure temporary space too.Hi Boochi,
You cannot restore a 9i RMAN backup into 10G.
You can use either export/import or transportable tablespace.
You can use below method:
1. Use transportable tablespace to migrate 9i to 10G.
2. Initially migrate all datafiles to filesystem.
3. Then migrate all datafiles to ASM.
Apart from this , you have one more option . upgrade existing 9i database to 10G and the use RMAN to restore it to 10G ASM database.
Regards
Rajesh

Restoring Database to ASM from tape

We're restoring a database from tape using Oracle 10.2.0.5. We explcitely specify the location for every single file with SET NEWNAME FOR DATAFILE X. The files that get restored don't match the NEWNAME format we set it to even though the log says it restored the file to that name. I don't know what's occuring under the hood of ASM, but it appears OMF is coming into play and generating names for the files. it's becoming a problem because when we restart the restore (which occurs often due to size of the database, length of time it takes, and drives going down) we start all over because RMAN doesn't know of the existing files. This doesn't seem to be normal behavior, and I know it's not like this during file based restores.
Does anyone know what's going on within ASM itself? It appears to be normal behavior when restoring to ASM and the names are later set appropriately after the SWITCH DATAFILE ALL. That's what I think would happen. It's currently a problem restarting restores.
Any insight or help is appreciated. Thank you

We're restoring a database from tape using Oracle 10.2.0.5. We explcitely specify the location for every single file with SET NEWNAME FOR DATAFILE X. The files that get restored don't match the NEWNAME format we set it to even though the log says it restored the file to that name. I don't know what's occuring under the hood of ASM, but it appears OMF is coming into play and generating names for the files. it's becoming a problem because when we restart the restore (which occurs often due to size of the database, length of time it takes, and drives going down) we start all over because RMAN doesn't know of the existing files. This doesn't seem to be normal behavior, and I know it's not like this during file based restores.
Does anyone know what's going on within ASM itself? It appears to be normal behavior when restoring to ASM and the names are later set appropriately after the SWITCH DATAFILE ALL. That's what I think would happen. It's currently a problem restarting restores.Have you enabled OMF? as db_create_file_dest = '+data'
then if you restore database from tape/disk, it will place all the datafiles as '+data/db_unique_name/datafiles';

Duplicating a database restored to disk instead of ASM

Hello, I have the primary database, a RAC and it has all the archivers on ASM. When I do a duplicate command, archivers are restored to $ORACLE_HOME/dbs
datafile 20 switched to datafile copy
input datafile copy RECID=26 STAMP=778627959 file name=+DGDATELO/elo_stby/datafile/pki_idx.270.778627255
datafile 21 switched to datafile copy
input datafile copy RECID=27 STAMP=778627959 file name=+DGDATELO/elo_stby/datafile/tnf_locanales.274.778626923
datafile 22 switched to datafile copy
input datafile copy RECID=28 STAMP=778627959 file name=+DGDATELO/elo_stby/datafile/idx1.271.778627219
datafile 23 switched to datafile copy
input datafile copy RECID=29 STAMP=778627959 file name=+DGDATELO/elo_stby/datafile/monitorizacion.313.778627547
datafile 24 switched to datafile copy
input datafile copy RECID=30 STAMP=778627959 file name=+DGDATELO/elo_stby/datafile/users.312.778627555
contents of Memory Script:
   set until scn 6561078671424;
   recover
   standby
   clone database
    delete archivelog
executing Memory Script
executing command: SET until clause
Starting recover at 22-MAR-12
starting media recovery
archived log for thread 1 with sequence 72 is already on disk as file /opt/oracle/soft/elo_stby/11.2.0/db_1/dbs/arch1_72_777745261.arc
archived log for thread 2 with sequence 70 is already on disk as file /opt/oracle/soft/elo_stby/11.2.0/db_1/dbs/arch2_70_777745261.arc
archived log file name=/opt/oracle/soft/elo_stby/11.2.0/db_1/dbs/arch1_72_777745261.arc thread=1 sequence=72
archived log file name=/opt/oracle/soft/elo_stby/11.2.0/db_1/dbs/arch2_70_777745261.arc thread=2 sequence=70
media recovery complete, elapsed time: 00:00:01
Finished recover at 22-MAR-12
Finished Duplicate Db at 22-MAR-12
released channel: prmy1
released channel: prmy2
released channel: prmy3
released channel: prmy4
released channel: stbyHow can I make them get restored to the FRA ASM?

This is the init used to mount the database, before the duplicate
ELO_2.__db_cache_size=1744830464
ELO_1.__db_cache_size=1795162112
ELO_2.__java_pool_size=16777216
ELO_1.__java_pool_size=16777216
ELO_2.__large_pool_size=16777216
ELO_1.__large_pool_size=16777216
ELO_1.__oracle_base='/opt/oracle/soft/elo_stby'#ORACLE_BASE set from environment
ELO_2.__oracle_base='/opt/oracle/soft/elo_stby'#ORACLE_BASE set from environment
ELO_2.__pga_aggregate_target=1728053248
ELO_1.__pga_aggregate_target=1728053248
ELO_2.__sga_target=2566914048
ELO_1.__sga_target=2566914048
ELO_2.__shared_io_pool_size=0
ELO_1.__shared_io_pool_size=0
ELO_2.__shared_pool_size=754974720
ELO_1.__shared_pool_size=704643072
ELO_2.__streams_pool_size=0
ELO_1.__streams_pool_size=0
*.audit_file_dest='/opt/oracle/soft/elo/admin/elo/adump'
*.audit_trail='db'
*.cluster_database=true
*.compatible='11.2.0.0.0'
*.control_files='+DGDATELO/elo_stby/controlfile/current.278.778408803','+DGFRAELO/elo_stby/controlfile/current.276.778408803'#Set by RMAN
*.db_block_size=8192
*.db_create_file_dest='+DGDATELO'
*.db_domain=''
*.db_name='elo'
*.db_recovery_file_dest='+DGFRAELO'
*.db_recovery_file_dest_size=48330964992
*.db_unique_name='ELO_STBY'#Is standby
*.diagnostic_dest='/opt/oracle/soft/elo'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=eloXDB)'
*.fal_server='ELO'#Is primary
*.log_archive_config='DG_CONFIG=(ELO,ELO_STBY)'
*.log_archive_dest_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ELO_STBY'
*.log_archive_dest_2='SERVICE=ELO ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=ELO'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='%t_%s_%r.arc'
*.log_archive_max_processes=30
*.memory_target=4294967296
*.open_cursors=1000
*.processes=1024
*.remote_listener='scan-cludbr02.ca.es:1556'
*.remote_login_passwordfile='exclusive'
*.standby_file_management='AUTO'

DR type restore of 10gR1 RAC with ASM database to another cluster

Hi,
We have a requirement to restore the image copy of our production database to another location. The production database is a 10-node 10gR1 RAC deployment with ASM. The image copy is in the FRA.
We want to restore this image copy onto a 2-node 10gR1 RAC cluster, which is also running a development environment. We have so far used the 'backup copy copy of database' command to pipe the image copy from the FRA to an NFS mounted filesystem. We plan to restore (and convert the names) the files from here. I have a list of steps we need to undertake - like adding the production database metadata on the development cluster into CRS, restore the spfile and controlfile, restore and convert the datafiles from the production ASM diskgroup to the development ASM diskgroup.
has anyone out there done this? Are there any nasty 'gotchas' or pitfalls?
Please, tell me your pain so I can spare it myself :o)
regards
Dilbert

user562223 wrote:
We are planning to take cold backup through RMAN. But now the issue is that if something going wrong with the storage then both the diskgroup on the same storage will not be mounted.
What should be the backup & recovery strategy for this scenario? How to bring the server back online?The strategy depends entirely on the risk analysis and assessment. Do you need to be able to recover the database to the moment just before it crashed? Do you need point-in-time recovery? What are the availability requirements? Etc.
Databases can be quite diverse in nature. It can be fairly static with very few changes, to very dynamic to totally dynamic. In some cases, the database only needs to be restored as a "container" (structures with no data) as that is all the processes need and as these will supply the data. In other cases, the entire database with all committed transactions to the second before the crash is needed. In a few cases, you may want to use Data Guard and standby/clone databases instead.
There is no single set of rman instructions that you can copy-and-paste to implement any of these diverse backup and recovery strategies. You need to determine and define your backup, restore and availability requirement first - before looking at which rman commands to use and in what sequence, where and when.

ASM restore

Similar Messages

Maybe you are looking for