RMAN clone in new server

Hi
I have rman tape backup of the entire database. I want to clone this on new server.
I have started database in new server. It is in mount stage. how to restore and recover the datafiles on new host.
I am using leagato server for tape backup. Please guide me on this.

You need to use RMAN DUPLICATE and to adapt following steps to your environment http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmdupdb.htm#i1006474.
About tape backups, please note:
>
When using tape backups, you must make the tapes containing the backups accessible to the remote node. You can achieve this goal by physically moving the tape to a drive attached to the remote host or by means of a network-accessible tape server.

Similar Messages

Restore RMAN backup on new server

Hi
I took RMAN backup of a database with control file autobackup on...I copied the backup
to a new server restored the spfile from the backup and modified the parameters
bdump,udump,control file because the directory structure is different from the original
machine.I restored the control file and it was restored properly.
Now I need to restore the datafiles in the new path so I used set newname and switch
but I get some error ....I have posted the error please look at it
RMAN> run
2> {
3> set newname for datafile 1 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\SYSTEM01.DBF';
4> set newname for datafile 2 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\UNDOTBS01.DBF';
5> set newname for datafile 3 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\SYSAUX01.DBF';
6> set newname for datafile 4 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\USERS01.DBF';
7> set newname for datafile 5 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\TSDATA_01.DBF';
8> set newname for datafile 6 to 'E:\ORACLE\METAGRID\ORADATA\METAGRID\TSIDX01.DBF';
9> set newname for datafile 7 to
'E:\ORACLE\METAGRID\ORADATA\METAGRID\TSDATA_AUDIT01.DBF';
10> restore database;
11> switch datafile all;
12> recover database;
13> }
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 11-NOV-10
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 E:\ORACLE\METAGRID\ORADATA\METAGRID\SYSTEM01.DBF
restoring datafile 00002 to E:\ORACLE\METAGRID\ORADATA\METAGRID\UNDOTBS01.DBF
restoring datafile 00005 to E:\ORACLE\METAGRID\ORADATA\METAGRID\TSDATA_01.DBF
restoring datafile 00006 to E:\ORACLE\METAGRID\ORADATA\METAGRID\TSIDX01.DBF
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 11/11/2010 12:38:24
ORA-19693: backup piece E:\RMAN\DB_0FLSLJH1_1_1 already included

Try to clear and recatalog the backups to be used, before the restore:
rman target /
crosscheck backup;
delete expired backup;
catalog start with 'path_to_your_backup';

RMAN Duplicate to new Server

I need to RMAN Duplicate database from One Server to New Server. However both Target Database and Auxiliary databases must have same name.
Is it possible?
Database version 11g

Set the duplicate database DB_NAME differently from the target database DB_NAME in some cases. If the duplicate database exists in the same Oracle home as the target, then the DB_NAME initialization parameter must be different. If the duplicate database resides in a different Oracle home (on the same machine or on another machine), then its DB_NAME setting just has to be different from other database names in the same Oracle home on the duplicate host.

RMAN RESTORE A NEW SERVER

I have a complete backup of the source server and I would like to restore it to target server.
Problem is that on my source server I have the complete backup on "E" Drive.
On My target server I just have C and D Drives.
When I try to run Restore database command I get
RMAN-06023: no backup or copy of datafile 1 found to restore
for all the data files as it is looking for my backups on "E" drive which does not exist on Target Server.
Is there a way I can guide RMAN to look on D: drive when restoring?
Thanks
Edited by: user12180649 on May 16, 2012 8:07 AM

user12180649 wrote:
I have a complete backup of the source server and I would like to restore it to target server.
Problem is that on my source server I have the complete backup on "E" Drive.
On My target server I just have C and D Drives.
When I try to run Restore database command I get
RMAN-06023: no backup or copy of datafile 1 found to restore
for all the data files as it is looking for my backups on "E" drive which does not exist on Target Server.
Is there a way I can guide RMAN to look on D: drive when restoring?
Thanks
Edited by: user12180649 on May 16, 2012 8:07 AMOnce you have your controlfile, you can connect to RMAN, delete all the backup piece, and add the new with the new position.
The syntax is:
delete backup; -- to delete all the backups information
catalog start with 'PATH'; -- to add all the backup piece to the "catalog" that in this case could is in the controlfiles.
Other syntax:
http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcmsynta011.htm
Hope this helps.
Nunzio

Rman restore in new server?

