RMAN recovery

Hi all

As part of the migration from 32-bit to 64-bit process, I need to take the datafile level backup of the database in different file systems located on the server because of space issues. In the target server also, I need to keep the backup sets for different file for rman restore and recovery systems.

Can someone give me the steps for this or any document?

Database version: 10.2.0.3
Source OS: Linux 32 bit

Target OS: Linux 64-bit

If you have a complicated structure, you can use the VALUE of NEWNAME to specify a new name for each data file.

The BackupSets may be in a different location. You can use CATALOGUE START WITH to update the controlfile with information on the new location.

Hemant K Collette

Tags: Database

Similar Questions

Location of RMAN recovery

Hi all;

Try to learn the concepts of rman recovery.

RMAN > backup the database archivelog;

From backup 30 July 14
Current archived log
using channel ORA_DISK_1
channel ORA_DISK_1: from archive newspaper backupset
channel ORA_DISK_1: specification of archive log backup set
archive log entry thread = 1 sequence 2 recid = 74 = 854312620 stamp =
channel ORA_DISK_1: starting total, 1 to July 30, 14
channel ORA_DISK_1: finished piece 1 to July 30, 14
piece handle=/u01/app/oracle/flash_recovery_area/TEST/backupset/2014_07_30/o1_mf_annnn_TAG20140730T210340_9xl42oq6_.bkp tag = TAG20140730T210340 comment = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:02
Backup finished at 30 July 14
From backup 30 July 14
using channel ORA_DISK_1
channel ORA_DISK_1: from full datafile backupset
channel ORA_DISK_1: specifying datafile (s) in backupset
input datafile fno = 00001 name=/u01/app/oracle/oradata/test/system01.dbf
input datafile fno = name=/u01/app/oracle/oradata/test/undotbs01.dbf 00002
input datafile fno = name=/u01/app/oracle/oradata/test/sysaux01.dbf 00003
input datafile fno = name=/u01/app/oracle/oradata/test/users01.dbf 00004
input datafile fno = 00005 name=/u01/app/oracle/oradata/test/example01.dbf
input datafile fno = name=/u01/app/oracle/oradata/test/users02.dbf 00006
input datafile fno = name=/u01/app/oracle/oradata/test/test01.dbf 00007
channel ORA_DISK_1: starting total, 1 to July 30, 14
channel ORA_DISK_1: finished piece 1 to July 30, 14
piece handle=/u01/app/oracle/flash_recovery_area/TEST/backupset/2014_07_30/o1_mf_nnndf_TAG20140730T210342_9xl42s7o_.bkp tag = TAG20140730T210342 comment = NONE
channel ORA_DISK_1: complete set of backups, time: 00:02:16
channel ORA_DISK_1: from full datafile backupset
channel ORA_DISK_1: specifying datafile (s) in backupset
including the current control in backupset file
including current SPFILE in backupset
channel ORA_DISK_1: starting total, 1 to July 30, 14
channel ORA_DISK_1: finished piece 1 to July 30, 14
piece handle=/u01/app/oracle/flash_recovery_area/TEST/backupset/2014_07_30/o1_mf_ncsnf_TAG20140730T210342_9xl4702t_.bkp tag = TAG20140730T210342 comment = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:02
Backup finished at 30 July 14
SQL > conn / as sysdba
Connected.
SQL > archive logs list;
Database log mode Archive Mode
Active AutoArchive
Destination of archive USE_DB_RECOVERY_FILE_DEST
More old sequence of journal online 2
Log sequence archive 4
Current log sequence 4

SQL > conn gts/gts
Connected.

SQL > create table tab1 (identification number, name varchar2 (15));
Table created.
SQL > insert into tab1 values (1, "sona");
1 line of creation.
SQL > commit;
Validation complete.
SQL > update tab1 set name = "S/n";
1 line update.
SQL > select * v log$;
GROUP # THREAD # SEQUENCE # MEMBERS OF ARC STATUS FIRS BYTES
---------- ---------- ---------- ---------- ---------- --- ---------------- ----
1 1 4 52428800 1 NO CURRENT 30 - J
2 1 2 52428800 1 INACTIVE YES 30-J
3 1 3 52428800 1 ACTIVE YES 30-J
$ rm - rf redo0 *.

