Error Duplicating Target Database

Dear DBA's
RH 4
Oracle 9.2.0.8
When I start duplicating my target database with script below everything goes fine until the recover :
RMAN> run
2> {
3> allocate auxiliary channel ch1 type sbt;
4> set newname for datafile 1 to '/u02/oradata/SIEBDEV/system/system01.dbf';
5> set newname for datafile 2 to '/u02/oradata/SIEBDEV/system/undotbs01.dbf';
6> set newname for datafile 3 to '/u03/oradata/SIEBDEV/index/tbs_igd_index01.dbf';
7> set newname for datafile 4 to '/u01/oradata/SIEBDEV/data/dm_casebase_docbase_01.dbf';
8> set newname for datafile 5 to '/u01/oradata/SIEBDEV/data/dm_imdoc_audit_01.dbf';
9> set newname for datafile 6 to '/u01/oradata/SIEBDEV/data/dm_imdoc_docbase_01.dbf';
10> set newname for datafile 7 to '/u01/oradata/SIEBDEV/data/tbs_siebdw_data_01.dbf';
11> set newname for datafile 8 to '/u01/oradata/SIEBDEV/data/tbs_dwhview_01.dbf';
12> set newname for datafile 9 to '/u01/oradata/SIEBDEV/data/tbs_igd_01.dbf';
13> set newname for datafile 10 to '/u01/oradata/SIEBDEV/data/igd_eim_01.dbf';
14> set newname for datafile 11 to '/u01/oradata/SIEBDEV/data/TBS_SIEBEL_EMPTY.dbf';
15> set newname for datafile 12 to '/u01/oradata/SIEBDEV/data/tbs_siebel_data_01.dbf';
16> set newname for datafile 13 to '/u01/oradata/SIEBDEV/data/tools_01.dbf';
17> set newname for datafile 14 to '/u01/oradata/SIEBDEV/data/users_01.dbf';
18> set newname for datafile 15 to '/u01/oradata/SIEBDEV/data/perfstat_01.dbf';
19> set newname for datafile 16 to '/u03/oradata/SIEBDEV/index/tbs_siebdw_index_01.dbf';
20> set newname for datafile 17 to '/u03/oradata/SIEBDEV/index/tbs_siebbig_index01.dbf';
21> set newname for datafile 18 to '/u03/oradata/SIEBDEV/index/dm_casebase_index_01.dbf';
22> set newname for datafile 19 to '/u03/oradata/SIEBDEV/index/dm_imdoc_index_01.dbf';
23> set newname for datafile 20 to '/u03/oradata/SIEBDEV/index/tbs_siebel_index_01.dbf';
24> set newname for datafile 21 to '/u01/oradata/SIEBDEV/data/dm_casebase_audit_01.dbf';
25> set newname for datafile 22 to '/u01/oradata/SIEBDEV/data/tbs_siebview_01.dbf';
26> set newname for datafile 23 to '/u01/oradata/SIEBDEV/data/invoice_app_data01.dbf';
27> set newname for datafile 24 to '/u03/oradata/SIEBDEV/index/tbs_invoice_index01.dbf';
28> DUPLICATE TARGET DATABASE TO SIEBDEV
29> NOFILENAMECHECK
30> PFILE = $ORACLE_BASE/admin/SIEBDEV/initSIEBDEV.ora
31> LOGFILE GROUP 1 ('/u01/oradata/SIEBDEV/rdo/sibdevredog1m1.log',
32> '/u02/oradata/SIEBDEV/rdo/sibdevredog1m2.log',
33> '/u03/oradata/SIEBDEV/rdo/sibdevredog1m3.log') SIZE 104857600,
34> GROUP 2 ('/u01/oradata/SIEBDEV/rdo/sibdevredog2m1.log',
35> '/u02/oradata/SIEBDEV/rdo/sibdevredog2m2.log',
36> '/u03/oradata/SIEBDEV/rdo/sibdevredog2m3.log') SIZE 104857600,
37> GROUP 3 ('/u01/oradata/SIEBDEV/rdo/sibdevredog3m1.log',
38> '/u02/oradata/SIEBDEV/rdo/sibdevredog3m2.log',
39> '/u03/oradata/SIEBDEV/rdo/sibdevredog3m3.log') SIZE 104857600;
40> }
executing command: SET until clause
Starting recover at 20-APR-10
starting media recovery
archive log thread 1 sequence 19 is already on disk as file /u03/archive/SIEBTEST/SIEBTEST_19.arc
archive log thread 1 sequence 20 is already on disk as file /u03/archive/SIEBTEST/SIEBTEST_20.arc
archive log thread 1 sequence 21 is already on disk as file /u03/archive/SIEBTEST/SIEBTEST_21.arc
channel ch1: starting archive log restore to default destination
Finished recover at 20-APR-10
printing stored script: Memory Script
shutdown clone;
startup clone nomount pfile= '$ORACLE_BASE/admin/SIEBDEV/initSIEBDEV.ora';
executing script: Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 3410991136 bytes
Fixed Size 747552 bytes
Variable Size 1040187392 bytes
Database Buffers 2348810240 bytes
Redo Buffers 21245952 bytes
input datafilecopy recid=23 stamp=716818426 filename=/u03/oradata/SIEBDEV/index/tbs_invoice_index01.dbf
printing stored script: Memory Script
Alter clone database open resetlogs;
executing script: Memory Script
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03004: fatal error during execution of command
RMAN-10039: error encountered while polling for RPC completion on channel clone_default
RMAN-10006: error running SQL statement: select act from x$ksusex where sid=:1 and serial=:2
RMAN-10002: ORACLE error: ORA-03113: end-of-file on communication channel
RMAN-03002: failure of Duplicate Db command at 04/20/2010 12:13:53
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database:
ORA-01092: ORACLE instance terminated. Disconnection forced
I don't understand what is wrong?
When I check the Alert.log it shows the tablespace UNDOTBS1 doesn't exist !!!!!!!
Tue Apr 20 12:13:51 2010
SMON: enabling cache recovery
Tue Apr 20 12:13:52 2010
Errors in file /u01/app/oracle/admin/SIEBDEV/udump/siebdev_ora_14220.trc:
ORA-30012: undo tablespace 'UNDOTBS1' does not exist or of wrong type
Tue Apr 20 12:13:52 2010
Error 30012 happened during db open, shutting down database
USER: terminating instance due to error 30012
Instance terminated by USER, pid = 14220
ORA-1092 signalled during: alter database open resetlogs...
Please Help...
This dupliaction took me 1 week and crashed me the Test Databases.
Thxs if you can Help.
Bests Carlos

