Database duplication

Question

Hi
I'm trying to restore production to a different mount point which is a brand new server.And mount points of the production to that of new server is totally different.
It is 9.2.07 on solaris , both servers have different file systems
SO, I'm little confused about redo logs creation.
I'm restoring it through rman where my backup is on tape.
NOTE:I'm not doing database duplication.I'm restoring the database through rman until certain SCN.
Below is my rman script and steps I've followed till mounting the database.
Steps on NEW server
RMAN > connect target /
connect catalog rman@rman
set dbid=xxxxxxx
startup nomount pfile=$ORACLE_HOME/dbs/intx.ora
Restore controlfil to '/u10/oradata/shark/control01.ctl';
alter database mount;
It worked perfectly till here....
Now My rman scripts looks this way
run{
allocate channel c1 TYPE 'SBT_TAPE';
allocate channel c2 type 'SBT_TAPE';
allocate channle c3 type 'SBT_TAPE';
SEND 'NB_ORA_SERV=clash, NB_ORA_CLIENT=shark';
set newname for datafile 1 to '/u02/oradata/shark/system01.dbf';
set newname for datafile 2 to '/u02/oradata/shark/webuser_data01.dbf';
set newname for datafile 3 to '/u02/oradata/shark/webuser_indx01.dbf';
set newname for datafile 5 to '/u02/oradata/shark/drsys01.dbf';
set newname for datafile 6 to '/u02/oradata/shark/tools01.dbf';
set newname for datafile 7 to '/u02/oradata/shark/users01.dbf';
restore (database);
SWITCH DATAFILE ALL;
I want to do recovery later....
Now whats the status of redo logs ...where would it be created,..since the file system being different where should I mention rman to create the logs....
Please advice..If I'm unclear please do let me know...
Edited by: ORA_DBA2 on May 14, 2009 10:44 AM

Answer 1

ORA_DBA2 wrote:
I'm still get this though I set the parameter
sql ' alter session set sort_area_size=120';
sql ' alter session set sort_area_retained_size=200';
resync got ORA-1220, retrying with sort_area_size = 170MB
resync got ORA-1220, retrying with sort_area_size = 180MB
resync got ORA-1220, retrying with sort_area_size = 190MB
resync got ORA-1220, retrying with sort_area_size = 200MB
resync got ORA--1220, giving upSo how did you arrive at setting sort_area to 120? We see right here that a sort_area_size of 200mb wasn't enough, so your setting of '120' was insufficient from the git-go. And sort_area_retained should generally be the same or smaller than sort_area_size. Read up on both of those in the REFERENCE manual.
Also, I'd set those in the init.ora file that you reference on db startup.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of sql command at 05/14/2009 11:17:45
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of partial resync command on default channel at 05/14/2009 11:17:45
ORA-01220: file based sort illegal before database is open