$ ls-l again *.
LS: do it again *: no such file or directory
SQL > insert into tab1 values (2, 'sona');
1 line of creation.
SQL > insert into tab1 values (3, 'sona');
1 line of creation.
SQL > commit;
Validation complete.
SQL > startup strength;
ORACLE instance started.
Total System Global Area 465567744 bytes
Bytes of size 1220024 fixed
96469576 variable size bytes
364904448 of database buffers bytes
Redo buffers 2973696 bytes
Mounted database.
ORA-00313: open failed for the members of the group log 1 of thread 1
ORA-00312: thread 1 1 online journal: ' / u01/app/oracle/oradata/test/redo01.log'
ORA-27037: unable to get file status
Linux error: 2: no such file or directory
Additional information: 3
rman target $ /.
Recovery Manager: Release 10.2.0.1.0 - Production Wed Jul 30 21:13:47 2014
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: TEST (DBID = 2152371022, is not open)
RMAN > run
2 > {}
3 > set until sequence 4.
4 > restore database;
5 > restore database;
6 > sql ' alter database open resetlogs;
{7 >}
executing command: SET until clause
using the control file of the target instead of recovery catalog database
From pick up to 30 July 14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 156 devtype = DISK
starting media recovery
Oracle error:
ORA-01547: WARNING: RECOVER succeeded but OPEN RESETLOGS would get below error
ORA-01194: file 1 needs a recovery more match
ORA-01110: data file 1: ' / u01/app/oracle/oradata/test/system01.dbf'
media recovery complete, duration: 00:00:02
Finish to recover 30 July 14
From restoration to July 30, 14
using channel ORA_DISK_1
channel ORA_DISK_1: from datafile backupset restoration
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
restoring datafile 00001 to /u01/app/oracle/oradata/test/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/test/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/test/sysaux01.dbf
restoring datafile 00004 in /u01/app/oracle/oradata/test/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/test/example01.dbf
restoring datafile to /u01/app/oracle/oradata/test/users02.dbf 00006
restoring datafile 00007 to /u01/app/oracle/oradata/test/test01.dbf
channel ORA_DISK_1: backup /u01/app/oracle/flash_recovery_area/TEST/backupset/2014_07_30/o1_mf_nnndf_TAG20140730T210342_9xl42s7o_.bkp piece reading
channel ORA_DISK_1: restored the backup part 1
piece handle=/u01/app/oracle/flash_recovery_area/TEST/backupset/2014_07_30/o1_mf_nnndf_TAG20140730T210342_9xl42s7o_.bkp tag = TAG20140730T210342
channel ORA_DISK_1: restore complete, duration: 00:01:37
Restoration finished in 30 July 14
SQL statement: alter database open resetlogs
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03009: failure of the sql command to the default channel on 30/07/2014-21:16:16
RMAN-11003: failure in parsing / execution of the SQL statement: alter database open resetlogs
ORA-01152: 1 no file has been restored from a sufficiently old backup
ORA-01110: data file 1: ' / u01/app/oracle/oradata/test/system01.dbf'
RMAN > exit
SQL > startup strength;
ORACLE instance started.
Total System Global Area 465567744 bytes
Bytes of size 1220024 fixed
96469576 variable size bytes
364904448 of database buffers bytes
Redo buffers 2973696 bytes
Mounted database.
ORA-01589: must use RESETLOGS or NORESETLOGS option of database open
SQL > alter database open resetlogs;
ALTER database open resetlogs
*
ERROR on line 1:
ORA-01152: 1 no file has been restored from a sufficiently old backup
ORA-01110: data file 1: ' / u01/app/oracle/oradata/test/system01.dbf'

Why do you get BACK them before the RESTORATION?

RMAN > run

2 > {}

3 > up to sequence 4.

4 > restore database;

5 > restore database;

6 > sql ' alter database open resetlogs;

{7 >}

To try:

RMAN > run

2 > {}

3 > up to sequence 4.

4 > restore database ;

5 > restore database ;

6 > sql ' alter database open resetlogs;

{7 >}

RMAN recovery failure
Expensive of DBA,.

I tried a RMAN recovery... to form a 64-bit server to a 32-bit server 10.2.0.4 10.2.0.3.

After the recoverey DB won't start... I had a lot of posts like this: ORA-06553: PLS-801: Internet Fehler [56319]...

After that, I let start the database in upgrade mode and allow to run the following scripts:

@?\rdbms\admin\utlirp.sql

@?\rdbms\admin\catproc.sql

@?\rdbms\admin\catalog.sql

@?\rdbms\admin\utlrp.sql

After that, everything works fine in 32-bit...

My question is:

It's OK to let flow catproc.sql and catalog.sql again?
Or is it wrong?
What it means exactly by an existing database?

Thanks for all replies!

BR
Herrmann
The easiest way would be wanted to get an export of the database and then import it on the new host. Other than that, you can migrate your db to the 32-bit version and can then move it to the new host. For error, a quick Google search gave this
ORA-06553: PLS-801: internal error [56319]

Try it and post your comments.

HTH
Aman...

the recovered data is only a row during rman recovery Camille
I tried a point in time for recovery in RMAN, but the table I got contains only 1 row which is supposed to be 2 rows.

Here's what I did:

1 create the table
2 validation;
3 insert the value 1 in the table
4 validation;
5. Insert the value 2 in the table
6 validation;
7 remove the table
8 validation;
9 get sysdate July 28, 2010 07:01
10 make a rman recovery and apply the sysdate recovered, but use on July 28, 2010, 07:0 * 0 *: 00
11. check the table and found that 1 row only recovered.
You can use logminer, because no back in 8i

RMAN recovery failed with the incarnation of target of error 03002,11003 and recovery 19906 changed during recovery

Hi all
I was cloning a Prod DB (Oracle 10.2.0.5) from tape backup. So the cloning is going on it failed with the below error in RMAN:
archive log thread = 2 sequence 23044 = filename=+DG_zeus_FRA_01/zeus/archivelog/2014_05_23/thread_2_seq_23044.3558.848348137
output channel: ch01
output channel: ch02
output channel: ch03
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of Db in dual at 23/05/2014 20:15:48
RMAN-03015: an error has occurred in the script stored memory Script
ORA-00283: cool cancelled due to errors
RMAN-11003: failure in parsing / execution of the SQL statement: alter database recover logfile ' +DG_zeus_FRA_01/zeus/archivelog/2014_05_23/thread_2_seq_23044.3558.84
8348137'
ORA-00283: cool cancelled due to errors
ORA-19906: embodiment of changed during recovery recovery targets
Any possible solution to the resume and cloning complete successfully?
Kind regards
Ritu

incarnation of the list;

It listed 2 incarnation. I have reset the previous incarnation

RESET DATABASE TO INCARNATION 2;

and recovered again and it solved my problem.

After that added temp files as usual after failing RMAN duplication;

After this nest of DB and open reset logs.

RMAN recovery catalog number