My linux machine hardisk has crashed, i am rebuilt entire thing from begining, we have the rman backup & controlfiles & init.ora, pwd file in the tape.
How to rebuild the database from the new catalog. appreciate any body provide a rman step to restore & rebuild...
Adv thanks

>>
Whether i need to create catalog first?. Steps pls
>>
Tell us onething, were was the catalog kept? Was it in the same database? or any other database? or you were using controlfile instead catalog to backup your database?
Lets, catalog is maintained in another database or nocatalog (controlfile) is used to backup.
set oracle_sid
startup nomount
rman target /
run {
allocate channel t1 type 'sbt_tape';
restore controlfile to '<destination>';
sql "alter database mount";
restore database;
recover database;
sql "alter database open resetlogs";
}Jaffar

Restore on new server with new DB_NAME/SID?

My goal is to restore database with the RMAN backup on a server that has no connectivity to the production database (I don’t want to use duplicate command).
I restore a database from RMAN using a same DB_NAME/SID and everything was ok.
-     restore spfile
-     restore controlfile
-     restore database
-     recover database
-     open with reset logs
Now I want to restore database but with different DB_NAME/SID (My production database is PROD and I want to restore this PROD RMAN backup on new server and this new database I want to be called DEV).
How to restore database with new DB_NAME/SID?
Oracle 10g, Windows Server 2003
Thanks in advance!

user9106065 wrote:
My goal is to restore database with the RMAN backup on a server that has no connectivity to the production database (I don’t want to use duplicate command).
I restore a database from RMAN using a same DB_NAME/SID and everything was ok.
-     restore spfile
-     restore controlfile
-     restore database
-     recover database
-     open with reset logs
Now I want to restore database but with different DB_NAME/SID (My production database is PROD and I want to restore this PROD RMAN backup on new server and this new database I want to be called DEV).
How to restore database with new DB_NAME/SID?
Oracle 10g, Windows Server 2003
Thanks in advance!You can use NID command
Run NID and you can see the options to run
or see How to Change the DBID, DBNAME Using NID Utility in version 10GgR2 onwards [ID 863800.1]
Cheers

RMAN backup restoring to new server help!

I'm using Oracle 8.1.7. The production database was copied (datafiles, controlfile etc) to a NEW server that I'm trying to set up as a development DB. I take full database backups using RMAN from the production server, and I want to restore them on the development server. I think I somehow have to specify the filename/location of the backup file but I can't seem to figure out how to do it.
I am not using a recovery catalog.
Any help is appreciated.

If you restore the controlfile backup to the development server RMAN
will "read" the expected location of the backupsets from there.
In 8i you cannot use the CATALOG command so you have to copy all
the backupsets to the same path on the development server as on the
production server.
Once you have your init.ora and controlfiles in place (and created the
expected target directory structure for the database and redolog files),
you can use STARTUP MOUNT and thene RESTORE from RMAN.
I believe that you should be able to rename files in 8i RMAN as well.
If not, you'll have to stick to restoring to the same location.
The key thing is that the controlfile records the "location" of the RMAN backupsets
and the "location" where datafiles are to be restored to.

Trying to restore a database with RMAN in new server

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.

user521219 wrote:
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\Is this a cold backup? Did you change the location of control file in your PFILE or is it still pointing to old location?
You may want to check the output of RESTORE DATABASE PREVIEW command, which will just report which backup files it uses without actually restoring thhe DB.

Migrating Non ASM, Non RMAN to New Server with ASM and RMAN - Possible?

We currently have a database ( Oracle 10g R1 ) on a Sun Solaris server that is NOT using ASM or RMAN. The database is about 300GB. We are getting a new server and we want to install Oracle 10g R2 with ASM and RMAN and migrate the database.
I have seen the documentation on migrating non ASM to an ASM server but the methods all use RMAN. Is it possible to migrate to an ASM database without using RMAN? Would datapump import/export work if I created a new database on the new server with all the same tablespaces? Or, do I have to bite the bullet, install RMAN on the old server and do the backup?
Thanks.

If you're not using RMAN that doesn't mean you can't use it to perform a single backup, rman is contained in every oracle RDBMS installation version 10G or higher.
this is only a sample of how to do it
RMAN> CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '<file_system_path>/%U.DBF';
--first we allocate the channel default channel.
RMAN>RUN
ALLOCATE CHANNEL DEFAULTCHANNEL TYPE DISK;
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
BACKUP DATABASE;
SHUTDOWN
}then once you have it, you can do what you want.
It should also be possible to manually restore the database from the original datafiles but it's better to follow the solution involving RMAN.
Bye Alessandro