But The UNDOTBS1 is in the ispfile
SQL> startup mount
ORACLE instance started.
Total System Global Area 3410991136 bytes
Fixed Size 747552 bytes
Variable Size 1040187392 bytes
Database Buffers 2348810240 bytes
Redo Buffers 21245952 bytes
Database mounted.
SQL> show parameters undo
NAME TYPE VALUE
undo_management string AUTO
undo_retention integer 18000
undo_suppress_errors boolean TRUE
undo_tablespace string UNDOTBS1
SQL>
SQL>
SQL> select INSTANCE_NAME,STATUS,DATABASE_STATUS,INSTANCE_ROLE from v$instance;
INSTANCE_NAME STATUS DATABASE_STATUS INSTANCE_ROLE
SIEBDEV MOUNTED ACTIVE PRIMARY_INSTANCE
SQL> select NAME,CREATED,OPEN_MODE,ACTIVATION# from v$database;
NAME CREATED OPEN_MODE ACTIVATION#
SIEBDEV 20-APR-10 MOUNTED 2834443258
SQL> r
1* select FILE#,STATUS,ENABLED,NAME from v$datafile
FILE# STATUS ENABLED NAME
1 SYSTEM DISABLED /u02/oradata/SIEBDEV/system/system01.dbf
2 ONLINE DISABLED /u02/oradata/SIEBDEV/system/undotbs01.dbf
3 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_igd_index01.dbf
4 ONLINE DISABLED /u01/oradata/SIEBDEV/data/dm_casebase_docbase_01.dbf
5 ONLINE DISABLED /u01/oradata/SIEBDEV/data/dm_imdoc_audit_01.dbf
6 ONLINE DISABLED /u01/oradata/SIEBDEV/data/dm_imdoc_docbase_01.dbf
7 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_siebdw_data_01.dbf
8 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_dwhview_01.dbf
9 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_igd_01.dbf
10 ONLINE DISABLED /u01/oradata/SIEBDEV/data/igd_eim_01.dbf
11 ONLINE DISABLED /u01/oradata/SIEBDEV/data/TBS_SIEBEL_EMPTY.dbf
FILE# STATUS ENABLED NAME
12 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_siebel_data_01.dbf
13 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tools_01.dbf
14 ONLINE DISABLED /u01/oradata/SIEBDEV/data/users_01.dbf
15 ONLINE DISABLED /u01/oradata/SIEBDEV/data/perfstat_01.dbf
16 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_siebdw_index_01.dbf
17 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_siebbig_index01.dbf
18 ONLINE DISABLED /u03/oradata/SIEBDEV/index/dm_casebase_index_01.dbf
19 ONLINE DISABLED /u03/oradata/SIEBDEV/index/dm_imdoc_index_01.dbf
20 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_siebel_index_01.dbf
21 ONLINE DISABLED /u01/oradata/SIEBDEV/data/dm_casebase_audit_01.dbf
22 ONLINE DISABLED /u01/oradata/SIEBDEV/data/tbs_siebview_01.dbf
FILE# STATUS ENABLED NAME
23 ONLINE DISABLED /u01/oradata/SIEBDEV/data/invoice_app_data01.dbf
24 ONLINE DISABLED /u03/oradata/SIEBDEV/index/tbs_invoice_index01.dbf
As you can see datafiles are there.
I don't get why the recover Fails.
Any clues?
thxs