Hi all;
Lem I have a probwhen you configure the recovery catalog.
SERVER 01: 192.168.1.105 DB - NAME (db1)
SERVER 02: 192.168.1.106 DB - NAME (db2)
DB1 the TNS alias name is : DBONE -> 192.168.1.105
db2 the TNS alias name is : DBTWO -> 192.168.1.106
I tried to cash catalog of recovery in db2 to db1. but I encountered some problems.
Already, I have configured listener, tns entered into two servers.

The OS level - in db2 database) (192.168.1.106 server) here's the problem ...

rman catalog username $ / password@tns_aliasname.

I want to know, TNS ALIAS name should be what server what show above the command?
Thanks in advance...

Run rman in your data base (d1) target server (105). The tns for the catalog alias is dbtwo.

Connect to 192.168.1.105 'oracle' (or the owner of oracle)

value your ORACLE_SID db1

RMAN target / catalog rmn_rc/rmn_rc@dbtwo

Hemant K Collette

Controlfile autobackup without RMAN recovery

Hello
I'm trying to restore a customer database of RMAN backups for the same instance name and DBID but a different server with a different directory structure.
It is a full RMAN backup, but the log shows that the controlfile is supported only through current, not with autobackup backup controlfile.
I have built directories bdump standard and created a directory of data, file a copy of the init.ora in order to take into account locations suitable for the dump file, the archive logs and the controlfiles and also added in the settings db_file_name_convert and log_file_name_convert to map the original directory structure noted in the backup rman to the new locations.
I understand that you cannot restore the backup controlfile, but was under the impression that you can set the format and restore the controlfile but am not having luck with this-
[oracle@el64dev03 dbs] $ echo $ORACLE_SID
EUMSIPSP
rman target $ [oracle@el64dev03 dbs].
Recovery Manager: Release 10.2.0.4.0 - Production Wed Aug 28 16:05:37 2013
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to the database target (not started)
RMAN > startup nomount;
Oracle instance started
Total System Global Area 524288000 bytes
Bytes of size 2085256 fixed
285216376 variable size bytes
230686720 of database buffers bytes
Redo buffers 6299648 bytes
RMAN > set dbid 1887849233; (this is the ID of database)
executing command: SET DBID
RMAN > restore controlfile to ' / oradata2/10.2.0/CUST-EUMSIPSP/BAK_98723_d3ohkisi. CTL'; (this is the backup piece pointed in the RMAN backup)
From restoration to 28 Aug 13
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 430 devtype = DISK
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the restore command at 28/08/2013 16:06:24
RMAN-06172: no autobackup couldn't find or handle specified is not a valid copy or a piece
RMAN > run {}
2 > affect the disc type channel d1 format ' / oradata2/10.2.0/CUST-EUMSIPSP/BAK_%s_%u.CTL';
3 > restore controlfile to ' / oradata2/10.2.0/EUMSIPSP/' to ' / oradata2/10.2.0/CUST-EUMSIPSP/';
{4 >}
output channel: ORA_DISK_1
allocated channel: d1
channel d1: sid = 430 devtype = DISK
From restoration to 28 Aug 13
output channel: d1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the restore command at 28/08/2013 16:09:01
RMAN-06172: no autobackup couldn't find or handle specified is not a valid copy or a piece
RMAN > exit
RMAN BACKUP log-
...
connected to target database: EUMSIPSP (DBID = 1887849233)
using the control file of the target instead of recovery catalog database
RMAN > run {}
2 > allocate channel d1 type disk;
3 > setlimit channel d1 readrate 2000;
4 > sql 'alter database backup controlfile to trace. "
5 > backup
6 > filesperset 1
7 > format ' / oracle/RMAN/eumsipsp/backups/full/BAK_%s_%u.CTL'
8 > (current controlfilE);
{9 >}
10 >
allocated channel: d1
channel d1: sid = 425 devtype = DISK

SQL statement: alter database backup controlfile to trace
From backup 18 August 13
channel d1: from full datafile backupset
channel d1: specifying datafile (s) in backupset
including the current control in backupset file
channel d1: from room 1 to 18 August 13
channel d1: finished piece 1 at 18 August 13
piece handle = / oracle/RMAN/eumsipsp/backups/full/BAK_98723_d3ohkisi. Tag CTL = comment TAG20130818T191425 = NONE
channel d1: complete set of backups, time: 00:00:01
Backup finished on 18 August 13
output channel: d1
...
Copied the information from backup files-
[CUST-EUMSIPSP oracle@el64dev03] $ pwd
/oradata2/10.2.0/Cust-EUMSIPSP
[CUST-EUMSIPSP oracle@el64dev03] $ ls - lt * Journal
-rw - r - r - 1 oracle oinstall 22139 23 August at 14:25 rman_full_eumsipsp_20130818190000.log
[CUST-EUMSIPSP oracle@el64dev03] $ ls - lt * CTL
-rw - r - r - 1 oracle oinstall 11927552 28 August at 11:08 BAK_98723_d3ohkisi. CTL
Is it possible to recover the controlfile at all (as in a disaster situation) so that the database can then be recovered.
More welcome advice
Concerning
Lesley

I do not know what operating system, customers use

I need to prove the process works and what I'm looking for is correct, before I can go back to them and ask what they sent.

Yes, but operating systems may be incompatible. For example, if yours is Linux, and one of the clients is AIX, it would not work, and you get the error that you actually get.

RMAN recovery is data loss - tips welcome
Hello

I really need help here if someone is a guru RMAN n.

Problem
------------

The system I have recover aid that the rman backup below does not include the table that I created after the backup was completed, the database has been recovered, but somehow the creation and populating a table after the backup is complete have been lost. Can you see what I did wrong here, the text is based on an existing script I need to also change little this is used in Prod dystsems elsewhere

