Rman Duplicate database synchronization problem

Hi
I have the Oracle database 9.2.0.1.0 .I've created Duplicate database on another computer with the same structure and Oracle 9.2.0.1.0 too.
Now, I want to synchronize my duplicate by primary database, and I copied backup of all datafiles & archive logs & and backup that was taken by RMAN, but in the middle of processing I got this error.
printing stored script: Memory Script
set until scn 443620578;
recover
clone database
delete archivelog
executing script: Memory Script
executing command: SET until clause
Starting recover at 31-MAR-03
starting media recovery
channel ch1: starting archive log restore to default destination
channel ch1: restoring archive log
archive log thread=1 sequence=106
channel ch1: restored backup piece 1
piece handle=C:\ORACLE\ORA9I\DATABASE\23EJCO3D_1_1 tag=TAG20030331T114405 params=NULL
channel ch1: restore complete
archive log filename=C:\ORACLE\ORADATA\DELLDUP\ARCHIVE\DELLDUPT001S00106.ARC thr
ead=1 sequence=106
channel clone_default: deleting archive log(s)
archive log filename=C:\ORACLE\ORADATA\DELLDUP\ARCHIVE\DELLDUPT001S00106.ARC rec
id=1 stamp=490112362
media recovery complete
Finished recover at 31-MAR-03
printing stored script: Memory Script
shutdown clone;
startup clone nomount ;
executing script: Memory Script
RMAN-00571:===============================================
RMAN-00569: ===============ERROR MESSAGE STACK FOLLOWS
RMAN-00571:===============================================
RMAN-03002: failure of Duplicate Db command at 03/31/2003 15:20:53
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01013: user requested cancel of current operation
What should I Do?
tx

I beleive... and correct me if I'm wrong, but the duplicate command will open the db created with RESET LOGS. Thereby meaning you can't use the archive logs.

Similar Messages

Problems creating control file in RMAN duplicate database

There is so much detail involved in this operation that I don't know what might be useful, so I'll start simple. I'm attempting to clone a database on the same host using RMAN "duplicate database". I finally got all the setup done, the OS authentication hurdles hurdled, etc. and entered the command:
duplicate target database to COPYCH2M until time "to_date('March 15 2012 12:00:00', 'Mon DD YYYY HH24:MI:SS')";
The first time I got:
ORA-19504: failed to create file "/u01/app/oracle/oradata/COPYCH2M/control01.ctl"
ORA-27040: file create error, unable to create file
Linux-x86_64 Error: 2: No such file or directory
There was nothing in the Oracle instructions about manually creating the directory, but I did so, thinking that might be the problem. And it created the control files! But then I got the following:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/21/2012 15:59:25
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-00201: control file version 11.2.0.0.0 incompatible with ORACLE version 11.1.0.1.0
ORA-00202: control file: '/u01/app/oracle/oradata/COPYCH2M/control01.ctl'
Sounds straightforward, if frustrating, right? Apparently you can't duplicate a database that's not in the exact same version. But:
1) The backuppiece we got the control file from was from last November.
2) The version of Oracle has not been updated since that time.
How can a file created by this version be incompatible with this version? Where is it even getting 11.1?
Thanks, I'm hoping this is easy but I can post more info if needed.