Clone DB to a new Server

Hi,
I'm trying to clone our old server with a Oracle database to a new computer. But I can't get our ERP system running because the database is not working somehow. Unfortunately my database knowledge is quite limited.
Actually I cloned the whole system but maybe something went wrong with copying the database. In the original system I opened the "Adminstration Assistent for Windows", stopped the database service by right click and copied the files to the new server.
When I start the ERP system it says "Oracle 8 Error: ORA-01033: Oracle initialization or shutdown in progress".
Any help would really be appreciated.
Thanks
Oliver

Dump file c:\oracle\ora10\rdbms\trace\prod\bg\alert_prod.log
Thu Feb 07 15:00:39 2013
ORACLE V10.2.0.4.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows NT Version V6.0 Service Pack 1
CPU : 1 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1038M/2398M, Ph+PgF:846M/4107M, VA:1902M/2047M
Thu Feb 07 15:00:39 2013
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =61
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 500
sga_max_size = 1577058304
__shared_pool_size = 469762048
__large_pool_size = 8388608
__java_pool_size = 8388608
__streams_pool_size = 8388608
nls_language = AMERICAN
nls_territory = AMERICA
nls_sort = BINARY
sga_target = 1073741824
control_files = F:\ORADB\PROD\PROD_CONTROL1.ORA, D:\ORALOG1\PROD\PROD_CONTROL2.ORA, E:\ORALOG2\PROD\PROD_CONTROL3.ORA
db_block_size = 8192
__db_cache_size = 562036736
compatible = 10.2.0.1.0
log_archive_dest = E:\ORAARCH\PROD
log_archive_format = PROD_%s%r%t.ora
log_buffer = 15236608
db_file_multiblock_read_count= 32
dml_locks = 500
undo_management = AUTO
undo_tablespace = UNDOTBS
undo_retention = 1800
remote_login_passwordfile= EXCLUSIVE
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=INFOR)(PORT=1521))
utl_file_dir = C:\Oracle\ORA10\rdbms\trace\PROD\app
job_queue_processes = 8
parallel_min_servers = 4
parallel_max_servers = 0
background_dump_dest = C:\ORACLE\ORA10\RDBMS\TRACE\PROD\BG
user_dump_dest = C:\ORACLE\ORA10\RDBMS\TRACE\PROD\USER
db_name = PROD
open_cursors = 300
optimizer_mode = ALL_ROWS
pga_aggregate_target = 209715200
PMON started with pid=2, OS id=5428
PSP0 started with pid=3, OS id=4928
MMAN started with pid=4, OS id=3456
DBW0 started with pid=5, OS id=5452
LGWR started with pid=6, OS id=5288
CKPT started with pid=7, OS id=616
SMON started with pid=8, OS id=5464
RECO started with pid=9, OS id=4972
CJQ0 started with pid=10, OS id=4932
MMON started with pid=11, OS id=5032
MMNL started with pid=12, OS id=5608
Thu Feb 07 15:00:39 2013
Oracle Data Guard is not available in this edition of Oracle.
Thu Feb 07 15:00:40 2013
alter database mount exclusive
Thu Feb 07 15:00:40 2013
ORA-214 signalled during: alter database mount exclusive...

RMAN Hot backup Restore in new Server

Hi,
Our Current Environment:
Source: Current Production
Database: 11.1.0.7
OS: Windows server 2003 R2
Target Environemnt:
Database 11.2.0.1
OS:windows server 2008 R2
Here my scenario is need to take RMAN Hot backup in Prod Instance and need to restore in New Server with smae SID which is going to use as Prod instance.
Please suggest the detailed steps in order to achive the goal.
Waiting for your thoughts.
Thanks
Shaik

RMAN can make it easy to restore a database to a new host.
Notice that: Using RMAN RESTORE and RECOVER commands to move a database permanently to another host, will keep the original database identifier (DBID) and will therefore cause a conflict in the RMAN repository, because the restored database with the same DBID will be considered the current target database.
Below you may find the steps:
Preparing the New Host
Record the DBID of the source database.
Copy the initialization parameter file from the source database to the new host.
Make sure that all source database backups are available to the new host. Do not connect to the recovery catalog.
Restoring and Recovering on the New Host
Configure environment variables on the new host.
Connect to the new target database with NOCATALOG.
Set the DBID.
Start the instance with NOMOUNT.
Restore the SPFILE from backup.
Shut down the new instance.
Edit the PFILE.
Start the instance with NOMOUNT (again).
Create an RMAN RUN block to restore the control file.
Create an RMAN RUN block to restore and recover the database.
Open the database with RESETLOGS.
Regards,