DB is:-11.2.0.1

Please adsvise where I'm wrong...

Target of $ORACLE_HOME/bin/rman / log = $BACKUP_LOG < < EOF
Run {}
delete noprompt obsolete device type disk;
affect the disc channel d1 device format type "$ORACLE_BACKUP_DIR_LOC/%Y_%M_%D/database_%U."
allocate channel device d2 disc format type "$ORACLE_BACKUP_DIR_LOC/%Y_%M_%D/database_%U."
backup as compressed backupset database include current controlfile;
output channel d1;
output channel d2;
SQL 'alter system archive log current';
affect the disc channel a1 device format type "$ORACLE_BACKUP_DIR_LOC/%Y_%M_%D/archivelog_%U."
Backup to compressed backupset archivelog all;
output channel a1;
delete noprompt obsolete device type disk;
}
backup from the list;
output
EXPRESSIONS OF FOLKLORE

What I've done
------------------

Create a table and insert a line first (backup before): -.

create table rman_test (empname varchar2 (20), varchar2 (20)) of the city.

insert into rman_test values ('azar', 'riyadh');
insert into rman_test values ('jabar', 'chennai');
commit;

Select count (*) in the rman_test;
2 rows

Run the script of backup as follows: -.
CD/u01/scripts
SH hot_backup_db.bash emrep/u01/backup/u01/scripts
Parameter 1 - SID ORACLE
Parameter 2 - directory where will backups rman
Parameter 3 - directory where rman records go

Create a table after backup so we can verify that the data is not lost

create table rman_test1 (empname varchar2 (20));
insert into rman_test1 values ('kareem');
insert into rman_test1 values ('syed');
commit;
Select count (*) in the rman_test1;
2 rows

Stop and rename the db files to impersonate a systems crash

Closing of the database '
Rename/u01/oradata/emrep in emrep-ren

Renamed the spfile;
CD $ORACLE_HOME/dbs
MV spfileemrep.ora spfileemrep.ora_ren

Prepare for recovery

Look at the rman backuplog: -.

Search the DBID:-e, g, connected to the target database: EMREP (DBID = 4012088007)

Looking for where are the backups spfile and controlfile;
Item name: / u01/backup/2012_07_25/database_2jnh03ua_1_1
Control file included: cash SNA: 1344967 cash time: July 25, 12 16:16:10
Item name: / u01/backup/2012_07_25/database_2knh03uc_1_1
SPFILE included: Modification Date: July 25, 12 14:27:55

Note the path and the name of the backup items to the location of backup for the last backup.

Recover the database (all nuked)
----------------------------------------------------------

RMAN target /.
the value of dbid 4012088007

startup nomount

Restore spfile to ' / u01/backup/2012_07_25/database_2knh03uc_1_1 ";

Restore controlfile to ' / u01/backup/2012_07_25/database_2jnh03ua_1_1 ";
From restoration to 24/07/2012 10:32:24
using channel ORA_DISK_1
channel ORA_DISK_1: restore the control file
channel ORA_DISK_1: restore complete, duration: 00:00:01
output file name=/u01/app/oracle/product/11.2.0/dbhome_1/dbs/cntrlemrep.dbf
Finished restore at 24/07/2012 10:32:25

immediate stop
startup nomount

Restore controlfile to ' / u01/app/oracle/product/11.2.0/dbhome_/dbs/cntrlemrep.dbf';
change the editing of the database;

Catalogue backuppiece ' / u01/backup/2012_07_25/database_2hnh03u3_1_1 ";
Catalogue backuppiece ' / u01/backup/2012_07_25/database_2inh03u3_1_1 ";
Catalogue backuppiece ' / u01/backup/2012_07_25/database_2jnh03ua_1_1 ";
Catalogue backuppiece ' / u01/backup/2012_07_25/database_2knh03uc_1_1 ";
Catalogue backuppiece ' / u01/backup/2012_07_25/archivelog_2lnh03vg_1_1 ";

restore the database;

recover the database;

This experience: -.

Archives journal thread = 1 sequence = 49
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command recover at 25/07/2012 13:42:54
RMAN-06054: unknown request media recovery log archived for thread 1 with sequence 49 and from the 1330997 SNA

ALTER database open resetlogs;

Select count (*) in the rman_test;
Select count (*) in the rman_test1;

QL > select count (*) in the rman_test;
Select count (*) in the rman_test1;

COUNT (*)
----------
2

SQL > select count (*) in rman_test1
*
ERROR on line 1:
ORA-00942: table or view does not exist

How can I recover it?
Welcome to all the advice I can get. Select count (*) rman_test1 should return 2 rows.

Cheers, Rob Ford, DBA Oracle recent to rman
RMAN-06054: unknown request media recovery log archived for thread 1 with sequence 49 and from the 1330997 SNA

This sequence might not have been archived, and it could be your with the State CURRENT redolog file.

During my recovery, give the path of your redolog file RUNNING when he asks sequence 49.

SQL > restore database using backup controlfile until cancel;

Published by: renee_mathieu on July 26, 2012 14:49

Restore and backup RMAN recovery in a new server

Version: 11.2
Platform: Solaris

I did several restorations of RMAN backups to new hosts. Whenever I do a full recovery of a cold backup, when I run the

RECOVER DATABASE

I used to get

archive log filename=/u04/mvf/data/dbase/arch/arch.log1_235_678649266.dbf thread=1 sequence=235
unable to find archive log
archive log thread=1 sequence=236
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 12/04/2011 14:33:18
RMAN-06054: media recovery requesting unknown log: thread 1 seq 236 lowscn 11290198

I considered this as being 'Normal' and always used to cause

