Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Trying to restore a database with RMAN in new server and new location of backppieces

475 views
Skip to first unread message

Big George

unread,
Apr 26, 2012, 10:38:12 AM4/26/12
to
Hello,

Database: Oracle 10gR2
O/S: Windows Server 2003

My RMAN backuppieces are stored in a network drive:
\\old_location\FULL
and
\\old_location\INC

I'm trying to restore a whole database with RMAN in another server
from my FULL backup.

For that, I copy all backuppieces files
from: \\old_location\FULL
to new server: D:\new_location\

Also I created the relevant folder hierarchy under <ORACLE_BASE>
directory, as follows:

a. Create BDUMP, CDUMP, and UDUMP directories under '<ORACLE_ BASE>
\admin' directory

b. Create <DATABASE_NAME> directory under '<ORACLE_BASE>\oradata'
directory

c. pfile.ora and controlfile (CTL_MTDPROD_2308_20120401_1.CTL) are
backup from original database and they are in D:\new_location\

d. I copied pfile.ora and controlfile to folder: C:\oracle\product
\10.2.0\db_1\database\

I started creating an instance in new server from scratch:

C:\>oradim -new -sid MTDPROD -intpwd mtdprod
C:\> SET ORACLE_SID=MTDPROD
C:\> rman
RMAN> connect target sys
RMAN> SET DBID=21692876873
RMAN> STARTUP force nomount PFILE=C:\oracle\product
\10.2.0\db_1\database\init_mtdprod.ora
RMAN> restore controlfile from 'C:\oracle\product\10.2.0\db_1\database
\CTL_MTDPROD_2308_20120401_1.CTL';
RMAN> alter database mount;

#Since I want to read my backuppieces from D:\new_location and not
from \\old_location\FULL then I catalog and restore like:

RMAN> catalog start with 'D:\new_location\';
RMAN> restore database;

Starting recover at 25/04/12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=541 devtype=DISK
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile copies to recover
recovering datafile copy fno=00003 name=D:\BD_MTDPROD\CONTROLFILES
\SYSAUX01.DBF
recovering datafile copy fno=00004 name=D:\BD_MTDPROD\CONTROLFILES
\USERS01.DBF
recovering datafile copy fno=00007 name=D:\BD_MTDPROD\DATAFILES_DATA
\MSE.ORA
recovering datafile copy fno=00010 name=D:\BD_MTDPROD\DATAFILES_DATA
\EXPEDIENTES2.ORA
channel ORA_DISK_1: reading from backup piece \\old_location\FULL
\FULL_MTDPROD_20120401_2304_1.BAK
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: failover to piece handle=D:\new_location\FULL
\FULL_MTDPROD_20120401_2304_1.BAK tag=TAG20120401T190004
.....(continues)

Questions:

1. RMAN still reads from old_location. The only way to avoid that
would be deleting all files from \\old_location\FULL ?
2. The message "failover to piece handle=D:\new_location\...."
indicates that that file is not usefull? I just copy them from
old_location to new_location... how can they get useless?

I suspect there is something in controlfile that redirects to \
\old_location\FULL\ and doesn't let to read from D:\new_location\

Please, advice.

onedbguru

unread,
Apr 27, 2012, 6:04:07 PM4/27/12
to
1) before starting the instance, modify the init.ora and comment out the DB_RECOVERY parameters
2) after starting the instance an restoring the control files:
a) make sure the database cannot see ..\old_version
b) crosscheck archive all , crosscheck backup
c) delete noprompt expired backup, delete noprompt expired archivelog all
d) catalog start with '...new_location'

0 new messages