>
There was nothing in the Oracle instructions about manually creating the directory, but I did so, thinking that might be the problem. And it created the control files! But then I got the following:
>
The database is limited as to what it can create. Since you defined where you wanted the controlfiles to go (pfile/spfile), it's up to you to make sure the directory is valid and exists. :)
>
How can a file created by this version be incompatible with this version? Where is it even getting 11.1?
>
As for your controlfiles, make sure the compatible parameter is set the same on both the source and the target unless you are using the default (11.1.0.1 for you, and you aren't)
Keep going, you'll get there. RMAN duplicate is a great feature.
Good luck.

RMAN duplicate Database

Hi ALL,
While doing duplicate database using RMAN i m getting following error.
released channel: d1
RMAN-00571: =================================
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ======
RMAN-00571: =======================================
RMAN-03002: failure of Duplicate Db command at 05/14/2008 08:08:23
RMAN-03015: error occurred in stored script Memory Script
ORA-06550: line 1, column 1730:
PLS-00302: component 'LOGTERMINAL_OBJ' must be declared
ORA-06550: line 1, column 1716:
PL/SQL: Statement ignored
Recovery Manager complete.
Please Help
Regards
Mital

thanks Werner for reply ,
the above problem is solved, the proble was that you have said. the problem was realted to version . the target db was of 10.2.0.3 and the rman aux db is at 10.2.0.4
i have changed auxiliary db to 10.2.0.3 and the problem is resolved.
but now i am facing some diff. error.
setup:
backup server :\\bkpsvr\backup$\
backup location : \\bkpsvr\backup$\
target server \\tgt_svr
auxiliary server :\\aux_svr\ :
restore location : G:\ORACLE\ORADATA\ERPBI2DV\
during duplicate db commad while reading from backup piece it is givnig following error.
ORA-19870: error reading backup piece \\BRNORA10\BACKUP$\BI2\DF_ERPBI2_654625830_4599_1
ORA-19504: failed to create file "G:\ORACLE\ORADATA\ERPBI2DV\OWB_ERPBI2DV_01"
ORA-27040: file create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
released channel: d1
RMAN-00571: ==============================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ======================================
RMAN-03002: failure of Duplicate Db command at 05/14/2008 12:39:14
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 100 found to restore
RMAN-06023: no backup or copy of datafile 99 found to restore
please help.
Message was edited by:
mits

Duplicate database synchronize

I have duplicated the database “prod” to “dup”.
$rman target sys/oracle@ORIGDB auxiliary /
RMAN> duplicate target database to DUP nofilenamecheck;
My question is in order to synchronize the duplicate database from time to time, do I need to drop the duplicate database first and then re-run the “RMAN> duplicate target database to DUP;” command?

You don't have to drop the database first.
Shutdown and then start in nomount before you run the duplicate command.

RMAN duplicate database suddenly slow

Hi Everyone,
I posted at wrong forum last time, sorry about that.
I used RMAN to duplicate database to different box in the same local network area. Here are the scenario:
boxA: target database (PROD) -- 250G
database:Oracle 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
OS:Windows Server 2003 Enterprise x64 Edition
boxB: cloned database
database:Oracle 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
OS:Windows Server 2003 Enterprise x64 Edition
After prepared necessary steps,listener and tnsnames,etc, I run the following scripts:
C:\>rman target sys/[email protected] auxiliary sys/[email protected] catalog rman/rman
RMAN>RUN
SET NEWNAME FOR DATAFILE 1 TO 'D:\oracle\undb\system01.dbf';
.... (some set newname omitted here)
SET NEWNAME FOR DATAFILE 15 TO 'D:\oracle\undb\RMAN01.ORA';
SET NEWNAME FOR TEMPFILE 1 TO 'D:\oracle\undb\TEMP01.ORA';
# to manually allocate three auxiliary channels for disk issue
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
ALLOCATE AUXILIARY CHANNEL aux3 DEVICE TYPE DISK;
DUPLICATE TARGET DATABASE TO undb
LOGFILE
GROUP 1 ('D:\oracle\undb\redo01.log') SIZE 100M REUSE,
GROUP 2 ('D:\oracle\undb\redo02.log') SIZE 100M REUSE,
GROUP 3 ('D:\oracle\undb\redo03.log') SIZE 100M REUSE;
database duplicated successfully last week.
Monday, I created another database in boxA (testdb) and used the similiar scripts (just made necessary changed, database name,file names,etc), and the duplication also successful.
Yesterday, I tried to duplicate PROD, did the exactly same thing as Monday,
everything was very slow,
RMAN>report schema; took over 30 minutes,
RMAN>list backup;took another 30 minutes,
then I delete testdb in boxA, nothing better.
I have tried from boxA, also tried from boxB, things were similiar.
(when test from boxB, I input: rman target sys/[email protected] auxiliary sys/[email protected] catalog rman/[email protected] )
when I input:
RMAN> report schema;
and checked from Enterprise Manager,
SELECT RECID , STAMP , THREAD# , SEQUENCE# , FIRST_CHANGE# LOW_SCN , FIRST_TIME LOW_TIME , NEXT_CHANGE# NEXT_SCN ,
RESETLOGS_CHANGE# , RESETLOGS_TIME FROM V$LOG_HISTORY WHERE RECID BETWEEN :1 AND :1 AND RESETLOGS_TIME IS NOT NULL
AND STAMP >= :1 ORDER BY RECID
the query is running for a long time, my V$LOG_HISTORY has 18688 rows, select count(*) from V$LOG_HISTORY took less than 1 second.
I am wondering what is the reason?
Can anybody give me a clue?
Thank you very much.

Thanks Alan,
Hardware spec:
duplicate database server CPU: 2x1995 Mhz ,RAM:4G, hard disk 500G
production server CPU: 2x2993 Mhz ,RAM:5G,hard disk 900G
the production server is better than the duplicate server. the production only run Oracle 10g server, the duplicate server is brand new and nothing is runing except Windows and Oracle software only.
I noticed that when in peek hour, RMAN is really slow, no matter which box I run the RMAN, when in non peek hour, it's reasonable.
Is there anything I can do on the RMAN side?
Thanks again

Rman duplicate database from test to production different host

Dear All,
usually i do the rman duplicate (clone) database in different host using same backup location as the source database in target database.
now i am in situation to clone the database with different backup location
source database location:/u01/db/backup
target database location: /tmp_dbbkup
is it possible to create the duplicate database with the command
rman target sys@UAT1 auxiliary /
RMAN>CATALOG BACKUPPIECE '/tmp_dbbkup/UAT_2670198561_44_20110101;
RMAN>duplicate target database to DEV;
is it ok?
we dont have privilege/rights to create a folder/directory in production server.
what i have to do now?
thanks in advance.
my oracle version: 10.2.0.4.0
operating system: AIX

tychos wrote:
Hi rajeysh,
what i have to do now?You could make a sym link on the dev server
So /u01/db/backup on the dev server points to /tmp_dbbkup
Regards,
Tychothank for your reply tychos,
$ ln -s /u01/db/backup/OUAT_2670198561_44_20110101 /oracle/db/backup/UAT_2670198561_44_20110101
$ ls -ltr
total 1475968
-rw-r----- 1 oracle dba 307654656 Jan 7 10:03 db_DEV_20110107_4em1gm3e_1_1_L0
-rw-r----- 1 oracle dba 448030720 Jan 7 10:03 db_DEV_20110107_4dm1gm3e_1_1_L0
lrwxrwxrwx 1 oracle dba 45 Jan 11 20:53 UAT_2670198561_44_20110101 -> /u01/db/backup/OUAT_2670198561_44_20110101
$ ln -s /u01/db/backup/AOUAT_2670198561_46_20110101 /oracle/db/backup/OUAT_2670198561_46_20110101
$ ln -s /u01/db/backup/OUAT_2670198561_47_20110101 /oracle/db/backup/OUAT_2670198561_47_20110101
$ ln -s /u01/db/backup/OUAT_2670198561_45_20110101 /oracle/db/backup/OUAT_2670198561_45_20110101
$
is it ok
will the duplicate gets the information from /oracle/db/backup
if i did anything wrong , please correct me?

RMAN target database Connectivity problem

Error while connecting to target database also tried as sys user but same error
C:\>rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Sep 10 11:06:31 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04005: error from target database:
ORA-01031: insufficient privileges

You can try like this
rman target 'DBNAME'
or set ORACLE_SID=DBNAME
then rman target /
Do you multiple oracle homes?
Is it in windows or in Unix
IF it is unix you should login as ORACLE user and execute the commands
Theuser should have the SYSDBA privilge
In windows the user excuting the command the user should be a part of the ORA_DBA group
Edited by: Maran Viswarayar on Sep 10, 2008 1:34 PM

DUPLICATE DATABASE giving problems

I donot know what I am doing wrong, can anybody please assist me with duplicating target database to my auxiliary database?
@9:00 pm - Full Backup and Database is in Archivelog mode.
next day around 11am I tried to close my auxiliary database. I copied all the backup files from last night full backup plus the 10 archive log files which I needed.
when I issue SET UNTIL LOG SEQUENCE = 5546 because this is where I want to stop.
RMAN ask me the full backup file from "a day before yesterday's backup"
for example today is tuesday and at 11am I am cloning my database by using monday's full backup plus the archive logs generated since then. why do I need backup file from Sunday?
any clue?
Thanks for any suggestion!
Data Sheet

Hi,
go through below link
http://dbataj.blogspot.com/2006/12/duplicating-database-with-recovery.html
hope this helps
Taj

Problems with DUPLICATE DATABASE when datafile was added after full backup

Hi,
I'm facing a problem when performing database duplication with the RMAN duplicate database command on a 10g database. If I preform the duplication from a full backup that is missing a datafile which was added to the database after the full backup, I get the following error message:
Starting restore at 10-10-2009 18:00:38
released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/10/2009 18:00:39
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06100: no channel to restore a backup or copy of datafile 43The redo log which was CURRENTat the time of the datafile's 43 creation is also available in the backups. It seems like RMAN can't use the information from the archived redo logs to reconstruct the contents of datafile 43. I suppose that because the failure is reported already in the RESTORE and not in the RECOVER phase, so the archived redo logs aren't even accessed yet. I get the same message even if I make a separate backup of datafile 43 (so a backup that is not in the same backupset as the backup of all other datafiles).
From the script the duplicate command produces, I guess that RMAN reads the contents of the source database's controlfile and tries to get a backup which contains all the datafiles to restore them on the auxiliary database - if such a backup is not found, it fails.
Of course if I try to perform a restore/recover of the source database it works without problems:
RMAN> restore database;
Starting restore at 13.10.09
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
creating datafile fno=43 name=F:\ORA10\ORADATA\SOVDEV\SOMEDATAFILE01.DBF
channel ORA_DISK_1: starting datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to F:\ORA10\ORADATA\SOVDEV\SYSTEM01.DBF
.....The datafile 43 is recreated and then redo is applied over.
So, does anyone know if duplicate database can't use archived redo logs to recreate the contents of a datafile as a normal restore/recover does? If it's so, then it means it's necessary to perform a full database backup before every run of duplicate database if a datafile was added after such a backup.
Thanks in advance for any answers.
Regards,
Jure

Hi Jure,
I have hit exactly the same problem during duplication.
Because we backup the archive logs every 6 hours with rman I added an extra run block to this script.
run
backup incremental level 0
format 'bk_%d_%s_%p_%t'
filesperset 4
database not backed up;
(I also than hit a bug in the catalog which was solved by patching up the catalog dbs from 11.1.0.6 to 11.1.0.7.)
This will narrow down the datafile not being part of any rman backup to 6 hours while skipping datafiles for which a backup already exists.
Regards,
Tycho

Duplicate database from active database in 11g?

Does anyone know if it's possible to clone a database from stby by issuing RMAN duplicate database FROM ACTIVE DATABASE command in 11g?
I know it's possible from primary to create stby.
Thanks in advance

You may have run into the same problem like I did recently:
The (UR=A) clause in tnsnames.ora is intended to work with a dynamically registered handler so the use of SERVICE_NAME versus SID is preferred.
ORA-12528: TNS listener BLOCKED - trying to duplicate database
Also for further problems:
RMAN 11gR2 duplicate database ORA-17627 ORA-01017 RMAN-03009 ORA-17628

File rename on rman duplicate

Oracle 11.2.0.2 SE-One 64-bit
Oracle Linux 5.6 x86-64
Question I had never considered. When performing an rman duplicate database with no NEWNAME parameters in sight, how does rman know how to set new names? There is something more than just the init parm “db_create_file_dest”.
The setup:
Server SRVPRD,
- ASM instance
- database DBPRD , has files in diskgroups SAN and SMALL
Server SRVDEV
- ASM instance
- database DBSTG, has files in diskgroups LARGE and SMALL
- database DBDEV, has files in diskgroups DEV_LARGE and DEV_SMALL
Shell script on SRVDEV to replicate DBPRD to DBSTG.   Script ftp’s the rman backups from SRVPRD, shuts down the instance DBSTG, deletes all of its files using asmcmd commands, then executes the following:
echo "connect catalog rman/********@rmcat"       > /backup/dbstgvb/dbstgvb_refresh.rman
echo "connect target sys/********@srvprd"       >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "connect auxiliary /"                      >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "run {"                                    >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "set until time \"to_date('`date +%Y-%m-%d` 12:38:00','YYYY-MM-DD hh24:mi:ss')\";" >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "duplicate target database to DBSTGVB;"    >> /backup/dbstgvb/dbstgvb_refresh.rman
echo "}"                                        >> /backup/dbstgvb/dbstgvb_refresh.rman
$ORACLE_HOME/bin/rman < /backup/dbstgvb/dbstgvb_refresh.rman
It runs perfectly and the files that were in the +SAN diskgroup in prod are correctly placed in +LARGE, and the files that were in +SMALL are correctly placed in +SMALL.
Now a new requirement to start doing the same for DBDEV. Made a copy of the script and changed all references from DBSTG to DBDEV. Equivalent changes in the string of asmcmd commands that delete the files, specifying the correct specific disk groups.
With this one, instead of mapping files from the two disk groups in DBPRD to the two diskgroups in DBDEV, they all get put into the one disk group +DEV_SMALL.
On DBSTG, we see
SQL> show parameter db_create_file_dest
NAME TYPE VALUE
db_create_file_dest     string +SMALL
and the rman log output of the replication includes this:
database mounted
contents of Memory Script:
   set until scn 2984496;
   set newname for datafile 1 to
"+SMALL/dbstgvb/system01.dbf";
   set newname for datafile 2 to
"+SMALL/dbstgvb/sysaux01.dbf";
   set newname for datafile 3 to
"+SMALL/dbstgvb/undotbs01.dbf";
   set newname for datafile 4 to
"+SMALL/dbstgvb/users01.dbf";
   set newname for datafile 5 to
"+LARGE/dbstgvb/perfstat_01.dbf";
   set newname for datafile 6 to
"+LARGE/dbstgvb/dw_tbs1.dbf";
   restore
   clone database
executing Memory Script
On DBDEV we see
SQL> show parameter db_create_file_dest
NAME TYPE VALUE
db_create_file_dest     string +DEV_SMALL
and the rman log output of the replication includes this:
database mounted
contents of Memory Script:
   set until scn 2984496;
   set newname for clone datafile 1 to new;
   set newname for clone datafile 2 to new;
   set newname for clone datafile 3 to new;
   set newname for clone datafile 4 to new;
   set newname for clone datafile 5 to new;
   set newname for clone datafile 6 to new;
   restore
   clone database
executing Memory Script
So, I am missing exactly how it is that in the replicate to DBSTG, it is able to correctly identify that files coming from prod diskgroup SAN correctly mapped to diskgroup LARGE? And further, why that mechanism did not work to map to +DEV_LARGE when replicating to DBDEV. In DBDEV it seems to be controlled entirely by db_create_file_dest, but in DBSTG there seems to be something that I am missing that allows the greater complexity of mapping two diskgroups.

Interesting side observation
In making sure all files ended up in the correct location I started noticing differences in the FQFN from the source db to the target.   Doing an asmcmd 'ls -l' on both systems, I discovered things like this:
On the source db, we have
DW_TBS1.dbf => +SAN/DBPRD/DATAFILE/DW_TBS.278.755044731
while on the target it came out
dw_tbs1.dbf => +LARGE/DBSTG/DATAFILE/DW.259.821974713
or
STAGE_CUST_ACCT_I1.ora => +SAN/DBPRD/DATAFILE/STAGE_CUST_ACCT_I.262.754925519
vs
stage_cust_acct_i1.ora => +LARGE/DBSTG/DATAFILE/STG_CUST_ACCT_IDX.266.822009311
Obviously not an operational problem, but a curiosity about the algorithm to generate the base part of the FQFN, and why it generated different names on different systems.

Rman duplicate vs. imp/exp

I try to use rman duplicate database to bring entire databse form Windows XP system to another Windows XP.
I have been trying to use rmain duplicate database without success.
I failed on "startup force nomount......". The system always prompt
me an error as "ORA-12514: TNS:listener does not currently know of service requested in connect descriptor" and following by
TNSLSNR.exe has encountered a problem and need to be close......"
I have tried to re-install the oracle multiple times and failed at
the same problem as above.
So, I am thinking of using imp and exp to do the work. Is it possible? If yes, how to do it.
Thanks

IMP/EXP is not a solution. Fixing the problem you have created is the solution.
This error message is self-explanatory ... you did not create a listener service.
This error message is also one of the most common on the internet and google or OTN forums have answered questions on this thousands upon thousands of times.
Last time I looked ... netca ... creates services in all versions of the Oracle database.

Why do we use RMAN DUPLICATE for cloning DB on a different server ?

DB version : 11.2.0.2, 10.2.0.5
I want to create a clone of my Production DB in a test server. In the past, I have taken hot backup of this production DB and restored and recovered it in a different server using plain RMAN commands.
After restoring the control file , mounting the DB and cataloging the backup pieces in the test server , I run
run {
restore database ;
recover database until time <time> ;
alter database open resetlogs ;
}In OTN , i came across long running discussions like
RMAN duplicate database
where they are trying to restore and recover using DUPLICATE command as shown below.
run
duplicate target database to RBS
nofilenamecheck
pfile=/tmp/aux.ora;
Can't they just use plain RMAN restore and recover commands as I did ? What advantage does RMAN DUPLICATE have over the plain commands ?

RMAN DUPLICATE is designed to give to clone database a new database name and new database identifier:
>
If you copy a database with operating system utilities instead of the DUPLICATE command, then the DBID of the copied database remains the same as the original database. To register the copy database in the same recovery catalog with the original, you must change the DBID with the DBNEWID utility (see Oracle Database Utilities). In contrast, the DUPLICATE command automatically assigns the duplicate database a different DBID so that it can be registered in the same recovery catalog as the source database.

Duplicate database from Linux to sun

Hi All,
RMAN duplicate database from Linux 5.2 (Tikanga) to sun 5.9 is possible, please share link or doc.

Thanks for reply.
But confused to Capture ENDIAN_FORMAT
1-
uname -a gives below SUN OS detail,
SunOS 5.9 Generic_122300-51 sun4u sparc SUNW,Sun-Fire-V490
and in oracle i am getting below 4 records,so please help me which would be my SUN flavour from below list.
PLATFORM_NAME ENDIAN_FORMAT
Solaris[tm] OE (32-bit) Big
Solaris[tm] OE (64-bit) Big
Solaris Operating System (x86) Little
Solaris Operating System (x86-64) Little
2-
uname -a
Linux *** 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
SQL> select platform_name, endian_format from V$TRANSPORTABLE_PLATFORM where platform_name like '%Linux%';
PLATFORM_NAME ENDIAN_FORMAT
Linux IA (32-bit) Little
Linux IA (64-bit) Little
Linux x86 64-bit Little
please help me which would be my Linux flavour from above list.

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 Duplicate database synchronization problem

Similar Messages

Maybe you are looking for