Similar Messages

RMAN-04005: error from target database:

Hi,
when I want register my target by
]$ rman catalog prdrman/prdrman@PRD target sys/manager@DEV
I receive this :
RMAN-04005: error from target database:
ORA-01031: insufficient privileges
Do you have any idea ?
Many thanks before.

Here are some further hints from documentation:
ORA-01031: insufficient privileges
When : SQL> connect sym/sym as SYSDBA
Additional : init.ora remote_login_passwordfile=EXCLUSIVE or SHARED
Cause : Username/password is not correct (if the user is added by granting
SYSDBA to the user, this user is added to the passwordfile with the
password from the data dictionary)
or:
Password file has
-> incorrect name orapw<name_of_database>
-> is not in $ORACLE_HOME/dbs
-> has wrong privileges
They should be -rwSr-----
For example:
-rwSr----- 1 server sdb 1536 Mar 25 08:12 orapwv901
Solve : You can set the correct privileges (Unix) by issueing
$ chmod 4640 passwordfile
As a last resort, recreate the password file and remind to add
additional privileged (sysdba or sysoper) users

Error: The target database JDBC driver class cannot be loaded

Hi
We have a GTC DB connector deployed and configured in one environment. We are able to provision the users to DB table in that environment.
Then we have taken export of all related data objects(like IT Resource, Resource Obj, Process Defs, Adapter tasks, etc) and imported to another environment.
In this environment we changed the conn parameters in IT resource and made sure that all the files has been copied to respective folders under Xellerate.
When ever we try to provision user to the DB it throws an error message as The target database JDBC driver class cannot be loaded as a response and the create user task is rejected.
Database: MS SQL Server.
App Server: WebSphere App Server 6.1
OIM: 9.1.0.1
Does any one faced this type of issue??
Thanks

Thanks lot for the quick response.
I have copied the sqljdbc.jar file to the ThirdParty folder and restarted in App server. Now that the earlier error "The target database JDBC driver class cannot be loaded" is not appearing while provisioning in the rejected task.
I am getting a new error "GCPROV.ProvTransportProvider.DBProvisioningTransport.DB_GET_CONNECTION_ERROR".
Can you please let me know the reason for this. All the connections parameters are correct to connect to the target databse.
Waiting for the response.

Connecting to Catalog & Target Database

