9i RAC datafile restore
Hi,
In our 9i RAC production database one of the mount point crashed and we lost few datafiles. But we have a DR site with the same DBID and the DR is in sync with production, Can we use the datafile from DR and put it in the production and do recovery?
Thanks in advance.
Newbee
Do you have backup of the Prod database. If yes then you can use the backup to restore the datafile and do the recovery.
If using datafile from DR to restore the database is not tested, I will not use it in Production.
Regards
Similar Messages
-
Oracle 9i RAC datafile restore
Hi,
In our 9i RAC production database one of the mount point crashed and we lost few datafiles. But we have a DR site with the same DBID and the DR is in sync with production, Can we use the datafile from DR and put it in the production and do recovery?
Thanks in advance.If by DR you mean a physical standby database for production, yes you can. Just make sure all the redo and archive logs are accessible on the production DB.
-
Blockrecover but full datafile restore + ORA-01193
Hi,
We have a proplem, here is a short sescription:
We have corrupt blocks, how can we solve this problem? Blockrecover uses full datafile restore and finally fails with ORA-01193.
Here is a detailed description:
We have a 330GB datafile (bigfile tablespace) with 46 corrupt block.
DB version 10.2.0.4, Oracle linux, we use ASM.
We would repair these blocks.
V$DATABASE_BLOCK_CORRUPTION after "backup validate check logical datafile 7" :
FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTION_TYPE
7 16872378 1 0 FRACTURED
7 16872408 40 0 CORRUPT
7 16872379 5 0 CORRUPT
The result is similar by dbv.
We have archivelog mode and backupset created by rman command:
backup as compressed backupset incremental level 0 database;
All of the corrupted blocks are in 1 LOB segment.
We copied the LOB segment, only 5 record cannot be read.
The corrupted LOB segment (and table) was exchanged by the copied (not corrupted) data, so users can work.
We remained the corrupted LOB segment in the database, but it is not in use.
I started blockrecovery by command:
BLOCKRECOVER DATAFILE 7 BLOCK 16872378,...,16872447;
The listed blocks are same as in the V$DATABASE_BLOCK_CORRUPTION, so the command could be:
BLOCKRECOVER CORRUPTION LIST;
The database was opened during blockrecocer and the datafile 7 was online.
A line appeared in the V$SESSION_LONGOPS with:
"RMAN: full datafile restore"
The restore was more than 4 hours, and finally it is failed with error:
Starting blockrecover at 29-AUG-12
starting media recovery
ORA-01193 file % is not the same file seen at start of recovery
Based on V$SESSTAT there were lot of physical read but only some physical write.
Maybe full datafile read, and only corrupted blocks was changed, but I didn't check it exactly.
We retried blockrecover with only one block, but the result was same: it failed after 4 hours with ORA-01193.
We retried the blockrecovery on a mounted but not opened database, and the datafile was offline:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER DATABASE DATAFILE 7 offline
BLOCKRECOVER ...
The result was same: it failed after 4 hours with ORA-01193.
rman backup failed with error:
RMAN : ORA-19566: exceeded limit of 0 corrupt blocks for file %
After set maxcorrupt, rman backup ran successfuly
SET MAXCORRUPT FOR DATAFILE 7 TO 46;
Based on our current info, these workaround seems best for us:
- rman "set maxcorrupt"
- DB_BLOCK_CHECKING=FULL
- drop corrupted (but copied and not used segment)
- wait until corrupted blocks will be reallocated (checking it periodically by dbv)
- set maxcorrupt to 0
Our questions are:
*1. Why oracle uses "RMAN: full datafile restore" during blockrecover?*
Why needed to read the whole datafile?
One of the advantage of blockrecover should be the relative small IO, and fast restore.
I found only 2 results in google for "blockrecover" and "RMAN: full datafile restore".
(One of the findings was in this forum, but it was no answer for our problem)
*2. ORA-01193: file is not the same, but why?*
It is strange on opened database and online datafile, because other advantage of blockrecover should be the online recovery.
But it is more-more strange on closed(mounted) database and offline datafile. Only the rman blockrecover could change this file.
I found only 3 results in google for "blockrecover" "ORA-01193"
I found only the oerr output in google for "ORA-01193". But what does it mean? Only the rman blockrecover could change this file.
Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery.
Action: Ensure the correct file is available, then retry recovery.
*3. What else can be do to repair these corrupt blocks? What can we do for success blockrecover, or is there any other idea?*
Other infos:
- DB_BLOCK_CHECKING was false, but we changed it to FULL to avoid the subsequent corruptions
ALTER SYSTEM SET DB_BLOCK_CHECKING = FULL scope=both
- DBMS_REPAIR cannot detect the (out-of-line) LOB segment errors.
- rman SET MAXCORRUPT is not a "calming" solution
- When I read on internet, when we drop the corrupted LOB segments, the blocks will remains corrupt.
And the block will be repaired/formatted only when a new segment will allocate these blocks.
Based on metalink 336133.1, we can ensure the new allocation by fill the datafile with dummy data until the corrupted blocks will be allocated.
But this is a very IO intensive task.
- full recovery
very IO intensive, we try to avoid it.
Thx: lados.Hi,
other infos:
We use ASM, and one of the disk is dropped and added after the last full (incremental level 0) backup. Can this premise causes the slow restore (something physical storage info is changed), or the ORA-01193 error (file % is not the same file seen at start of recovery) ? I don't think that a full db backup is needed after ASM disk drop/add/rebalance. But we tried a full backup (this was when the corrupt block first appeared with ORA-19566).
I found only one finding in the metalink for ORA-01193. The oerr reference (cause,action). It would be strange, if nobady else had problem with this error.
Thx: lados. -
Hi folks,
I have some doubts about the PATH to disaster recovey with RAC and RMAN.
In this case I have just the RAC without data guard/streams, just only a single rac with two nodes.
The hypothetical scenario is:
One database using ASM (database name orcl) , two inatances in two separated servers (nodes serv1 and serv2) and two instances ( orcl1 and orcl1).
In this scenary I lost everything, and just keep the backups of: spfile, controlfile, database and archives.
So the steps to recovery is (using serv1):
1- Create the cluster (install clusteware, create CRS/Vdisk, create ASM instance)
2 - Just install the oracle files in all nodes serv1 and serv2, but don't create the instance orcl1 and orcl2.
3 - restore/recover spfile - rman
4 - restore/recover controlfile - rman
5 - restore/recover database with until clause - rman
After these steps the instance orcl1 will be restored by RMAN in the serv1 and the database orcl was created in the ASM.
But, please correct if I'm wrong, the instance and database will not be registered in CRS (RMAN not register the instance).
So I need to registry the instance and database with srvctl, doing:
1 - create PFILE in serv1 for orcl1 (that point to SPFILE in ASM) and ORAPWD file.
2 - add the database orcl to CRS
3 - add the instance orcl1 to CRS
4 - add the dependency about ASM and orcl1 from the node serv1 (using srvclt)
But after this I have the instance orcl2 in serv2 to create.
Just the instance, because the binaries already installed and the database was already created.
To complete I need to do the steps:
1 - Copy/Create PFILE for instance orcl2 in serv2
2 - add the instance orcl2 to CRS (using srvctl add instance)
3 - add the dependency about ASM instance (that exists in server2) and Instance orcl2 from the node serv2 (using srvctl)
4 - create PFILE and ORAPWD file.
The question is, RMAN will registry the instancie and database in CRS?
Another question, the RMAN will create PFILE and registry all instances of the original cluster?
I believe that not for two questions, correct?
Exists another path to restore/recover the RAC in this scenary?
The version in this case is 10Gr2 and 11Gr2.
Thanks.>
The hypothetical scenario is:
One database using ASM (database name orcl) , two inatances in two separated servers (nodes serv1 and serv2) and two instances ( orcl1 and orcl1).
In this scenary I lost everything, and just keep the backups of: spfile, controlfile, database and archives.
So the steps to recovery is (using serv1):
1- Create the cluster (install clusteware, create CRS/Vdisk, create ASM instance)
2 - Just install the oracle files in all nodes serv1 and serv2, but don't create the instance orcl1 and orcl2.
3 - restore/recover spfile - rman
4 - restore/recover controlfile - rman
5 - restore/recover database with until clause - rman
After these steps the instance orcl1 will be restored by RMAN in the serv1 and the database orcl was created in the ASM.
But, please correct if I'm wrong, the instance and database will not be registered in CRS (RMAN not register the instance).
So I need to registry the instance and database with srvctl, doing:
1 - create PFILE in serv1 for orcl1 (that point to SPFILE in ASM) and ORAPWD file.
2 - add the database orcl to CRS
3 - add the instance orcl1 to CRS
4 - add the dependency about ASM and orcl1 from the node serv1 (using srvclt)
But after this I have the instance orcl2 in serv2 to create.
Just the instance, because the binaries already installed and the database was already created.
To complete I need to do the steps:
1 - Copy/Create PFILE for instance orcl2 in serv2
2 - add the instance orcl2 to CRS (using srvctl add instance)
3 - add the dependency about ASM instance (that exists in server2) and Instance orcl2 from the node serv2 (using srvctl)
4 - create PFILE and ORAPWD file.
The question is, RMAN will registry the instancie and database in CRS?NO.. You will need the SRVCTL for registry services.
Another question, the RMAN will create PFILE and registry all instances of the original cluster?No... RMAN perform restore SPFILE only.
I believe that not for two questions, correct?
Correct.
Exists another path to restore/recover the RAC in this scenary?
The version in this case is 10Gr2 and 11Gr2.You can skip a few steps above by doing this:
After installing Oracle Clusterware / RAC
You will configure the network via NETCA.
You will create and configure ASM with DBCA.
To skip all the setup steps the Database (orcl) in Oracle Clusterware, you will create a database via DBCA with the same DB_NAME (orcl) of the database that will be restored.
The DBCA will configure the database with all the dependent services of the Clusterware including TNSNAMES.
Finished creating the database, all services should be configured, you will connect to ASM via asmcmd and drop (spfile, controlfile and datafiles), now just perform the restore (SPFILE,CONTROLFILE and DATAFILES) via rman. -
RMAN restore when system datafile get corrupt
Hi,
I am new to Backup and recovery, Can anybody suggest.
If my system datafile gets corrupt, do I need to restore and recover complete database or just datafile restore will be suffice.
In case the database is running on archive log mode.
Waiting for reply.
Thanks & Regards,
DeepakDeepak Pushkarna wrote:
Hi,
I am new to Backup and recovery, Can anybody suggest.
If my system datafile gets corrupt, do I need to restore and recover complete database or just datafile restore will be suffice.
In case the database is running on archive log mode.
Waiting for reply.
Thanks & Regards,
DeepakMount you database
restore tablespace system
recover tablespace system -
What advantages/disadv to having a none-rac db datafiles on rac clusterware
Hello,
We have a rac 10.2.0.3 with ocfs2 files on linux 4. We want to create a none-rac database on one of the rac nodes. The none-rac 10.2.0.4 is in its own new separate oracle home. Would it be a bad idea to use the existing ocfs2 mountpoints for the none-rac datafile locations? What would be adv/dis-adv to using ocfs2 for none-rac database files? Thank you.I will disagree of if a non-RAC database should use CFS or not. Since the file systems in use are clustered I see no reason to use a non-clustered file system and by using a CFS should the server the database is built on fail you can with a few minor edits start the database on the other node. If you used a traditional file system to hold the non-RAC database then its data files would not be accessible to the remaining node.
Placing the Oracle database on CFS then starting it from another node in the advent of failure is one of the early high availability (quick recovery) methods. This kind of set up was not uncommon in the VMS (DEC) world back in the late 1980's and early 1990's.
Also what if at a future data you determine you want to convert the database to RAC? It will be easier if the database is already on a CFS.
IMHO -- Mark D Powell -- -
Error during restore/recovery and 'open resetlogs'
Hello forum. I'm attempting to restore a database to a new host and have run into an error during the opening of the database (with resetlogs). The renaming of the datafiles, restore, switching of datafiles, and recovery are all done by an rman script, the contents of which are below:
# Restore production database to DR site using file system
# instead of ASM
run {
set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
restore database;
switch datafile all;
recover database;
I get the following output:
RMAN> @/home/oracle/scripts/rman_dr.rman
RMAN> # Restore production database to DR site using file system
2> # instead of ASM
3> #
4> run {
5> set newname for datafile 1 to '/opt/oracle/product/10gR2/oradata/DB01/system.dbf';
6> set newname for datafile 2 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf';
7> set newname for datafile 3 to '/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf';
8> set newname for datafile 4 to '/opt/oracle/product/10gR2/oradata/DB01/users.dbf';
9> set newname for datafile 5 to '/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf';
10> set newname for datafile 6 to '/opt/oracle/product/10gR2/oradata/DB01/file1.dbf';
11> set newname for datafile 7 to '/opt/oracle/product/10gR2/oradata/DB01/file2.dbf';
12>
13> restore database;
14> switch datafile all;
15> recover database;
16> }
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
Starting restore at 03-JAN-08
Starting implicit crosscheck backup at 03-JAN-08
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
Crosschecked 651 objects
Finished implicit crosscheck backup at 03-JAN-08
Starting implicit crosscheck copy at 03-JAN-08
using channel ORA_DISK_1
Crosschecked 1 objects
Finished implicit crosscheck copy at 03-JAN-08
searching for all files in the recovery area
cataloging files...
no files cataloged
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /opt/oracle/product/10gR2/oradata/DB01/system.dbf
restoring datafile 00002 to /opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
restoring datafile 00003 to /opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
restoring datafile 00004 to /opt/oracle/product/10gR2/oradata/DB01/users.dbf
restoring datafile 00005 to /opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
restoring datafile 00006 to /opt/oracle/product/10gR2/oradata/DB01/file1.dbf
restoring datafile 00007 to /opt/oracle/product/10gR2/oradata/DB01/file2.dbfchannel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus
channel ORA_DISK_1: restored backup piece 1
piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642899284.1.1.bus tag=20080101_LV0_DB
channel ORA_DISK_1: restore complete, elapsed time: 01:22:28
Finished restore at 03-JAN-08
datafile 1 switched to datafile copy
input datafile copy recid=14 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/system.dbf
datafile 2 switched to datafile copy
input datafile copy recid=15 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs1.dbf
datafile 3 switched to datafile copy
input datafile copy recid=16 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/sysaux.dbf
datafile 4 switched to datafile copy
input datafile copy recid=17 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/users.dbf
datafile 5 switched to datafile copy
input datafile copy recid=18 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/undotbs2.dbf
datafile 6 switched to datafile copy
input datafile copy recid=19 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file1.dbf
datafile 7 switched to datafile copy
input datafile copy recid=20 stamp=643049225 filename=/opt/oracle/product/10gR2/oradata/DB01/file2.dbf
Starting recover at 03-JAN-08
using channel ORA_DISK_1
starting media recovery
channel ORA_DISK_1: starting archive log restore to default destination
channel ORA_DISK_1: restoring archive log
archive log thread=2 sequence=1005
channel ORA_DISK_1: restoring archive log
archive log thread=1 sequence=1365
channel ORA_DISK_1: reading from backup piece /ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus
channel ORA_DISK_1: restored backup piece 1
piece handle=/ocfs2/remitpro/oracleBackups/tmp/rman_LV0_DB01.642900444.1.1.bus tag=20080101_LV0_DB
channel ORA_DISK_1: restore complete, elapsed time: 00:00:05
archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc thread=1 sequence=1365
archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_2_1005_3qtshncz_.arc thread=2 sequence=1005
channel default: deleting archive log(s)
archive log filename=/opt/oracle/product/10gR2/db/flash_recovery_area/DB01/archivelog/2008_01_03/o1_mf_1_1365_3qtshnfv_.arc recid=2418 stamp=643049236
unable to find archive log
archive log thread=1 sequence=1366
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/03/2008 16:47:22
RMAN-06054: media recovery requesting unknown log: thread 1 seq 1366 lowscn 181804603
RMAN> **end-of-file**
I searched for a decription of the 06054 error, and found that if the archive logs weren't available, then to run "alter database open resetlogs;", which I did. Here's the output:
RMAN> alter database open resetlogs;
database opened
RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
ORACLE error from target database:
ORA-06553: PLS-801: internal error [56319]
I've done all of this twice now, with the same result. I've googled PLS-801 and found more than a few instances of people getting this code, but not during a database open after a restore. Can anyone shed some light on what might have gone wrong? In the interest of brevity, I left out the rest of the restore process prior to running the database restore, but other than setting "compatible" and "db_recovery_file_dest_size", it was all by the book.
Thanks in advance.Thanks for the reply Pierre.
I am not using RMAN Duplicate. Yes, the source of the backup is an RAC. The destination is a single server, with the DB on the filesystem. Here's an overview of of the commands I ran and the procedure.
Copied tar'd backup controlfile and datafiles to destination machine. Untar'd. Install 10.2.0.1.0 on destination machine, patch to 10.2.0.2.0.
OS> sqlplus /nologin
SQL> alter system set compatible = '10.2.0.2.0' scope=spfile;
SQL> alter system set db_recovery_dest_file_size = '8g'; scope spfile;
SQL> shutdown immediate;
SQL> startup; (to verify changes took...)
SQL> shutdown immediate;
OS> Copy control file from untar'd dir and place in $ORACLE_HOME/dbs/, truncate name to c-DBID-date-00.
OS> rman target /
RMAN> startup nomount;
RMAN> set dbid <dbid from control file>;
RMAN> restore controlfile from autobackup; (finds control file with no problem...)
RMAN> alter database mount;
RMAN> @/home/oracle/rman_dr.rman (script cited in first post, to rename datafiles from ASM to filesystem, restore, switch files, and recover...)
RMAN> alter database open resetlogs; (as cited before...)
If I'm not using Duplicate and not specifying dates, the UNTIL/SET UNTIL commands aren't necessary, correct? -
Restore using TSPITR Results Dead lock error
This is the step is followed but i am getting deadlock error .please give your valuable suggestion .
Product Used:oracle 11g in linux environmnet
1)Before taking backup get SCN number for restore.
Command applied: Select current_scn from v$database;
2)running Full backup of database
Command applied:
configure controlfile autobackup on;
backup database;
CROSSCHECK BACKUP;
exit;
3)Running level 0 incremental backup
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 TAG ='WEEKLY' TABLESPACE TEST;
exit;
3) Running level 1 incremental backup
Command applied:
BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 TAG ='DAILY' TABLESPACE TEST;
4)Before Restore(TSPITR) following procedure are applied under sysdba privilege
Command applied:
SQL 'exec dbms_backup_restore.manageauxinstance ('TSPITR',1)';
5)TSPITR Restore command
Command applied:
run
SQL 'ALTER TABLESPACE TEST OFFLINE'
RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
SQL 'ALTER TABLESPACE TEST ONLINE';
and i tried with this option also(the same error i was getting)
Command applied:
run
SQL 'ALTER TABLESPACE TEST OFFLINE';
SET UNTIL SCN 1912813;
RESTORE TABLESPACE TEST ;
RECOVER TABLESPACE TEST UNTIL SCN 1912813 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
SQL 'ALTER TABLESPACE TEST ONLINE';
The follwing error i get for above mentioned restore command
Recovery Manager: Release 11.2.0.1.0 - Production on Tue Aug 17 18:11:18 2010
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: NEW10 (DBID=2860680927)
RMAN> run
2> {
3> SQL 'ALTER TABLESPACE TEST OFFLINE';
4> RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
5> SQL 'ALTER TABLESPACE TEST ONLINE';
6> }
7>
using target database control file instead of recovery catalog
sql statement: ALTER TABLESPACE TEST OFFLINE
Starting recover at 17-AUG-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=404 device type=DISK
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS1
Creating automatic instance, with SID='BkAq'
initialization parameters used for automatic instance:
db_name=NEW10
db_unique_name=BkAq_tspitr_NEW10
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/opt/oracle/base/flash_recovery_area
log_archive_dest_1='location=/opt/oracle/base/flash_recovery_area'
#No auxiliary parameter file used
starting up automatic instance NEW10
Oracle instance started
Total System Global Area 292933632 bytes
Fixed Size 1336092 bytes
Variable Size 100666596 bytes
Database Buffers 184549376 bytes
Redo Buffers 6381568 bytes
Automatic instance created
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully
contents of Memory Script:
# set requested point in time
set until scn 1791053;
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 17-AUG-10
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=59 device type=DISK
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 /opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp tag=TAG20100817T142607
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl
Finished restore at 17-AUG-10
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until scn 1791053;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 8 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 2 to new;
set newname for clone datafile 9 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 7 to
"/opt/oracle/base/oradata/NEW10/test01.dbf";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 8, 3, 2, 9, 7;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
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
renamed tempfile 1 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 17-AUG-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00008 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00009 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp tag=TAG20100817T140128
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:02:45
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00007 to /opt/oracle/base/oradata/NEW10/test01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp tag=WEEKLY
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:06:55
Finished restore at 17-AUG-10
datafile 1 switched to datafile copy
input datafile copy RECID=6 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf
datafile 8 switched to datafile copy
input datafile copy RECID=7 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=8 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=9 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf
datafile 9 switched to datafile copy
input datafile copy RECID=10 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf
contents of Memory Script:
# set requested point in time
set until scn 1791053;
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 8 online";
sql clone "alter database datafile 3 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 9 online";
sql clone "alter database datafile 7 online";
# recover and open resetlogs
recover clone database tablespace "TEST", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 8 online
sql statement: alter database datafile 3 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 9 online
sql statement: alter database datafile 7 online
Starting recover at 17-AUG-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00007: /opt/oracle/base/oradata/NEW10/test01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp
channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp tag=DAILY
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
starting media recovery
archived log for thread 1 with sequence 39 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc
archived log for thread 1 with sequence 40 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc
archived log for thread 1 with sequence 41 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc
archived log for thread 1 with sequence 42 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc
archived log for thread 1 with sequence 43 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc thread=1 sequence=39
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc thread=1 sequence=40
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc thread=1 sequence=41
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc thread=1 sequence=42
archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc thread=1 sequence=43
media recovery complete, elapsed time: 00:00:50
Finished recover at 17-AUG-10
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace TEST read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/opt/oracle/base/flash_recovery_area''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/opt/oracle/base/flash_recovery_area''";
executing Memory Script
sql statement: alter tablespace TEST read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
Performing export of metadata...
EXPDP> Starting "SYS"."TSPITR_EXP_BkAq":
EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
EXPDP> Processing object type TRANSPORTABLE_EXPORT/GRANT/OWNER_GRANT/OBJECT_GRANT
EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX
EXPDP> Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TRIGGER
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
EXPDP> Master table "SYS"."TSPITR_EXP_BkAq" successfully loaded/unloaded
EXPDP> ******************************************************************************
EXPDP> Dump file set for SYS.TSPITR_EXP_BkAq is:
EXPDP> /opt/oracle/base/flash_recovery_area/tspitr_BkAq_82690.dmp
EXPDP> ******************************************************************************
EXPDP> Datafiles required for transportable tablespace TEST:
EXPDP> /opt/oracle/base/oradata/NEW10/test01.dbf
EXPDP> Job "SYS"."TSPITR_EXP_BkAq" successfully completed at 18:25:02
Export completed
contents of Memory Script:
# shutdown clone before import
shutdown clone immediate
# drop target tablespaces before importing them back
sql 'drop tablespace TEST including contents keep datafiles';
executing Memory Script
database closed
database dismounted
Oracle instance shut down
sql statement: drop tablespace TEST including contents keep datafiles
Removing automatic instance
shutting down automatic instance
target database instance not started
Automatic instance removed
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_66o1k480_.tmp deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_3_66o1k0mg_.log deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_2_66o1jyt4_.log deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_1_66o1jx3w_.log deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf deleted
auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/17/2010 18:25:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on default channel at 08/17/2010 18:25:25
RMAN-11003: failure during parse/execution of SQL statement: drop tablespace TEST including contents keep datafiles
ORA-00604: error occurred at recursive SQL level 1
ORA-00060: deadlock detected while waiting for resource
Recovery Manager complete.
please give your valuable suggestion .It should be more helpful for us.
Edited by: user10750009 on Aug 20, 2010 1:07 AM
Edited by: user10750009 on Aug 20, 2010 1:15 AMI want TSPITR ,during this operation i faced this deadlock error.
Before that we faced roll backsegment error for that we applied follwing workaround .
If i applied follwing workaround before every backup and restore .i didn't get any error .all things went successful.
spool /tmp/Createtest.log
connect / as sysdba
REM Perform startup in case we are still down
ALTER SYSTEM SET PROCESSES=500 SCOPE=SPFILE;
SHUT IMMEDIATE;
STARTUP MOUNT EXCLUSIVE;
ALTER DATABASE ARCHIVELOG;
ARCHIVE LOG START;
ALTER DATABASE OPEN;
connECT / as sysdba;
alter system set undo_management = MANUAL scope=spfile;
shutdown immediate;
startup;
Connect / as sysdba;
DROP TABLE TEST123;
create table test123 (t1 number, t2 varchar2(10));
begin
for i in 1.. 300000 loop
insert into test values (i,'AAAAAAAAAA');
end loop;
end;
delete test123;
commit;
alter system set undo_management = auto scope=spfile;
shutdown immediate ;
startup ;
The above workaround we applied before creating tablespace and datafile ,after that we face some dead lock error while restore TSPITR .Did you need any more information
Edited by: user10750009 on Aug 20, 2010 1:12 AM -
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
PVEven 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] > -
Unable to restore TABLESPACE using RMAN backups
Hi,
I am not able to restore tablespace using RMAN (TSPITR).
I have full backup of database,
While try to restore it's failed.
RMAN> recover tablespace TEST1 until logseq 706 auxiliary destination '/tmp';
Starting recover at 16-OCT-13
using channel ORA_DISK_1
RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
List of tablespaces expected to have UNDO segments
Tablespace SYSTEM
Tablespace UNDOTBS2
Creating automatic instance, with SID='CsFz'
initialization parameters used for automatic instance:
db_name=TRAINEE
db_unique_name=CsFz_tspitr_TRAINEE
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=/tmp
log_archive_dest_1='location=/tmp'
#No auxiliary parameter file used
starting up automatic instance TRAINEE
Oracle instance started
Total System Global Area 292933632 bytes
Fixed Size 1336092 bytes
Variable Size 100666596 bytes
Database Buffers 184549376 bytes
Redo Buffers 6381568 bytes
Automatic instance created
List of tablespaces that have been dropped from the target database:
Tablespace TEST1
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
executing Memory Script
executing command: SET until clause
Starting restore at 16-OCT-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=81 device type=DISK
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 /oracle/product/11.2.0/dbhome_1/dbs/c-332232391-20131016-09
channel ORA_AUX_DISK_1: piece handle=/oracle/product/11.2.0/dbhome_1/dbs/c-332232391-20131016-09 tag=TAG20131016T144951
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/tmp/TRAINEE/controlfile/o1_mf_95wbkpvj_.ctl
Finished restore at 16-OCT-13
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 7 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 6 to
"/oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 7, 2, 6;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to /tmp/TRAINEE/datafile/o1_mf_temp_%u_.tmp in control file
Starting restore at 16-OCT-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /tmp/TRAINEE/datafile/o1_mf_system_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00007 to /tmp/TRAINEE/datafile/o1_mf_undotbs2_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00002 to /tmp/TRAINEE/datafile/o1_mf_sysaux_%u_.dbf
channel ORA_AUX_DISK_1: restoring datafile 00006 to /oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf
channel ORA_AUX_DISK_1: reading from backup piece /tmp/1iomi9rv_1_1
channel ORA_AUX_DISK_1: piece handle=/tmp/1iomi9rv_1_1 tag=TAG20131016T144935
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:15
Finished restore at 16-OCT-13
datafile 1 switched to datafile copy
input datafile copy RECID=11 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_system_95wbkybb_.dbf
datafile 7 switched to datafile copy
input datafile copy RECID=12 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_undotbs2_95wbkycy_.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=13 STAMP=828975325 file name=/tmp/TRAINEE/datafile/o1_mf_sysaux_95wbkybz_.dbf
contents of Memory Script:
# set requested point in time
set until logseq 706 thread 1;
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 7 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 6 online";
# recover and open resetlogs
recover clone database tablespace "TEST1", "SYSTEM", "UNDOTBS2", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 7 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 6 online
Starting recover at 16-OCT-13
using channel ORA_AUX_DISK_1
starting media recovery
archived log for thread 1 with sequence 702 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_702_807275402.dbf
archived log for thread 1 with sequence 703 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_703_807275402.dbf
archived log for thread 1 with sequence 704 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_704_807275402.dbf
archived log for thread 1 with sequence 705 is already on disk as file /oracle/product/11.2.0/dbhome_1/dbs/arch1_705_807275402.dbf
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_702_807275402.dbf thread=1 sequence=702
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_703_807275402.dbf thread=1 sequence=703
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_704_807275402.dbf thread=1 sequence=704
archived log file name=/oracle/product/11.2.0/dbhome_1/dbs/arch1_705_807275402.dbf thread=1 sequence=705
media recovery complete, elapsed time: 00:00:01
Finished recover at 16-OCT-13
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace TEST1 read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/tmp''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
/tmp''";
executing Memory Script
sql statement: alter tablespace TEST1 read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/tmp''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/tmp''
Performing export of metadata...
EXPDP> Starting "SYS"."TSPITR_EXP_CsFz":
EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
EXPDP> Master table "SYS"."TSPITR_EXP_CsFz" successfully loaded/unloaded
EXPDP> ******************************************************************************
EXPDP> Dump file set for SYS.TSPITR_EXP_CsFz is:
EXPDP> /tmp/tspitr_CsFz_17454.dmp
EXPDP> ******************************************************************************
EXPDP> Datafiles required for transportable tablespace TEST1:
EXPDP> /tmp/TRAINEE/datafile/o1_mf_test1_95wbkyck_.dbf
EXPDP> Job "SYS"."TSPITR_EXP_CsFz" successfully completed at 14:56:02
Export completed
contents of Memory Script:
# shutdown clone before import
shutdown clone immediate
executing Memory Script
database closed
database dismounted
Oracle instance shut down
Performing import of metadata...
IMPDP> Master table "SYS"."TSPITR_IMP_CsFz" successfully loaded/unloaded
IMPDP> Starting "SYS"."TSPITR_IMP_CsFz":
IMPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Removing automatic instance
Automatic instance removed
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_temp_95wblk08_.tmp deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_3_95wblj14_.log deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_2_95wblhn8_.log deleted
auxiliary instance file /tmp/TRAINEE/onlinelog/o1_mf_1_95wblh8q_.log deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_sysaux_95wbkybz_.dbf deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_undotbs2_95wbkycy_.dbf deleted
auxiliary instance file /tmp/TRAINEE/datafile/o1_mf_system_95wbkybb_.dbf deleted
auxiliary instance file /tmp/TRAINEE/controlfile/o1_mf_95wbkpvj_.ctl deleted
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 10/16/2013 14:56:16
RMAN-06963: Error received during import of metadata
RMAN-06961: IMPDP> ORA-39123: Data Pump transportable tablespace job aborted
ORA-01565: error in identifying file '/oracle/oradata/TRAINEE/datafile/o1_mf_test1_95w9fln9_.dbf'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3Hi,
Cloud you please cheek below link:
ORACLE Cookies: TSPITR to recover a dropped tablespace
Thank you -
PRCR-1079 Failed to start resource ora.rac.db - during installation
Hi
After successful installation of Grid Infrasturcture I proceeded with database installation on clusterware and at the stage when the installer was creating clone database I got the following errors ( this was my 2nd attempt and I got the same errors both the time ) :
Errors:
PRCR-1079 : Failed to start resource ora.rac.db
ORA-01092 : ORACLE instance terminated. Disconnection forced
ORA-00704 : bootstrap process failure
ORA-00604 : error occurred at resursiive SQL level 2
ORA-01578 : ORACLE data block corrupted (file # 1, block # 5505)
ORA-01110 : data file 1:'+DATA/rac/datafile/system.256.799676855'
Process ID : 23498
Session ID : 63 Serial number 3
CRS-2674 Start of 'ora.rac.db' on 'rac2' failed
CRS-2632 There are no more servers to try to place resource 'ora.rac.db' on that would satisfy its placement policy
There are no logs on that node (rac2)
I am running Oracle Linux 5.4 64 bit
As mentioned above this was my 2nd attempt afresh and I got the same errors both the times, please let me know what is the problem as the rac2 is replica of rac2 in VMWare.
Thanks for your help
Rgds
THi
I tried again for the 3rd time and go the same error again, this time I rebuilt the node 2 - Can someone ple ase help me with this issue why it keeps failing on node 2 at the same stage for the 2rd time in a row.
Also please help me clone the database manually from node 1 to node 2 so I don't have to try to reinstall it again, there must be ways to do it
Thanks for your help in advance
Rgds
T -
To monitorize RMAN restore progress. Very Urgent!!
Hi.
I´m doing a full database restore with RMAN and I need to know the progress of this operation.
Can anybody help me please, is very urgent
Thanks everybodyOk, I´ve skipped the WHERE clause and it likes work...
select sid, serial#, sofar, totalwork, opname, round(sofar/totalwork*100, 2) " % Complete" from v$session_longops;
SID SERIAL# SOFAR TOTALWORK
OPNAME % Complete
9 101 3374079 7774720
RMAN: aggregate input 43,4
11 13 3409663 7774720
RMAN: full datafile restore 43,86
Thanks -
Restore controlfile without RMAN Command
Hii..!! RMAN Experts ..
I have a RMAN Backup of my production database , Accidentally controlfile, datafiles, and redolog filies are lost .
Important thing is : I want to Restore Controlfile Without RMAN Commands ...
Is this possible,? If Yes How ??
Please get me out of this Doubt., & provide me detail steps
Will be very much thankful to you...937382 wrote:
Hii..!! RMAN Experts ..
I have a RMAN Backup of my production database , Accidentally controlfile, datafiles, and redolog filies are lost .
Important thing is : I want to Restore Controlfile Without RMAN Commands ...
Is this possible,? If Yes How ??
Please get me out of this Doubt., & provide me detail steps
Will be very much thankful to you...In an emergency situation, you can try using the SNAPSHOT CONTROLFILE.
Oracle is very clear on this point and says that this file should not be used for any purpose, but breaking this rule, we can have success and bring a consistent controlfile.
The snapshot control file is a copy of a database control file created in an operating system-specific location by RMAN. RMAN creates the snapshot control file so that it has a consistent version of a control file to use when either resynchronizing the recovery catalog or backing up the control file.
The Default Location of SNAPSHOT CONTROLFILE is $ORACLE_HOME/dbs/snapcf_<DB_NAME>.f
If we recently used RMAN most recent controlfile will be my SNAPSHOT CONTROLFILE.
See this example:
SQL> create pfile='/home/oracle/spfile.txt' from spfile;
SQL> !
oracle@aix:/home/oracle> cp /u01/app/oracle/product/11.2.0/dbhome_11203/dbs/snapcf_dbtst.f /home/oracle/control.ora
oracle@aix:/home/oracle> vi spfile.txt
"spfile.txt" 27 lines, 957 characters
*.control_files='/home/oracle/control.ora' ## Change this line
SQL> startup mount pfile ='/home/oracle/spfile.txt'
ORACLE instance started.
Total System Global Area 768294912 bytes
Fixed Size 2225448 bytes
Variable Size 293604056 bytes
Database Buffers 465567744 bytes
Redo Buffers 6897664 bytes
Database mounted.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
### We can open reseting log if you have all datafiles restored.
### Or you can use RMAN command to restore your database from Controlfile Catalog.
### Also you can generate a command to create a new controlfile
SQL> alter database backup controlfile to trace;Regards,
Levi Pereira -
Restore Backup log file back SID .log and be*****.ant
Dear all,
I have to restore sap oracle online backup from source server to target server. We have taken the backup of source server on tape. Now we have to restore that tape backup on target server. We don't have back<SID>.log and be*****.ant with us.
How can we restore the back<SID>.log and be****.ant tape first by which we can start the restore online backup on target server or without this back<SID>.log and be****.ant can we restore the backup on other location ( which i tried but not working, it is asking for back<SID>.log file.
Thanks
WardHi Ward,
As long as you have complete oracle datafiles, restore without logfiles can be done.
1. As a precauition, copy all /oracle/<SID> to a safe place during offline state (SAP down, Oracle down)
2. Replace each datafile from tape to the current datafile location. e.g /tape/sr3.data1 -> /oracle/<SID>/sapdata1/sr3_1/sr3.data1
3. Make sure that archive logs is complete from the point where you start online backup.
4. sqlplus /nolog
5. startup mount
6. You will likely found error with controlfile. Replace all oracle controlfiles from tape backup, then repeat the startup
7. recover database until cancel using backup controlfile
8. choose the archive where you want the point of restore
Good luck -
Step By step guide to recover lost datafiles from RMAN
Hi All
I am new to RMAN recovery.
I tried searching internet but I cannot find the detail steps for "How to restore datafile using RMAN when we have backup on tape and How to then apply archive logs" .
Can anyone please explain the steps .
I will really appreciate that.
ThanksThanks All I really appreciate your help :)
So as far as I understand here is my scenario and here are the steps I will follow please correct me if I am wrong.
I have last night backup of all datafiles and archivelog files on tape.
I lost one of datafile in morning.
Here are the steps I will perform to recover datafile
Restore the backup(including archive files) from tape to OS directory.
Mount the database
RMAN> run{
restore datafile 6;
RMAN > recover datafile 6;
RMAN> alter database open;
The RMAN will apply all the archivelog file and datafile will be available again.
I also have some additional question:
1) do I have to take datafile offline?
2) are these steps same for tablespace restore ? Do i have to take tablespace offline?
3) How will I confirm if all the archivelogs were applied to data file and data is upto date?
Thanks
Maybe you are looking for
-
Unable to generate printed documentation
I am running RoboHelp 9 HTML using Microsoft Word 2010 on a Windows 7 machine. Whenever I try to generate printed documentation using a single source layout that is set up for generating either a .docx file or a .doc file the program hangs up after p
-
Error during PO creation "Total BED % rate exceeds 100 % "
Hi. Its concerned to Indian Excice. Error during the creation of PO is " Total BED % rate exceeds 100 % " , ( Message no. 8I453). And you pls note in J1ID its 16% maintained for that perticular chapter id and its 100% for BED in tax code. Can you pls
-
I had this problem with Google Chrome and had to uninstall it completely. The problem occurred even if Chrome wasn't running.
-
Dicount condition multiplies with quantity in sales bom(quotation)
hi, i am trying to create a quotation for a sales bom(va21) while i give condition type rb00(discount value) as a header condition (eg.rs 50) it multiplies with no of line items(eg. 10 line items) in the sales bom and gives and shows my discount
-
Block AOL messages from 246-246
Early this morning for the first time ever I received text messages multiple times from AOL AIM. I do not subscribe to AOL and wish to BLOCK ALL TEXT MESSAGES other than those from people to whom I've given my 10-digit cellphone number. The SPAM mess