alter database open resetlogs

But I read the below mentioned informative post yesterday.

Question on create Redo log after restoring files and recover

According to the guidelines of this post, I shouldn't use

alter database open resetlogs

for a full recovery.

So, what should I do
a.
Should I use

ALTER DATABASE OPEN ; -- I think I got some error with this command when i issued it after RMAN-06054 error . Can't recall what error

OR

b.
Should I use

recover database until sequence 236;

Here is how I could use a combination of RMAN (for RESTORATION) and SQL (for the OPEN RESETLOGS):

$ rman target /

Recovery Manager: Release 10.2.0.2.0 - Production on Wed Nov 16 05:40:51 2011

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database (not started)

RMAN> startup nomount

Oracle instance started

Total System Global Area     419430400 bytes

Fixed Size                     1261164 bytes
Variable Size                113246612 bytes
Database Buffers             297795584 bytes
Redo Buffers                   7127040 bytes

RMAN> restore controlfile from autobackup;

Starting restore at 16-NOV-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK

recovery area destination: /usr/oracle/flash_recovery_area
database name (or database unique name) used for search: MYNDB
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /usr/oracle/flash_recovery_area/MYNDB/autobackup/2011_11_16/o1_mf_n_767337675_7d6l55ck_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/usr/oracle/oradata/MYNDB/control01.ctl
output filename=/usr/oracle/oradata/MYNDB/control02.ctl
Finished restore at 16-NOV-11

RMAN> sql 'alter database mount';

sql statement: alter database mount
released channel: ORA_DISK_1

RMAN>
RMAN> restore database;

Starting restore at 16-NOV-11
Starting implicit crosscheck backup at 16-NOV-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=155 devtype=DISK
Crosschecked 16 objects
Crosschecked 3 objects
Finished implicit crosscheck backup at 16-NOV-11

Starting implicit crosscheck copy at 16-NOV-11
using channel ORA_DISK_1
using channel ORA_DISK_2
Finished implicit crosscheck copy at 16-NOV-11

searching for all files in the recovery area
cataloging files...
cataloging done

List of Cataloged Files
=======================
File Name: /usr/oracle/flash_recovery_area/MYNDB/autobackup/2011_11_16/o1_mf_n_767337675_7d6l55ck_.bkp

using channel ORA_DISK_1
using channel ORA_DISK_2

channel ORA_DISK_2: starting datafile backupset restore
channel ORA_DISK_2: specifying datafile(s) to restore from backup set
restoring datafile 00003 to /usr/oracle/oradata/MYNDB/sysaux01.dbf
restoring datafile 00004 to /usr/oracle/oradata/MYNDB/users01.dbf
restoring datafile 00005 to /usr/oracle/oradata/MYNDB/datafile/o1_mf_example_7c4qzn5k_.dbf
restoring datafile 00006 to /usr/oracle/oradata/MYNDB/undotbs.dbf
channel ORA_DISK_2: reading from backup piece /usr/oracle/flash_recovery_area/MYNDB/backupset/2011_11_16/o1_mf_nnndf_TAG20111116T052209_7d6l4227_.bkp
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /usr/oracle/oradata/MYNDB/system01.dbf
restoring datafile 00002 to /usr/oracle/oradata/MYNDB/datafile/o1_mf_hemant_7c4qzn0o_.dbf
restoring datafile 00007 to /usr/oracle/oradata/MYNDB/datafile/o1_mf_assm_tbs_7c4qzn0q_.dbf
restoring datafile 00008 to /usr/oracle/oradata/MYNDB/datafile/o1_mf_mssm_tbs_7c4qzn0x_.dbf
channel ORA_DISK_1: reading from backup piece /usr/oracle/flash_recovery_area/MYNDB/backupset/2011_11_16/o1_mf_nnndf_TAG20111116T052209_7d6l4216_.bkp
channel ORA_DISK_1: restored backup piece 1
piece handle=/usr/oracle/flash_recovery_area/MYNDB/backupset/2011_11_16/o1_mf_nnndf_TAG20111116T052209_7d6l4216_.bkp tag=TAG20111116T052209
channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
channel ORA_DISK_2: restored backup piece 1
piece handle=/usr/oracle/flash_recovery_area/MYNDB/backupset/2011_11_16/o1_mf_nnndf_TAG20111116T052209_7d6l4227_.bkp tag=TAG20111116T052209
channel ORA_DISK_2: restore complete, elapsed time: 00:00:35
Finished restore at 16-NOV-11

RMAN>
RMAN> exit

Recovery Manager complete.
$ sqlplus '/ as sysdba'

SQL*Plus: Release 10.2.0.2.0 - Production on Wed Nov 16 05:42:52 2011

Copyright (c) 1982, 2005, Oracle.  All Rights Reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SQL> alter database open resetlogs;

Database altered.

SQL>

Note This error message 1589 is:

$ oerr ora 1589
01589, 00000, "must use RESETLOGS or NORESETLOGS option for database open"
// *Cause:  Either incomplete or backup control file recovery has been
//          performed. After these types of recovery you must specify either
//          the RESETLOGS option or the NORESETLOGS option to open your
//          database.
// *Action: Specify the appropriate option.
$

Hemant K Collette

RMAN recovery window and redundancy
Hello

I am using Oracle 11 g (11.2.0.1) in windows 2003 server. RMAN is it possible to put both the below configuration in force or any configuration cannot be used?

RMAN > CONFIGURE RETENTION POLICY to RECOVERY OF 7-DAY WINDOW;

RMAN > CONFIGURE REDUNDANCY 2 RETENTION POLICY;

Kind regards

007
I want the political configuration RMAN to apply