Restoring Rman backup on New Host with different directory structure

Hi,
I have a following scenario to clone the database.
1. clone the database on new server
2. source is non - ASM and target is ASM
3. On source incremental level 0 backup taken on disk connecting to catalog, the backup is moved to target host to different directory structure
4. source is running on 32-bit Linux two node Rac and Target is running on 64-bit Linux two node Rac
I did the following steps and getting below error:
1. I copied incremental Level 0 backup to target server(where we need to build new db) to different directory structure
2. On target i created pfile and build the instance, as dbf file are in multiple locations in source i put following tow parameters in init.ora of target database
*.db_file_name_convert =(/u02/oradata/app1p/,+QADATA2/udev/datafile),(/u03/oradata/app1p/,+QADATA1/udev/datafile),(/u12/oradata/app1p/,+QADATA1/udev/datafile,),(/u99/oradata/app1p/,+QADATA1/udev/datafile),(/u09/oradata/app1p/,+QADATA1/udev/datafile),(/u14/oradata/app1p/,+QADATA1/udev/datafile),(/u07/oradata/app1p/,+QADATA1/udev/datafile),(/u06/oradata/prod/,+QADATA1/udev/datafile'),(/u05/oradata/app1p/,+QADATA1/udev/datafile)
*.log_file_name_convert =("/u99/oradata/app1p/","+QADATA2/udev/onlinelog/")
3. connected to rman -->> started db in nomount -->> restored the controlfile --> cataloged the backup piece and then i am trying to restore
All the above steps i did using the Doc id *How To Restore Rman Backups On A Different Node When The Directory Structures Are Different [ID 419137.1]*
script i am using is :
RMAN> run {
2> set until time "to_date('DEC/20/2010 05:30:00','Mon/DD/YYYY HH24:MI:SS')";
3> allocate channel c1 device type disk;
4> allocate channel c2 device type disk;
5> allocate channel c3 device type disk;
6> allocate channel c4 device type disk;
7> set newname for datafile 1 to '+QADATA1/UDEV/DATAFILE';
8> set newname for datafile 2 to '+QADATA1/UDEV/DATAFILE';
9> set newname for datafile 3 to '+QADATA1/UDEV/DATAFILE';
10> set newname for datafile 4 to '+QADATA1/UDEV/DATAFILE';
11> set newname for datafile 5 to '+QADATA1/UDEV/DATAFILE';
12> set newname for datafile 6 to '+QADATA1/UDEV/DATAFILE';
13> set newname for datafile 54 to '+QADATA1/UDEV/DATAFILE';
set newname for datafile 63 to '+QADATA1/UDEV/DATAFILE';
14> 15> set newname for datafile 67 to '+QADATA1/UDEV/DATAFILE';
16> set newname for datafile 68 to '+QADATA1/UDEV/DATAFILE';
17> set newname for datafile 50 to '+QADATA1/UDEV/DATAFILE';
18> set newname for datafile 39 to '+QADATA1/UDEV/DATAFILE';
19> set newname for datafile 38 to '+QADATA1/UDEV/DATAFILE';
20> set newname for datafile 7 to '+QADATA1/UDEV/DATAFILE';
21> set newname for datafile 9 to '+QADATA1/UDEV/DATAFILE';
22> set newname for datafile 8 to '+QADATA1/UDEV/DATAFILE';
23> set newname for datafile 11 to '+QADATA1/UDEV/DATAFILE';
24> set newname for datafile 10 to '+QADATA1/UDEV/DATAFILE';
25> set newname for datafile 66 to '+QADATA1/UDEV/DATAFILE';
26> set newname for datafile 48 to '+QADATA1/UDEV/DATAFILE';
27> set newname for datafile 47 to '+QADATA1/UDEV/DATAFILE';
28> set newname for datafile 12 to '+QADATA1/UDEV/DATAFILE';
29> set newname for datafile 13 to '+QADATA1/UDEV/DATAFILE';
30> set newname for datafile 14 to '+QADATA1/UDEV/DATAFILE';
31> set newname for datafile 15 to '+QADATA1/UDEV/DATAFILE';
32> set newname for datafile 16 to '+QADATA1/UDEV/DATAFILE';
33> set newname for datafile 18 to '+QADATA1/UDEV/DATAFILE';
34> set newname for datafile 17 to '+QADATA1/UDEV/DATAFILE';
35> set newname for datafile 19 to '+QADATA1/UDEV/DATAFILE';
36> set newname for datafile 69 to '+QADATA1/UDEV/DATAFILE';
37> set newname for datafile 60 to '+QADATA1/UDEV/DATAFILE';
38> set newname for datafile 59 to '+QADATA1/UDEV/DATAFILE';
39> set newname for datafile 55 to '+QADATA1/UDEV/DATAFILE';
40> set newname for datafile 53 to '+QADATA1/UDEV/DATAFILE';
41> set newname for datafile 44 to '+QADATA1/UDEV/DATAFILE';
set newname for datafile 22 to '+QADATA2/UDEV/DATAFILE';
42> 43> set newname for datafile 21 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 20 to '+QADATA2/UDEV/DATAFILE';
44> 45> set newname for datafile 72 to '+QADATA2/UDEV/DATAFILE';
46> set newname for datafile 70 to '+QADATA2/UDEV/DATAFILE';
47> set newname for datafile 65 to '+QADATA2/UDEV/DATAFILE';
48> set newname for datafile 64 to '+QADATA2/UDEV/DATAFILE';
49> set newname for datafile 57 to '+QADATA2/UDEV/DATAFILE';
50> set newname for datafile 56 to '+QADATA2/UDEV/DATAFILE';
51> set newname for datafile 49 to '+QADATA2/UDEV/DATAFILE';
52> set newname for datafile 45 to '+QADATA2/UDEV/DATAFILE';
53> set newname for datafile 26 to '+QADATA2/UDEV/DATAFILE';
54> set newname for datafile 25 to '+QADATA2/UDEV/DATAFILE';
55> set newname for datafile 24 to '+QADATA2/UDEV/DATAFILE';
56> set newname for datafile 23 to '+QADATA2/UDEV/DATAFILE';
57> set newname for datafile 27 to '+QADATA2/UDEV/DATAFILE';
58> set newname for datafile 28 to '+QADATA2/UDEV/DATAFILE';
59> set newname for datafile 29 to '+QADATA2/UDEV/DATAFILE';
60> set newname for datafile 30 to '+QADATA2/UDEV/DATAFILE';
61> set newname for datafile 73 to '+QADATA2/UDEV/DATAFILE';
62> set newname for datafile 32 to '+QADATA2/UDEV/DATAFILE';
63> set newname for datafile 31 to '+QADATA2/UDEV/DATAFILE';
64> set newname for datafile 34 to '+QADATA2/UDEV/DATAFILE';
65> set newname for datafile 33 to '+QADATA2/UDEV/DATAFILE';
66> set newname for datafile 35 to '+QADATA2/UDEV/DATAFILE';
67> set newname for datafile 36 to '+QADATA2/UDEV/DATAFILE';
68> set newname for datafile 37 to '+QADATA2/UDEV/DATAFILE';
69> set newname for datafile 51 to '+QADATA2/UDEV/DATAFILE';
70> set newname for datafile 43 to '+QADATA2/UDEV/DATAFILE';
71> set newname for datafile 40 to '+QADATA2/UDEV/DATAFILE';
72> set newname for datafile 41 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 71 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 58 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 52 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 46 to '+QADATA2/UDEV/DATAFILE';
set newname for datafile 42 to '+QADATA2/UDEV/DATAFILE';
73> 74> 75> 76> 77> 78> set newname for datafile 62 to '+QADATA2/UDEV/DATAFILE';
79> set newname for datafile 61 to '+QADATA2/UDEV/DATAFILE';
80> set newname for datafile 74 to '+QADATA2/UDEV/DATAFILE';
81> restore database;
82> switch datafile all;
83> recover database;
84> alter database open resetlogs;
85>
86> release channel c1;
87> release channel c2;
88> release channel c3;
89> release channel c4;
90> }
Getting the following error, copied lines from the error i am getting.
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 27-DEC-10
released channel: c1
released channel: c2
released channel: c3
released channel: c4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 12/27/2010 08:09:08
RMAN-06026: some targets not found - aborting restore
RMAN-06100: no channel to restore a backup or copy of datafile 74
RMAN-06100: no channel to restore a backup or copy of datafile 73
Please advice...
Thanks,
Tanveer Mohammed

If you would like, please refer the link:-
http://gavinsoorma.com/2010/04/creating-an-asm-duplicate-database-from-a-non-asm-database/

Move database to the new server

Hello,
I have 10.2.0.1 Standard Edition database (7GB, not in archivelog mode) on Windows2003 server, and need to move it to the new server (same environment). I thought to use OEM Clone option, but it appears cloning to the other host is working only in Grid - and I have DB Control.
I know about manual cloning/recreation, but now looking into export and import option. So I think to install Oracle database on the new server, then import some relevant tablespaces exported from the old database. I will use datapump utility in OEM, under system username.
Is that a good approach ? What rules should be applied to avoid problems in that case ? Sorry if it's very basic question, never moved database before.
Marina

Options for porting the database from one server to another after installing Oracle on the new server incldue
Export/Import using expdp/impdp
Rman duplicate to compatiable hardware
Rman file conversion to non-compatiable hardware
On advantage of expdp/impdp is this option supports reconfiguring the database tablespace/file/object storage layout as part of the migration. Also the adoption of new features like ASSM.
A disadvantage is that using expdp/impdp will probably be slower and involve more DBA work than using file copies via rman. There are approaches to reduce the clock time necessary to support export/import and the work is often beneficial for long-term database management efforts.
There have been threads on this topic before and failry recently. You might want to hunt one or two of them down.
HTH -- Mark D Powell --

Advice on RAID and backup of new server in CAD office

Hi, I work for an architects firm and we're looking to purchase a new server.
Our current situation:
• Dozen workstations running Leopard, on a gigabit network
• Server running Leopard Server (Standard setup), with one 250GB ATA hard drive (17GB space spare)
• Data files are backed up and taken off site each day with a triple rotation of external hard drives, using Retrospect.
• The server hard drive is cloned to an external drive each week, which stays on site, using SuperDuper.
• User accounts from workstations are all backed up to an external drive, which also stays on site, using Retrospect.
• And I've been trialing Time Machine, backing up the data to an external hard drive, but I can't see this replacing Restrospect backup as Time Machine doesn't compress the files.
To the future:
• What sort of RAID setup should we go for in a new Mac Pro server?
• I'd like to throw it all into performance but I'm thinking we should probably use a RAID to replace our SuperDuper clone from above.
• When you have mirrored drives presumably if one fails the other one just carries on doing all the work by itself?
• Should we run the system on two mirrored drives and the data on the other two? Or if I'm looking for more performance would I be better having 3 mirrored drives for the data and one for the system? Is this even possible?
• Is it possible to get the smaller 73GB SAS drives for the Mac Pros? It seems you can only get the 300GB ones, which are £500 a pop!

Keep in mind that mirrored RAIDs require two similar drives preferably the same make and model. A mirrored RAID only provides drive failure protection, it does not provide data redundancy. If you need a backup then you need two mirrored RAIDs using one to backup the other. This is also true of striped RAIDs which only provide increased storage but provide no protection against drive failure nor provide data redundancy.
These factors should be taken into account when planning your setup.
Personally, I would not recommend using Time Machine. Aside from being fairly basic as a backup utility it is not sufficiently reliable in my opinion for your situation. Retrospect is a much better choice.

Oracle 10.2.0.3 Databases - Restore to New Server

We will soon be replacing an old server with a new server and I need to restore all Oracle 10.2.0.3 databases to the new server
and ensure Oracle functionality/connectivity with all databases.
I am in the process of testing and need advice and hopefully a 'Step by Step' process I can follow.
I am a systems admin - not an Oracle db admin - so please explain details of any commands I may have to run.
I have already tested once:
ran command prompt: sqplus / as sysdba
SQL>shutdown immediate;
Stopped all Oracle services:
Oracle Database
Oracle Listener
Oracle DBConsole
Installed Oracle 10.2.0.3 on new server
Ensured that the SID and all other Oracle services information matched the old server during installation on the new server.
Stopped all Oracle services on the new server (used the steps above).
Backed-up and test restored to new server.
Enterprise Manager shows: Listener Up Database Instance Down Agent Down
Any help would be appreciated

It would be good to know your operation system. I hope both new and old match or similar.
You can use RMAN to dumplicate you DB so you can follow [Creating a Duplicate Database on a New Host. Doc ID: 388431.1|https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=388431.1]
but a simple file system copy based manual duplication is also possible if new and old OS system is similar...

RMAN clone in new server

Similar Messages

Maybe you are looking for