I am trying to register a target database with a recovery catalog. RMAN database and the catalog table space were created. When trying to connect to target with the SID set to the instance name and simply connecting as username/password, I am getting connected to the target. If I try to connect using the connect string, I get the following error
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-12154: TNS:could not resolve service name
But the TNS names have been properly configured and I am able to connect from sql*plus using the connect string.
Similarly I set the SID to RMAN database and try to connect catalog with username/password I am able to connect to Catalog and if I use connect string for the target, I am getting the same error as mentioned above.
I really do not know, How to resolve this and to connect to Target and RMAN databases simultaneously.

I suggest you do the following to see if the connect strings are really working, either:
1) Change ORACLE_SID to be of the catalog database, now do:
% sqlplus "<user>/<pwd>@<target string> as sysdba"
Does that work? If as I suspect it does not work or connects you to the catalog database (not the target), then it is a missconfiguration of the network files.
2) Do the same for connection to the catalog, set ORACLE_SID to be the one of the target database and do:
% sqlplus "<user>/<pwd>"
Does that connects you to the catalog?

Getting ORA-01031 while connecting to target database

I have created RMAN catalog. While connecting to target database i am getting ORA-01031: insufficient privileges. What could be the reason. I have added entry of both the databases in listner.ora as well as tnsnames.ora, but still facing the same problem. Please help
[oracle@dbapool ~]$ rman catalog=rman/pass@sdn target=sys/pass@sdn1
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Apr 30 23:49:46 2010
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

Issue got resolved. The problem was with password file.

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

Old atcsn value from target database

database version: 11.2.0.4.0
goldengate version: 12.1.0.2.0
OS: SunOs 5.10
Hello guys I have a scenario.
I start the primary extract & datapump extract
(primary extract)
          register extract <extract group name> database
          add extract <extract group name>, integrated tranlog, begin now
          add exttrail <extract trail path>, extract <extract name>
          start extract <extract group name>
(datapump extract)
          add extract <datapump extract name>, exttrailsource <extract trail path>
          add rmttrail <remote trail path>, extract <datapump extract name>
          start extract <datapump extract name>
and after I start the primary extract & datapump extract, for the initial load I take an export datapump with flashback_scn=<some_value> from the source database.
I import the data into the target database and I start the replicat
(replicat)
          add replicat <replicat group name>, integrated extrail <extract trail path>
          start replicat <replicat group name>, atcsn <flashback_scn value given in datapump export>
Now my question if I want to start the replicat after one week, and I start it with the atcsn taken during the export datapump for initial load (which was taken one week ago), how would the replicat start if that scn is not present in the source database?
Thank You