Lol you can only use the KeepOption to change a specific backup strategy:

http://download.Oracle.com/docs/CD/B28359_01/backup.111/b28273/rcmsubcl011.htm#i97063

Pouvez RMAN recovery table level
Hello

I know you can make database level recovery and a tablespace with RMAN. Can you also level table recovery? How granular can you get?

Thank you
N ° as you said granularity restore RMAN tablespace (TSPITR) and the database (complete or incomplete). No database object level recovery.
If you're on 10g, you may benefit from features of flashback. Flashback, flashback, flashback query etc. versions query table in the measure where your data is still in the undo tablespace. (if your tablespace big enough undo and retention period is high, you can be lucky for a few last periods)

Execution of disaster with RMAN recovery
Hello

http://kamranagayev.WordPress.com/2010/03/29/RMAN-video-tutorial-series-performing-disaster-recovery-with-RMAN/

I want to do the same thing available in the link above. But my ways little different since I use asm as the storage.

ex: -.

SQL > select name from v$ controlfile;

NAME
--------------------------------------------------------------------------------
+Data/proddb/controlfile/current.258.730005353
+Arch/proddb/controlfile/current.258.730005353

but my new database server is not configured for asm.

I can do the same thing by changing the path of the path parameter file everything I love in the dr site?
Or
I need to create a storage asm for the same thing?

My attempt to base is to check the rman backup on a daily basis by restoring to a separate database.

Any ideas...? can someone give me a help to do this please... If you have any good tutorial as above, please report it here.

Thanks in advance,
Max
but my new database server is not configured for asm.

I can do the same thing by changing the path of the path parameter file everything I love in the dr site?
Or
I need to create a storage asm for the same thing?

Do not create instance ASM (also diskgroup). You have full backup, then this means that you can restore this backup to any location and there is no difference restore backup any file system or ASM. Yes as above Hemant mentioned, you can use The VALUE of NEWNAME clause. If you have a lot of data file, then I suggest that you use the DB_FILE_NAME_CONVERT and DUPLICATION of RMAN initialization parameter. But consider now that your database running in the ASM then take full to simple (not ASM) backup file system as BACKUP of DATABASE ARCHIVELOG FORMAT ' / u01/backup/full_ % d_ % u_ .bk %s '; (also take controlfile backup or activate backup AUTOMATIC). Now copy all the backup on the new server and
```
/*Restoring spfile*/
export ORACLE_SID=
rman target /
startup force nomount;
restore spfile  from 'AUTOBACKUP_LOCATION';
/*After restoring spfile then connect using sqlplus
and change need parameter like CONTROL_FILES and others
due to this is not ASM FS and again*/
startup force nomount;
restore controlfile from 'AUTOBACKUP_LOCATION';
alter database mount;
/*catalog backup*/
catalog start with 'backup_location';
/*Now change datafile location*/
run
{
set newname for datafile 1 to 'new location';
.............................................................
set newname for datafile n to 'new location';
}
restore database;
switch datafile all;
recover database;
alter database open resetlogs;
```

Problem in time through RMAN recovery
Salute to seniors,

I'm trying to recover a table that has been deleted by mistake at 22:25:11 (2 October 2010). I put the settings nls_date_format = DD - MM - YYYY:HH24:MI:SS, nls_lang = AMERICAN in the settings file used by the instance. When I try to run the following command at the RMAN prompt:

* RMAN > run {*}
* 2 > set until that time ='02-10 - 2010:22:25:00'; *
* 3 > restore database; *
* 4 > restore database ;} *

I get the following error:

executing command: SET until clause
RMAN-00571: ====================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ====================================================
RMAN-03002: failure of the set command in the 02/10/2010 22:29:24
ORA-01843: not one month valid

Help, please!

Kadamabari,
India.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With partitioning, OLAP, Data Mining and Real Application Testing options

SQL > select current_timestamp to double;

CURRENT_TIMESTAMP
---------------------------------------------------------------------------
OCTOBER 3, 10 10.37.42.839000 + 03:00 AM

SQL > select systimestamp from double;

SYSTIMESTAMP
---------------------------------------------------------------------------
OCTOBER 3, 10 10.38.22.950000 + 03:00 AM

SQL > drop table employee;

Deleted table.

SQL > commit;

Validation complete.

SQL > shutdown immediate
The database is closed.
The database is dismounted.
ORACLE instance stops.

SQL > startup pfile='D:\TEST\initow.ora' mount;
ORACLE instance started.

Total System Global Area 535662592 bytes
Bytes of size 1375792 fixed
188744144 variable size bytes
339738624 of database buffers bytes
Redo buffers 5804032 bytes
Mounted database.

C:\Users\mazar>RMAN target.

Recovery Manager: release 11.2.0.1.0 - Production on Sun 3 Oct 10:44:31 2010

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

connected to target database: OWN (DBID = 1547349083, is not open)

RMAN > run {}
2 > until ' to_date (October 3, 10 10.38.22 ',' DD-MON-RR HH24:MI:SS ') ";
3 > restore database;
4 > restore database;
{5 >}

executing command: SET until clause

From restoration to October 3, 10
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 10 type of device = DISK
flashing rear control SNA 1444750 file

jump datafile 9; already restored to the D:\TEST\TESTSAMPLE01 file. DBF
jump datafile 12; already restored to the D:\TEST\TESTSAMPLE file. DBF
, ,,, ,,,,,,,,

RMAN > alter database open resetlogs;

open database

RMAN > exit

Complete recovery manager.

C:\Users\mazar>sqlplus

SQL * more: Production of release 11.2.0.1.0 Sun 3 Oct 10:49:59 2010

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Enter the user name: / as sysdba

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With partitioning, OLAP, Data Mining and Real Application Testing options