DBA2008 wrote:
oracle:tulpcorpadb03$ rman TARGET sys/*****@wcmp AUXILIARY /
Recovery Manager: Release 9.2.0.8.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. 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
I findout this, this is prod db and not allowed to bounce to change, any other workaround to make rman duplicate work without changing this?
SQL> show parameter password
NAME TYPE VALUE
remote_login_passwordfile string NONE
SQL> connect /as sysdba;
Connected.
SQL> select * from v$pwfile_users;
no rows selectedYou are trying to connect from remote host to target host as SYSDBA. It will not be possible unless you have setup password file at target host.(remote_login_passwordfile=EXCLUSIVE). As RMAN automatically tries to connect as SYSDBA, you will fail.
I recommend, you execute duplication command from target host:
rman TARGET sys/***** AUXILIARY sys/password@AUX_TNS

Duplicate target database for standby failing with below error

Hello All, Need your assistance
We are creating a physical standby database (standalone) from 2 node RAC database, OS =RHEL5 and DB =11gR2
What we did: We took RMAN backup of primary DB along with archives and copied to standby server in same location. We have modified necessory prameters on primary as well as standby too.
The command we used :
RMAN>connect target sys/pwd@primary auxiliary sys/pwd@stdby
RMAN> run {
allocate auxiliary channel ch1 type disk;
duplicate target database for standby dorecover nofilenamecheck;
release channel ch1;
Note we tried : duplicate target database for standby as well as duplicate target database for standby nofilenamecheck methods too....But no luck..we are getting following error.
channel ch1: reading from backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
channel ch1: ORA-19870: error while restoring backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
ORA-19501: read error on file "/u01/BDB/BWFCCPRD_5fmpdvce_1_1", block number 121856 (block size=8192)
ORA-27072: File I/O error
Additional information: 4
Additional information: 121856
Additional information: 1036288
failover to previous backup
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/20/2011 09:16:11
RMAN-05501: aborting duplication of target database
RMAN-05556: not all datafiles have backups that can be recovered to SCN 41855007833
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 4 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
could you pease help to resolve this ....?
Note : Creating standby using RMAN 11g new feature : duplicate target database for standby from active database is not possible in our environment since the network bandwith is tooooo low, We have tried and not able to succeed because of n/w issue, So we are doing this alternate method...!!!
Looking for your valuable advises...
Thanks in Advance....

Take the fresh backup and also check the space crunch. The below clink may help you
ORA-27072: File I/O error Additional information: 2
--neeraj
Edited by: Vishen on Oct 20, 2011 2:14 PM

Error while Duplicating the Database

Hi All;
I am trying to duplicate a database and when run this command I get the below error....
RMAN> duplicate target database to rmdupl1 nofilenamecheck;
Starting Duplicate Db at 26-NOV-07
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=11 devtype=DISK
printing stored script: Memory Script
set until scn 53262;
set newname for datafile 1 to
"C:\ORACLE\ADMIN\PROD\DATAFILE\SYSTEM01.DBF";
set newname for datafile 2 to
"C:\ORACLE\ADMIN\PROD\DATAFILE\UNDOTBS.DBF";
restore
check readonly
clone database
executing script: Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 26-NOV-07
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to C:\ORACLE\ADMIN\PROD\DATAFILE\SYSTEM01.DBF
restoring datafile 00002 to C:\ORACLE\ADMIN\PROD\DATAFILE\UNDOTBS.DBF
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/26/2007 07:09:44
RMAN-03015: error occurred in stored script Memory Script
ORA-19504: failed to create file "C:\ORACLE\ADMIN\PROD\DATAFILE\SYSTEM01.DBF"
ORA-27086: skgfglk: unable to lock file - already in use
OSD-04002: unable to open file
O/S-Error: (OS 5) Access is denied.
RMAN>

I think Peter is right. You are probably erroneously attempting to overwrite the original, source database.
See: rman duplicate command fails?
Virtually the same error message!

Duplicate target database for standby backup location.... errors out

Hi ,
i am getting below error while executing
RMAN> duplicate target database for standby backup location '/rman1/perf/brmbkpdg' nofilenamecheck dorecover ;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "backup": expecting one of: "dorecover, db_file_name_convert, from, nofilenamecheck, ;, spfile"
RMAN-01007: at line 1 column 39 file: standard input
Can you please suggest a fix or what should be the syntax
Thanks
Naveen

If it helps here are my tested commands: (Oracle 11)
PRIMARY
RMAN RUN {
allocate channel d1 type disk;
backup format '/u01/backups/PRIMARY/df_t%t_s%s_p%p' database;
sql 'alter system archive log current';
backup format '/u01/backups/PRIMARY/al_t%t_s%s_p%p' archivelog all;
backup current controlfile for standby format '/u01/backups/PRIMARY/sb_t%t_s%s_p%p';
release channel d1;
STANDBY
RMAN> run {
allocate channel C1 device type disk;
allocate auxiliary channel C2 device type disk;
duplicate target database for standby nofilenamecheck;
My how to notes are here :
http://www.visi.com/~mseberg/duprman.html
Please note these were written not to create but to recover a standby, you still have to set up forced logging and the net80 in advance.
Best Regards
mseberg

RMAN duplicate target database error

Hello,
I’m trying to use RMAN ‘duplicate target from active database’ to a remote host however I’m getting a confusing error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/19/2009 13:47:23
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on aux13 channel at 11/19/2009 13:47:23
ORA-19504: failed to create file "+DATA2"
RMAN-03009: failure of backup command on aux14 channel at 11/19/2009 13:47:23
ORA-19504: failed to create file "+DATA2"
Here’s my script:
connect target sys/<password>@node1;
connect auxiliary sys/<password>@node2;
spool log to '/u01/app/oracle/dba/duplicate111909.log'
run
allocate auxiliary channel aux11 device type disk;
allocate auxiliary channel aux12 device type disk;
allocate channel aux13 device type disk;
allocate channel aux14 device type disk;
duplicate target database to node2 from active database DB_FILE_NAME_CONVERT='+DATA1','+DATA2';
release channel aux14;
release channel aux13;
release channel aux12;
release channel aux11;
spool log off;
exit;
Node1 uses ASM disk group DATA1 and I intend to use ASM disk group DATA2 on node2. Has anyone seen this error before? I have tried various permutations of DB_FILE_NAME_CONVERT clauses but all error with ORA-19504. On a side note I was able to use ASMCMD cp command to copy a datafile from node1 DATA1 to node 2 DATA2. Also, if I use disk group DATA1 on node 2 then the RMAN duplicate command runs successfully, it only errors when using DATA2. And yes +DATA2 is mounted on node2:
SQL> select name, state from v$asm_diskgroup;
NAME STATE
DATA1 MOUNTED
DATA2 MOUNTED
Any and all ideas are welcome. I’m running out of things to check.
Thanks,
RJL

For a duplicate you don't need to give the DB_FILE_NAME_CONVERT especially if you go from a asm to asm diskgroup.
The place where it'll put all the files will be automatically done taking care of the init.ora file parameter db_create_file_dest, (db_create_online_log_dest_1)

RMAN-05001 auxiliary .... conflicts with a file used by the target database

I can´t recreate my physical standby.
It worked in the past.
Now I reinstalled the 3 standbyclients.
Copied the spfile from the primary - modified the entries and did a rman backup.
But when issuing the duplicate database command - it comes up with the error above
SPFILE standyby db:
*.db_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
*.log_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
Starting restore at 15-APR-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/stage/33lb65n2_1_1
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/oracle/stage/33lb65n2_1_1 tag=TAG20100415T102434
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:11
output filename=+REDO1/stdy/controlfile/current.262.716293055
output filename=+REDO2/stdy/controlfile/backup.262.716293055
Finished restore at 15-APR-10
sql statement: alter database mount standby database
released channel: ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/15/2010 10:31:46
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename DATA/prim/datafile/system.262.715097535 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.263.715097499 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs3.269.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs2.270.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/example.272.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/users.268.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.273.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs1.271.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/system.264.710521021 conflicts with a file used by the target database+

Hi ,
I feel you are using ASM but still check the below details:
Cause
Production and Auxiliary have same directory structure and are running on two different machines. RMAN must be told not check that the target datafiles are sharing the same names as the duplicated files being created. Otherwise, the following errors will be returned:
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_03.dbf
conflicts with a file used by the target database
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_02.dbf
Solution
To implement the solution, please use nofilenamecheck in syntax as follows:
1. Connect to Target, auxiliary, and rman catalog and
2. use script as
run{
set until time "to_date('2005/09/17 14:00:00','yyyy/mm/dd HH24:MI:SS')";
allocate auxiliary channel aux1 type 'sbt_tape';
allocate auxiliary channel aux2 type 'sbt_tape';
duplicate target database for standby dorecover nofilenamecheck;
Make sure to use auxiliary type of channel so RMAN restore take place at auxiliary database.
Thanks,
Rafi.
http://rafioracledba.blogspot.com/

Duplicating a Database

RAC11g
Hi
I am duplicating a database with RMAN duplicate.
I set the parameters db_file_name_convert, log_file_name_convert on both instances of target database. The target database is a production database. I know I have to shutdown both instances and after start them for having the parameters on both. Accidentaly I shutdown one of them and up to I shutdown the another the instance1 is not going to be started because the instance tell me that the parameters have to be equal on both. I know that If I shutdown instance2, after both instances are going to be fine but I can not do it because I can not close the database.
Instance1 have the parameters originaly so:
SQL> show parameters convert
NAME TYPE VALUE
db_file_name_convert string
log_file_name_convert string
and the instance1 has these parameters with values that I set.
What I want ?. Clear these parameters on instance1 again for starting it again.
I know I can modify parameters of instance1 from instance2 but the values seems to be bad....
for example:
when I tro to clear the parameters from instance1 I get the following error:
SQL> alter system set db_file_name_convert='','' scope=spfile sid='instance1';
alter system set db_file_name_convert='','' scope=spfile sid='COFASADB1'
ERROR at line 1:
ORA-01078: failure in processing system parameters
LRM-00117: syntax error at ',' at the start of input
SQL>
what is the correct value to clear the parameter ?
Thanks

Hi
I removed the parameters with alter system reset <parameter name> scope=spfile sid='*';
Now I have set the parameters only in auxiliary database but it seems... it is looking for to retore on production dbfiles....
Both databases are RAC databases and they are on the same hosts.
I have done several duplicates in RAC enviroment from RAC Database to single instance inside these hosts without any problem.
I am doing the duplicate from node2 connecting to the production database instance2 and auxiliary database in instance2 as well.
Thanks

Error while duplicate database for standby

Hello Guys,
Both of my database are 10gR2 and Linux is the operating system.
I am trying to create a standby database for my production database.
I have matched the directory structure of primary and standby database and there is no conflict. Directory permissions are also set.
After taking the rman backup from production database when i connect auxiliary database from production. I run this command to duplicate database and create standby database.
rman
set until sequence XXXX;
duplicate target database for standby dorecover nofilenamecheck;
I get this error:
executing Memory Script
executing command: SET until clause
Starting restore at 04-JUN-11
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /tmp/backup_files/standby_control_1jme2far_1_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/04/2011 21:00:37
RMAN-03015: error occurred in stored script Memory Script
ORA-19870: error reading backup piece /tmp/backup_files/standby_control_1jme2far_1_1
ORA-01565: error in identifying file '/u01/app/oracle/product/10.2.0/db_1/dbs/spfileORCL.ora'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
*/tmp/backup_files/standby_control_1jme2far_1_1 file exists*
* spfileORCL.ora* exists on both servers in same directory and same path.
Can you please suggest where is the problem?
Thank you so much.
Imran