SQL > select * from employee;

EMP
--------------------
Azar

SQL >

Error # SNA on RMAN recovery

I am trying to restore a production database to a new host using an RMAN backup following these instructions:

http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14191/rcmrecov.htm#i1006453

I'm at the part where I run the restore script, but it keeps slightest mistake out on the RCS #. I have tried several values, including the one I got from the BD live, but no luck. Can anyone suggest a solution? Do I really need to use the restore to the SNA X #?

Here are the restore script:

RUN
{
  # allocate a channel to the tape device
  ALLOCATE CHANNEL c1 DEVICE TYPE DISK PARMS='D:\Oracle_backup';

  # rename the datafiles and online redo logs
  SET NEWNAME FOR DATAFILE 1 TO '+DATA/ts/system.256.591973253';
  SET NEWNAME FOR DATAFILE 2 TO '+DATA/ts/undotbs1.258.591973253';
  SET NEWNAME FOR DATAFILE 3 TO '+DATA/ts/sysaux.257.591973253';
  SET NEWNAME FOR DATAFILE 4 TO '+DATA/ts/users.259.591973253';
  SET NEWNAME FOR DATAFILE 5 TO '+DATA/ts/example.265.591973345';
  SET NEWNAME FOR DATAFILE 6 TO '+DATA/ts/peoplenetif.267.592044455';
  SET NEWNAME FOR DATAFILE 7 TO '+DATA/ts/htmldb.268.592497801';
  SET NEWNAME FOR DATAFILE 8 TO '+DATA/ts/peoplenetif.271.592044549';
  SET NEWNAME FOR DATAFILE 9 TO '+DATA/ts/statspack.333.592919141';
  SET NEWNAME FOR DATAFILE 10 TO '+DATA/ts/system.343.643980815';
  SET NEWNAME FOR DATAFILE 11 TO '+DATA/ts/flow_1.344.593167821';
  SET NEWNAME FOR DATAFILE 12 TO '+DATA/ts/flow_2.345.593169609';
  SET NEWNAME FOR DATAFILE 13 TO '+DATA/ts/flow_3.346.593178027';
  SET NEWNAME FOR DATAFILE 14 TO '+DATA/ts/rman.441.595605123';
  SET NEWNAME FOR DATAFILE 15 TO '+DATA/ts/apexlib.519.643624021';
  SET NEWNAME FOR DATAFILE 16 TO '+DATA/ts/ts_data.506.643981157';
  SET NEWNAME FOR DATAFILE 17 TO '+DATA/ts/flow_4.4420.705085451';

  # Do a SET UNTIL to prevent recovery of the online logs
  SET UNTIL SCN 534907;
  # restore the database and switch the datafile names
  RESTORE DATABASE;
  SWITCH DATAFILE ALL;

  # recover the database
  RECOVER DATABASE;
}
EXIT

Here is the error I get:

executing command: SET until clause
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 04/22/2010 14:02:20
RMAN-20208: UNTIL CHANGE is before RESETLOGS change

RMAN> EXIT

BTW - my production server is very good, we're just trying to get in place with new hardware backup procedures.

Run LIST BACKUP OF ARCHIVELOG ALL restored using controlfile and retrieve the YVERT value next to the last record returned by the list command.

Lukasz

RMAN recovery error? Why is it so? s ' Please help :)
Hi guys,.

First of all, 1 million of thanks and gratitude to those who are willing to spend time reading my thread and using all the less out / give suggestions.

I am very very very new for backup and restore, so I really hope that you guys will give me with your utmost patience and tolerance, if I by no risk stupid or dumb questions or if there is very direct terms that I don't apprehand...

--------------------------------

Current configuration.

I have 2 database each on a different server, but the configuration of file directories are the same for both (prod, 1 stage 1)

(1) on the prod, I do a daily backup of 03:00.
(2) my full backup includes controlfile autobackup and archivelogs.
(3) after that, I'll do a RSYNC to send all items to backup to the staging server.
(3) on stage, I will / want to apply the daily backup of prod on it. I don't mind not seen the last DB (changes after 03:00 not recorded)
(4) I don't use rman catalog. If all the backup information store in the control file.

I made a backup in the RMAN LIST on production and saw all the backup information including these...

Part name: /u02/rmanbkp/STARHUB_lskv1oi0_1_1.rmanbk

List of newspapers archived in defined backup 5819
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 8910 2440140540 22 NOVEMBER 09 2440223507 22 NOVEMBER 09
1 8911 2440223507 22 NOVEMBER 09 2440363724 22 NOVEMBER 09
1 8912 2440363724 22 NOVEMBER 09 2440508680 22 NOVEMBER 09

Overhere, we are sure that the archivelogs are backed up and I don't want to apply these archivelog when I restore the database.

 please NOTE THAT the backup is on/U02/rmanbkp / 

-------------------------------------------------

Now more to STAGE, where I restore / recover (please see the BOLD characters)


RMAN > restore controlfile autobackup.

From restoration to 23 November 09
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 157 devtype = DISK

channel ORA_DISK_1: looking for autobackup day: 20091123
channel ORA_DISK_1: autobackup found: / u02/rmanbkp/c-690163925-20091123-00
channel ORA_DISK_1: restore full automatic backup of control file
output filename=/u03/oradata/starhub/control02.ctl
output filename=/u01/oradata/starhub/control01.ctl
Restoration finished November 23 09

RMAN > change the editing of the database;

mounted database
output channel: ORA_DISK_1

RMAN > restore database;

From restoration to 23 November 09
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 157 devtype = DISK

channel ORA_DISK_1: from datafile backupset restoration
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
restoring datafile 00003 to /u03/oradata/starhub/sysaux01.dbf
restoring datafile to /u03/oradata/starhub/starhub02.dbf 00006
restoring datafile 00009 to /u03/oradata/starhub/starhub05.dbf
channel ORA_DISK_1: backup /u02/rmanbkp/STARHUB_m7kv1ols_1_1.rmanbk piece reading
channel ORA_DISK_1: restored the backup part 1
piece handle=/u02/rmanbkp/STARHUB_m7kv1ols_1_1.rmanbk tag = TAG20091123T030220
channel ORA_DISK_1: restore complete, duration: 00:02:26
channel ORA_DISK_1: from datafile backupset restoration
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
restoring datafile 00001 to /u03/oradata/starhub/system01.dbf
restoring datafile 00002 to /u03/oradata/starhub/undotbs1.dbf
restoring datafile 00007 to /u03/oradata/starhub/starhub03.dbf
channel ORA_DISK_1: backup /u02/rmanbkp/STARHUB_m8kv1opp_1_1.rmanbk piece reading
channel ORA_DISK_1: restored the backup part 1
piece handle=/u02/rmanbkp/STARHUB_m8kv1opp_1_1.rmanbk tag = TAG20091123T030220
channel ORA_DISK_1: restore complete, duration: 00:02:26
channel ORA_DISK_1: from datafile backupset restoration
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
restoring datafile 00004 in /u03/oradata/starhub/tbs1.dbf
restoring datafile 00005 to /u03/oradata/starhub/starhub01.dbf
restoring datafile 00008 to /u03/oradata/starhub/starhub04.dbf
channel ORA_DISK_1: backup /u02/rmanbkp/STARHUB_m9kv1ov0_1_1.rmanbk piece reading
channel ORA_DISK_1: restored the backup part 1
piece handle=/u02/rmanbkp/STARHUB_m9kv1ov0_1_1.rmanbk tag = TAG20091123T030220
channel ORA_DISK_1: restore complete, duration: 00:02:15
Restoration finished November 23 09

RMAN > restore database;

From pick up to 23 November 09
using channel ORA_DISK_1

starting media recovery


Archive journal 1 sequence 8935 thread is already on the disk that the file /u01/oradata/starhub/arch/log1_8935_656935637.arc--repertoire of the OPINION it IS READING /U01/
archive log thread = 1 sequence = 8935 filename=/u01/oradata/starhub/arch/log1_8935_656935637.arc
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8936_656935637.arc thread = 1 sequence = 8936
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8937_656935637.arc thread = 1 sequence = 8937
archive log thread = 1 sequence = 8938 filename=/u01/oradata/starhub/arch/log1_8938_656935637.arc
archive log thread = 1 sequence = 8939 filename=/u01/oradata/starhub/arch/log1_8939_656935637.arc
archive log thread = 1 sequence = 8940 filename=/u01/oradata/starhub/arch/log1_8940_656935637.arc
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8941_656935637.arc thread = 1 sequence = 8941
archive log thread = 1 sequence = 8942 filename=/u01/oradata/starhub/arch/log1_8942_656935637.arc
archive log filename=/u01/oradata/starhub/arch/log1_8943_656935637.arc = 1 sequence = 8943 thread
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8944_656935637.arc thread = 1 sequence = 8944
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8945_656935637.arc thread = 1 sequence = 8945
archive log thread = 1 sequence = 8946 filename=/u01/oradata/starhub/arch/log1_8946_656935637.arc
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8947_656935637.arc thread = 1 sequence = 8947
Archive newspaper filename=/u01/oradata/starhub/arch/log1_8948_656935637.arc thread = 1 sequence = 8948
archive log thread = 1 sequence = 8949 filename=/u01/oradata/starhub/arch/log1_8948_656935637.arc
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command recover at 23/11/2009 15:36:21
RMAN-11003: failure in parsing / execution of the SQL statement: alter database recover logfile ' / u01/oradata/starhub/arch/log1_8948_656935637.arc'
ORA-00310: archived log contains sequence 8948; 8949 sequence required
ORA-00334: archived log: ' / u01/oradata/starhub/arch/log1_8948_656935637.arc'



------------------------------------------------------

My questions are

T1) I restore the database (I see that these backup item is read from the rmanbkp/u02/and these data, the files are restored).
Now, I want to recover the database, so I think I must apply these archivelogs backup for recovery.

However, if you notice, RMAN is reading about (deprecated) /U01/ on the archivelogs instead of the archivelogs saved in /U02/rmanbkp. 

Why so much? Is this the correct behavior? How can I make RMAN uses these elements to backup archivelog on/U02/rmanbkp

Q2) that I encounter this error ORA-00310: and I get autour. It is saying that I need to use a BACK up to WHAT if I don't want this error.

However, I believe that information of hold of FILE OF CONTROL over where and how long does RETRIEVE UNTIL, isn't? (and since I'm on the CONTROL FILE of the recovery, why I always see this error?

Your kind advice/help would be really appreciated.

Best regards
Noob
Hey Noob,

A1) because the controlfile comes from the production server where the archived redologs are available in
/ U01/oradata/StarHub/Arch, you must run an overlap on the stage for the controlfile node is updated.

change archivelog than any overlap;

remove expired archivelog all;

To move forward with recovery of database until...;

A2)
You must specify a point in time, scn, or logsequence if you want to recover to a point in the past (which is what you want to do).
If you get it back until the clause, rman performs a recovery complete (up to the last committed transaction) to do this, you need the redologs online that are not backed up by rman.

Kind regards

Tycho

RMAN recovery

Similar Questions

Maybe you are looking for