ORA-19870: error reading backup piece /tmp/backup_files/standby_control_1jme2far_1_1
ORA-01565: error in identifying file '/u01/app/oracle/product/10.2.0/db_1/dbs/spfileORCL.ora'
ORA-27037: unable to obtain file statusLinux-x86_64 Error: 2: No such file or directory
Might the backup piece not exist or file is unae to read at this time. Can you check is this physically exist Or not?
And preferred to take new fresh backup and perform duplicate

TARGET database is not compatible with this version of RMAN

I am trying to register a database (version 8.0.4) on my catalog database which is version 8.1.7.
I get the following error:
RMAN-06185: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
Does this mean that my RMAN database has to be 8.0.4 ?
What happens if my RMAN database is 8.0.4 and target is 8.1.7 ?
Thanks for any help,
Sameer

check RMAN compatibility matrix
Target/Auxiliary Database|| RMAN Executable|| Catalog Database ||Catalog Schema
8.0.3 8.0.3 >=8.x 8.0.3
8.0.4 8.0.4 >=8.x >= 8.0.4, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.5 8.0.5 >=8.x >= 8.0.5, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.6 8.0.6 >=8.x 8.0.6
8.0.6 8.0.6 >=8.1.x >=8.1.x
8.1.5 8.1.5 >=8.1.x >= 8.1.5
8.1.6 8.0.6.1 >=8.x 8.0.6
8.1.6 8.0.6.1 >=8.1.x >= 8.1.x
8.1.6 8.1.x >=8.1.x >= RMAN executable
8.1.7 8.0.6.1 >=8.x 8.0.6
8.1.7 8.0.6.1 >=8.1.x >=8.1.x
8.1.7 8.1.x >=8.1.x >= RMAN executable
9.0.1 >=9.0.1 >=8.1.x >= RMAN executable
In other words to backup 8.0.4 version u need a separate schema in catalog database and which will be only used for 8.0.4

Error Duplicating Target Database

Similar Messages

Maybe you are looking for