DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT

hello guys,
I am configuring a data guard with one physical standby on VMWARE.. with primary database on one system and physical standby on the other.. database 11g r2
oracle document says that the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT has to mentioned if the directory structure is going to be different on both the sites.
directory structure on the primary database will be
/u01/app/oracle/oradata/oracle/
and on standby will be
/u01/app/oracle/oradata/oracles/
now my question is do we have to set this parameter on the standby system (i use RMAN to create the standby using DUPLICATE command so it renames the filepath of all the datafiles on the standby system during duplication process.) or on the primary database tooo please tell me..
i believe the log_file_name_convert parameter need not be set as the RMAN will automatically create the logfiles. please tell me if i am correct..

Yes you need to set both the parameter..
these parameters will update the controlfile regarding locations of datafiles & log files. it is mandatory.. if you specify these parameters then only RMAN knows where these need to restore.
because we are using controlfile from primary database http://www.stanford.edu/dept/itss/docs/oracle/9i/server.920/a96536/ch144.htm
http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams112.htm
Thanks
Edited by: CKPT on Nov 1, 2010 1:13 PM

Similar Messages

DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT and Data Guard

Can somebody give me an example of when DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT would not be set?
Assume the following:
Oracle 11 R2
Location of the datafiles are the on both servers
Physical Standby Server (One only)
Archive in FRA

You don't set if you have something like db_create_file_dest=whatever in your init file...then by default all files go there.
Another way not to use them is to set newname or set auxname in rman...but the easiest is db_create_file_dest in your init file

LOG_FILE_NAME_CONVERT failed to change name and dest of primary redo logs

Hi,
we tried to create standby using RMAN and we used db_file_name_convert and log_file_name_convert,every thing went fine but when we tried to put the database in MRM the primary database redo logs got corrupted.
what could be the reason for this parameter failing.
Thanks,
Mastan Ali

Does your database have a version?
Did you set those parameters on the standby database, or in the primary?
What error message are you getting?
Do you agree this forum doesn't contain a set of mindreaders and ouaja board users and fortunetellers, so posting 'It doesn't work' is useless?
Sybrand Bakker
Senior Oracle DBA

Data Guard: db_file_name_convert/log_file_name_convert when using ASM/OMF

All,
I have a call currently open with Oracle regarding the setting of the parameters db_file_name_convert and log_file_name_convert in a data guard environment. We use ASM / OMF for storage and file naming and my question is basically do these parameters have to be set. The documentation says they do where the file structure is different between PRIMARY and STANDBY.
I have successfully tested failover and switchover without these parameters. I have also added a new tablespace on the PRIMARY and watched it create a new OMF datafile on standby when the logs are switched.
I just can't see a reason for setting them when using ASM / OMF.
I'm hoping someone can enlighten me here because I'm getting nowhere whith support. The following is our Data Guard setup:
PRIMARY
DB_NAME=IBSLIVE
DB_UNIQUE_NAME=IBSLIVE
ASM Disk Groups:
+PRODDATA (Data Files, Control Files, Redo Logs)
+PRODFLASH (Archive Logs, Flashback Logs, RMAN backups)
+PRODLOGS (Multiplexed Control & Redo Logs)
STANDBY
DB_NAME=IBSLIVE
DB_UNIQUE_NAME=IBSDR
ASM Disk Groups:
+DRDATA (Data Files, Control Files, Redo Logs)
+DRFLASH (Archive Logs, Flashback Logs, RMAN backups)
+DRREDO (Multiplexed Control & Redo Logs)
Many Thanks,
Ian.

Ian,
I'm having similar thoughts.
I have created a new instance with files in asm under +datadisk/obosact (this is the smae name as primary)
I then modify the db_unique_name from obosact to obosactdr as is required for standby to work
When I recover (duplicate target database for standby; ) I find that the files are in datadisk/obosactdr not in the datadisk/obosact area
I found this reference http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
4. Connect to the ASM instance on one standby host, and create a directory within the DATA disk group that has the same name as the DB_UNIQUE_NAME of the standby database. For example: SQL> ALTER DISKGROUP data ADD DIRECTORY '+DATA/BOSTON';
This step seems to indicate that the location of the files is determined by the db_unique_name not the db_file_name_convert paramenter
DId you ever resolve the issue?

What value to be set in DB_FILE_NAME_CONVERT ?

Hi all,
I try to create standby database and my datafile are all over my hard disk,
what should I do to my DB_FILE_NAME_CONVERT to let my standby database know
this issue ?
example
/prod_data1/system01.dbf
/prod_data2/user01.dbf
/prod_data3/rbs01.dbf
my standby datafile
/standby_data1/system01.dbf
/standby_data1/user01.dbf
/standby_data2/rbs01.dbf
what is the right way to spacify using DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter ??
DB_FILE_NAME_CONVERT= ??
thanks in advance.
Deep

Hi,
like
db_file_name_convert = ('d:\oracle\product\10.1.0\oradata\ORA101','d:\oracle\product\10.1.0\oradata\TESTDB')
log_file_name_convert = ('d:\oracle\product\10.1.0\oradata\ORA101','d:\oracle\product\10.1.0\oradata\TESTDB')regards
Taj

Changing DB_FILE_NAME_CONVERT

Oracle Database 10g Enterprise Edition
Oracle Enterprise Linux
I am trying to learn creating Dataguard configuration on my laptop. Since I am creating both Primary and Standby databases on the same laptop using same Oracle home I need to use db_file_name_convert and Log_file_name_convert. But I just can't change db_file_name_convert parameter. I am using spfile.
I am getting ORA-2096 errors. That this parameter cannot be modified with these options.
Can anyone tell me how to change this parameter.
I have tried various ways,
ALTER SYSTEM SET DB_FILE_NAME_CONVERT=('ABC','XYZ') SCOPE= BOTH;
ALTER SYSTEM SET DB_FILE_NAME_CONVERT=('ABC','XYZ') SCOPE=SPFILE;
ALTER SYSTEM SET DB_FILE_NAME_CONVERT=('ABC','XYZ') SCOPE=BOTH DEFERRED;
ALTER SYSTEM SET DB_FILE_NAME_CONVERT=('ABC','XYZ') SCOPE=SPFILE DEFERRED;
Everytime I am getting 2096 error.

This is the error I am getting
This is the primary database.
SQL> select name from v$database;
NAME
XYZ
SQL> show parameter db_file_name_convert
NAME TYPE VALUE
db_file_name_convert string
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=spfile;
alter system set db_file_name_convert=('ABC','XYZ') scope=spfile
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=spfile deferred;
alter system set db_file_name_convert=('ABC','XYZ') scope=spfile deferred
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') deferred scope=spfile;
alter system set db_file_name_convert=('ABC','XYZ') deferred scope=spfile
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=memory;
alter system set db_file_name_convert=('ABC','XYZ') scope=memory
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=spfile sid='*';
alter system set db_file_name_convert=('ABC','XYZ') scope=spfile sid='*'
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option
SQL> alter system set db_file_name_convert=('ABC','XYZ') scope=spfile sid='*' deferred;
alter system set db_file_name_convert=('ABC','XYZ') scope=spfile sid='*' deferred
ERROR at line 1:
ORA-02096: specified initialization parameter is not modifiable with this
option

ORA-01678 parameter log_file_name_convert

Hi,
in my init.ora file I have :
LOG_FILE_NAME_CONVERT=("s:\ORADATA\DB1","u:\ORADATA\DB2","u:\ORADATA\DB1","u:\ORADATA\DB2")
And I receive this error :
ORA-01678: parameter log_file_name_convert must be two strings, a pattern and a replacement
Do you have any idea ?
Many nthanks.

Thanks, as you can see here
http://www.lc.leidenuniv.nl/awcourse/oracle/server.920
/a96536/ch1104.htm
we can have :
LOG_FILE_NAME_CONVERT
Parameter type
String
Syntax
LOG_FILE_NAME_CONVERT = [(]'string1' , 'string2' ,
'string3' , 'string4' , ...[)]
several couple of logfiles like what I have in my
init.ora file. But it does not function for me.
Message was edited by:
user522961Refer to a document at 9i, and performing actions on what you stated was 817. They are not the same.
To quote the 817 propaganda specified in my first post (had you read it closely):
The DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameters must have two strings. The first string is a sequence of characters to be looked for in a primary database filename. If that sequence of characters is matched, it is replaced by the second string to construct the standby database filename.
(emphasis is mine)
http://download-west.oracle.com/docs/cd/A87860_01/doc/server.817/a76995/standby.htm#23603
as in the following example from the same reference:
ample: Managed Standby Database on Same Host as Primary Database
Following are some sample initialization parameter settings for a managed standby database that resides on the same host as primary database PROD1.
COMPATIBLE = 8.1.6
CONTROL_FILES = /oracle/work/standby/dbs/cf1.f
DB_FILE_NAME_CONVERT = /oracle/dbs/tbs, /oracle/work/standby/dbs/standby
DB_NAME = prod1
LOCK_NAME_SPACE = stby # required for a standby on the same host as the primary
LOG_ARCHIVE_DEST = /oracle/work/standby/dbs/arc/
LOG_ARCHIVE_FORMAT = arc_%t_%s.ar
LOG_ARCHIVE_TRACE = 8
LOG_FILE_NAME_CONVERT = /oracle/dbs/t1, /oracle/work/standby/dbs/standby_t1
STANDBY_ARCHIVE_DEST = /oracle/work/standby/dbs/arc/
Example: Managed Standby Database on Different Host from Primary

Issue in configuring Standby Database from Active database in 11g by RMAN

POSTED THE SAME IN DATA GUARD CATEGORY UNABLE TO DELETE
Hi All,
I am facing issue in creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0)
Operating System:Linux 5
Error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52
RMAN-03015: error occurred in stored script Memory Script
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Primary Database Entries:
Tnsentry:
SONYPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)(UR=A)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listner Entry:
SID_LIST_SONYPRD =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtproc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
(SID_DESC =
(SID_NAME = SONYPRD)
(GLOBAL_DBNAME = SONYPRD)
Auxiliary Details:
Tns Entry:
SONYPRD =
(DESCRIPTION =
# (ADDRESS = (PROTOCOL = TCP)(HOST = oracle11g.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprd.localdomain)
SONYPRDSTBY =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sonyprdstby)(UR=A)
Listener Entry in auxiliary:
SID_LIST_SONYPRDSTBY =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = SONYPRDSTBY)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1)
(SID_NAME = SONYPRDSTBY)
TNSPING from Primary DB:
[oracle@oracle11g ~]$ tnsping sonyprdstby
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:39:28
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.132)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprdstby)(UR=A)))
OK (0 msec)
TNSPING from Auxuliary server
[oracle@oracle11gstby ~]$ tnsping sonyprd
TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 17:40:19
Copyright (c) 1997, 2009, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.20.131)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = sonyprd.localdomain)))
OK (10 msec)
Script Used for duplicate:
run {
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate auxiliary channel stby type disk;
duplicate target database for standby from active database
spfile
parameter_value_convert 'sonyprd','sonyprdstby'
set db_unique_name='sonyprdstby'
set db_file_name_convert='/sonyprd/','/sonyprdstby/'
set log_file_name_convert='/sonyprd/','/sonyprdstby/'
set control_files='/u01/app/oracle/oradata/control01.ctl'
set log_archive_max_processes='5'
set fal_client='sonyprdstby'
set fal_server='sonyprd'
set standby_file_management='AUTO'
set log_archive_config='dg_config=(sonyprd,sonyprdstby)'
set log_archive_dest_2='service=sonyprd ASYNC valid_for=(ONLINE_LOGFILE,PRIMARY_ROLE) db_unique_name=sonyprd'
Tried the script from both Primary and auxiliary but no luck
[oracle@oracle11gstby admin]$ rman target sys/welcome@sonyprd auxiliary sys/*****@sonyprdstby
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Dec 21 17:26:24 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: SONYPRD (DBID=3131093559)
connected to auxiliary database: SONYPRD (not mounted)
Listener Status from primary:
[oracle@oracle11g ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:08:56
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 20-DEC-2012 17:42:17
Uptime 1 days 0 hr. 26 min. 41 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/localhost/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.localdomain)(PORT=1521)))
Services Summary...
Service "sonyprd.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
Service "sonyprdXDB.localdomain" has 1 instance(s).
Instance "sonyprd", status READY, has 1 handler(s) for this service...
The command completed successfully
Listener Status from Standby when database bring to Nomount state:
[oracle@oracle11gstby admin]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 21-DEC-2012 18:11:54
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 21-DEC-2012 16:13:47
Uptime 0 days 1 hr. 58 min. 6 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/oracle11gstby/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracle11gstby)(PORT=1521)))
Services Summary...
Service "sonyprdstby" has 1 instance(s).
Instance "sonyprdstby", status BLOCKED, has 1 handler(s) for this service...
The command completed successfully
Please provide any work arounds to proceed further in creating the standby database.
Thanks,
Ram.
Edited by: 895188 on Dec 21, 2012 5:50 PM
Edited by: 895188 on Dec 21, 2012 6:09 PM
Edited by: 895188 on Dec 21, 2012 6:22 PM

Hello;
Script has to be run from auxiliary.
Great details, but what I don't see is how you connect in RMAN.
Example
Start RMAN
$ORACLE_HOME/bin/rman target=sys/@recover2 auxiliary=sys/@reclone
Recovery Manager: Release 11.2.0.2.0 - Production on Wed Feb 22 14:50:31 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: RECOVER2 (DBID=3806912436)
connected to auxiliary database: RECLONE (not mounted)Nothing in your tnsnames or listener jumps out as wrong. I copied them into my text editor and compared against my working ones.
Generally for active duplication I start the future standby on a pfile NOMOUNT.
Auxiliary Instance Initialization Parameters Needed :
DB_NAME
CONTROL_FILES
DB_BLOCK_SIZE
( add extra parameters like DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT instead of using the SET command - clean up standby spfile right after duplication )
Then start RMAN and finally run a single line duplication command.
$ORACLE_HOME/bin/rman target=sys/@primary auxiliary=sys/@standby
RMAN>duplicate target database for standby from active database NOFILENAMECHECK;Best Regards
mseberg

Create a new Database in an other server using a copie of RMAN backup

Hi all,
I want to create an other instance for our production database. We have disk and tape in rman backup. My question is can i create a new database using our disk backup in an other server?
If some procedure or steps is there, email it to my adresse [email protected]
Hamid.
Thanks

By means of the use of Recovery Manager it is possible to duplicate a database out from a previously taken rman backup. The method will be outlined in the next few lines.
Let's assume a source database named SRCDB and the target database, named GEMINI. A unix like environment is assumed, but it can be implemented on windows as well, just beware of the particular Oracle implementation on a windows platform (orapwd file name, service creation, path format)
1. Create a password file for the Cloned (GEMINI) instance:
orapwd file=/u01/app/oracle/product/9.2.0.1.0/dbs/orapwGEMINI password=password entries=10
2. Configure tnsnames.ora and listner.ora
Properly identify the database at the tnsnames.ora and have the instance manually registered against the listener.ora files, both files located at the $ORACLE_HOME/network/admin directory.
2.a Manually register the database against the listener (listener.ora)
(SID_DESC =
(ORACLE_HOME = /u01/app/oracle/product/9.2.0.1.0)
(SID_NAME = GEMINI)
2.b Added the target GEMINI to the tnsnames.ora
GEMINI =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1521))
(CONNECT_DATA =
(ORACLE_SID = GEMINI)
2.c Reload the listener
lsnrctl reload
3. Create a new init.ora for the cloned database.
Next create an init.ora file for the cloned database. In case the same paths cannot be used on the target host, either because it is the same source host or because those paths are not reproducible on the target, then DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT may be required to be defined
DB_NAME=GEMINI
CONTROL_FILES=(/u02/oradata/GEMINI/control01.ctl,
/u02/oradata/GEMINI/control02.ctl,
/u02/oradata/GEMINI/control03.ctl)
# Convert file names to allow for different directory structure.
DB_FILE_NAME_CONVERT=(/u02/oradata/SRCDB/,/u02/oradata/GEMINI/)
LOG_FILE_NAME_CONVERT=(/u01/oradata/SRCDB/,/u01/oradata/GEMINI/)
# block_size and compatible parameters must match those of the source database
DB_BLOCK_SIZE=8192
COMPATIBLE=9.2.0.0.0
4. Connect to the cloned instance
ORACLE_SID=GEMINI; export ORACLE_SID
sqlplus /nolog
conn / as sysdba
5. Create an SPFILE based on the init.ora
CREATE SPFILE FROM PFILE='/u01/app/oracle/admin/GEMINI/pfile/init.ora';
6. Start the database in NOMOUNT mode:
STARTUP FORCE NOMOUNT;
7. Connect to the TARGET, CATALOG and AUXILIARY databases.
By means of the rman three connections are open, one for the Source Database (SOURCEDB), another for the Catalog database (RCAT), and one more for the cloned database (GEMINI)
ORACLE_SID=GEMINI; export ORACLE_SID
rman TARGET sys/password@SRCDB CATALOG rman/rman@RCAT AUXILIARY /
8. Complete or Incomplete clone (recover)
From the rman the database using one of the following commands:
8.a Clone the database by means of a complete recover.
DUPLICATE TARGET DATABASE TO GEMINI;
8.b Clone the database up to a defined point in time in the past by means of an incomplete recover
DUPLICATE TARGET DATABASE TO GEMINI UNTIL TIME 'SYSDATE-2';
9. Process finished.
Once the process is finished, the newly created GEMINI database is ready to be used as an independent new cloned database.
Ref. RMAN Clone a Database
~ Madrid

Creation of standby db in ASM fails.

We are using dataguard to help us migrate off of ocfs and over to ASM. I am attempting to create the standby database and believe that I have all of the parameters setup correctly e.g. db_file_name_convert and log_file_name_convert but when I run my rman script that uses duplicate to create the standby db I get the following errors during standby db creation when rman attempts to mount the standby db right after the standby control files are created.
channel dev_0: restored backup piece 1
piece handle=fljsnrg1_1_1 tag=TAG20081009T145109
channel dev_0: restore complete, elapsed time: 00:06:36
output filename=+DATA_DG/rcidb/control01.ctl
output filename=+REDO_DG/rcidb/control02.ctl
Finished restore at 14-OCT-08
sql statement: alter database mount standby database
released channel: dev_0
released channel: dev_1
released channel: dev_2
released channel: dev_3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/14/2008 15:12:05
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on clone_default channel at 10/14/2008 15:12: 05
RMAN-11003: failure during parse/execution of SQL statement: alter database moun t standby database
ORA-15171: invalid syntax in the alias path after 'RCIDB/'
RCIDB is the name of our db and the directoty exists in the correct ASM disk group but still we get the error ORA-15171: invalid syntax in the alias path after 'RCIDB/'
Has anyone encountered the same.
Thanks.

SQL> show parameter control
NAME TYPE VALUE
control_file_record_keep_time integer 7
control_files string +DATA_DG/rcidb/control01.ctl,
+REDO_DG/rcidb/control02.ctl
SQL> show parameter db_file_name_convert
NAME TYPE VALUE
db_file_name_convert string /opt/oracle/oradata/oradata1/,
+DATA_DG/RCIDB/, /opt/oracle/
oradata/oradata2/, +DATA_DG/RC
IDB/, /opt/oracle/oradata/orad
ata3/, +DATA_DG/RCIDB/, /opt/o
racle/oradata/oradata4/, +DATA
_DG/RCIDB/, /opt/oracle/oradat
a/oraindex/, +DATA_DG/RCIDB/,
/opt/oracle/oradata/oraindex1/
, +DATA_DG/RCIDB/, /opt/oracle
/oradata/oraindex2/, +DATA_DG/
NAME TYPE VALUE
RCIDB/, /oradata2/, +DATA_DG/R
CIDB/
SQL> show parameter log_file_name_convert
NAME TYPE VALUE
log_file_name_convert string /opt/oracle/oradata/oradata1/,
+REDO_DG/RCIDB/, /opt/oracle/
oradata/oraindex1/, +REDO_DG/R
CIDB/
SQL> show parameter db_create_file_dest
NAME TYPE VALUE
db_create_file_dest string +DATA_DG
SQL> show parameter db_create_online
NAME TYPE VALUE
db_create_online_log_dest_1 string +REDO_DG
db_create_online_log_dest_2 string
db_create_online_log_dest_3 string
db_create_online_log_dest_4 string
db_create_online_log_dest_5 string

RMAN 11gr2 ORA-00308 when dulplicate database from active

Hi,
I'm trying to clone a production database (Oracle 11.2.0.3) from HP-UX IA64 to Solaris 10 (Sparc 64) (source on Filesystem, target on ASM)
the previous steps was done (same oracle software installation, same patches, sqlnet comunication, etc.)
but the RMAN fails at end of the process:
Recovery Manager: Release 11.2.0.3.0 - Production on Wed Aug 22 09:44:34 2012
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
connected to target database: SIN (DBID=634625013)
connected to recovery catalog database
connected to auxiliary database: SIN (not mounted)
RMAN> run
+2> {+
+3> allocate channel c1 type disk;+
+4> allocate channel c2 type disk;+
+5> allocate channel c3 type disk;+
+6> allocate channel c4 type disk;+
+7> allocate auxiliary channel a1 type disk;+
+8> allocate auxiliary channel a2 type disk;+
+9> set newname for datafile 1 to '+DG_DATA';+
+10> set newname for datafile 2 to '+DG_DATA';+
+11> set newname for datafile 3 to '+DG_DATA';+
+12> set newname for datafile 4 to '+DG_DATA';+
+13> set newname for datafile 5 to '+DG_DATA';+
+14> set newname for datafile 6 to '+DG_DATA';+
+15> set newname for datafile 7 to '+DG_DATA';+
+16> set newname for datafile 8 to '+DG_DATA';+
+17> set newname for datafile 9 to '+DG_DATA';+
+18> set newname for datafile 10 to '+DG_DATA';+
+... to...+
+398> set newname for datafile 390 to '+DG_DATA';+
+399> set newname for datafile 391 to '+DG_DATA';+
+400> duplicate target database to "sin" from active database nofilenamecheck+
+401> DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','+DG_DATA/',+
+402> '/u11/oradata/sin/','+DG_DATA/',+
+403> '/u07/oradata/sin/','+DG_DATA/',+
+404> '/u08/oradata/sin/','+DG_DATA/',+
+405> '/u09/oradata/sin/','+DG_DATA/');+
+406> }+
+407>+
starting full resync of recovery catalog
full resync complete
allocated channel: c1
channel c1: SID=1787 device type=DISK
allocated channel: c2
channel c2: SID=2406 device type=DISK
allocated channel: c3
channel c3: SID=850 device type=DISK
allocated channel: c4
channel c4: SID=1146 device type=DISK
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=1514 device type=DISK
executing command: SET NEWNAME
executing command: SET NEWNAME
+...+
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting Duplicate Db at 22-AUG-12
contents of Memory Script:
+{+
sql clone "create spfile from memory";
+}+
executing Memory Script
sql statement: create spfile from memory
contents of Memory Script:
+{+
shutdown clone immediate;
startup clone nomount;
+}+
executing Memory Script
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area    7317790720 bytes
Fixed Size                     2173456 bytes
Variable Size               3808433648 bytes
Database Buffers            3489660928 bytes
Redo Buffers                  17522688 bytes
allocated channel: a1
channel a1: SID=1325 device type=DISK
allocated channel: a2
channel a2: SID=758 device type=DISK
contents of Memory Script:
+{+
sql clone "alter system set control_files =
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/current.562.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
sql clone "alter system set db_name =
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+sql clone "alter system set db_unique_name =+
+''SIN'' comment=+
+''Modified by RMAN duplicate'' scope=spfile";+
+shutdown clone immediate;+
+startup clone force nomount+
+backup as copy current controlfile auxiliary format '+DG_DATA/sin/controlfile/current.512.791978153';+
+restore clone controlfile to '+DG_DATA/sin/controlfile/current.625.791978153' from+
+'+DG_DATA/sin/controlfile/current.512.791978153';+
+sql clone "alter system set control_files =+
+''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/current.625.791978153'' comment=+
+''Set by RMAN'' scope=spfile";+
+shutdown clone immediate;+
+startup clone nomount;+
+alter clone database mount;+
+}+
+executing Memory Script+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.511.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.562.791978153'' comment= ''Set by RMAN'' scope=spfile+
+sql statement: alter system set db_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+sql statement: alter system set db_unique_name = ''SIN'' comment= ''Modified by RMAN duplicate'' scope=spfile+
+Oracle instance shut down+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+Starting backup at 22-AUG-12+
+channel c1: starting datafile copy+
+copying current control file+
+output file name=/u06/tmpapp/rmanbkps/snapcf_sin.f tag=TAG20120822T094657 RECID=49 STAMP=791977621+
+channel c1: datafile copy complete, elapsed time: 00:00:01+
+Finished backup at 22-AUG-12+
+Starting restore at 22-AUG-12+
+channel a2: skipped, AUTOBACKUP already found+
+channel a1: copied control file copy+
+Finished restore at 22-AUG-12+
+sql statement: alter system set control_files = ''+DG_DATA/sin/controlfile/current.512.791978153'', ''+DG_DATA/sin/controlfile/cu+
+rrent.625.791978153'' comment= ''Set by RMAN'' scope=spfile+
+Oracle instance shut down+
+connected to auxiliary database (not started)+
+Oracle instance started+
+Total System Global Area 7317790720 bytes+
+Fixed Size 2173456 bytes+
+Variable Size 3808433648 bytes+
+Database Buffers 3489660928 bytes+
+Redo Buffers 17522688 bytes+
+allocated channel: a1+
+channel a1: SID=1514 device type=DISK+
+allocated channel: a2+
+channel a2: SID=2081 device type=DISK+
+database mounted+
+Using previous duplicated file +DG_DATA/sin/datafile/system.666.791914845 for datafile 1 with checkpoint SCN of 46164275052+
+Using previous duplicated file +DG_DATA/sin/datafile/undotbs1.678.791913821 for datafile 2 with checkpoint SCN of 46164227408+
+...+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.498.791939115 for datafile 389 with checkpoint SCN of 46165353395+
+Using previous duplicated file +DG_DATA/sin/datafile/mytablespace.674.791914359 for datafile 390 with checkpoint SCN of 46164253329+
+Using previous duplicated file +DG_DATA/sin/datafile/med_dat.499.791939115 for datafile 391 with checkpoint SCN of 46165353396+
+contents of Memory Script:+
+{+
+sql 'alter system archive log current';+
+}+
+executing Memory Script+
+sql statement: alter system archive log current+
+contents of Memory Script:+
+{+
+backup as copy reuse+
+archivelog like "/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065832.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065833.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065834.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065835.ARC" auxiliary format+
+"+DG_DATA" archivelog like+
+"/u06/app/oracle/admin/sin/arch/SIN_0544862197_0001_0000065836.ARC" auxiliary format+
+"+DG_DATA" ;+
+catalog clone start with "+DG_DATA";+
+catalog clone datafilecopy "+DG_DATA/sin/datafile/system.666.791914845",+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.679.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.689.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.690.791913821",+
+"+DG_DATA/sin/datafile/undotbs1.677.791914357",+
+"+DG_DATA/sin/datafile/drsys.621.791939555",+
+"+DG_DATA/sin/datafile/high_idx.663.791914889",+
+"+DG_DATA/sin/datafile/tools.507.791939555",+
+...+
+"+DG_DATA/sin/datafile/bkptemp.497.791939113",+
+"+DG_DATA/sin/datafile/med_dat.498.791939115",+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359",+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+switch clone datafile 1 to datafilecopy+
+"+DG_DATA/sin/datafile/system.666.791914845";+
+switch clone datafile 2 to datafilecopy+
+"+DG_DATA/sin/datafile/undotbs1.678.791913821";+
+switch clone datafile 3 to datafilecopy+
+...+
+"+DG_DATA/sin/datafile/med_dat.498.791939115";+
+switch clone datafile 390 to datafilecopy+
+"+DG_DATA/sin/datafile/mytablespace.674.791914359";+
+switch clone datafile 391 to datafilecopy+
+"+DG_DATA/sin/datafile/med_dat.499.791939115";+
+}+
+executing Memory Script+
+Starting backup at 22-AUG-12+
+channel c1: starting archived log copy+
+input archived log thread=1 sequence=65832 RECID=48339 STAMP=791913640+
+channel c2: starting archived log copy+
+input archived log thread=1 sequence=65833 RECID=48340 STAMP=791933223+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65834 RECID=48341 STAMP=791939052+
+channel c4: starting archived log copy+
+input archived log thread=1 sequence=65835 RECID=48342 STAMP=791962351+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.791978259 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:00:35+
+channel c3: starting archived log copy+
+input archived log thread=1 sequence=65836 RECID=48343 STAMP=791977692+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 RECID=0 STAMP=0+
+channel c1: archived log copy complete, elapsed time: 00:00:51+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.791978259 RECID=0 STAMP=0+
+channel c2: archived log copy complete, elapsed time: 00:01:41+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.791978295 RECID=0 STAMP=0+
+channel c3: archived log copy complete, elapsed time: 00:01:06+
+output file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.791978259 RECID=0 STAMP=0+
+channel c4: archived log copy complete, elapsed time: 00:01:41+
+Finished backup at 22-AUG-12+
+searching for all files that match the pattern +DG_DATA+
+List of Files Unknown to the Database+
+=====================================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+cataloging files...+
+cataloging done+
+List of Cataloged Files+
+=======================+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65832.513.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65833.514.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65834.515.791978259+
+File Name: +dg_data/SIN/ARCHIVELOG/2012_08_22/thread_1_seq_65835.516.791978259+
+...+
+File Name: +dg_data/SIN/DATAFILE/XDB.508.791939555+
+File Name: +dg_data/SIN/DATAFILE/DRSYS.621.791939555+
+File Name: +dg_data/SIN/CONTROLFILE/Current.703.791913737+
+File Name: +dg_data/SIN/CONTROLFILE/Current.704.791913737+
+List of Files Which Where Not Cataloged+
+=======================================+
+File Name: +dg_data/SIN/CONTROLFILE/Current.691.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.692.791913737+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.511.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/SIN/CONTROLFILE/Current.562.791978153+
+RMAN-07517: Reason: The file header is corrupted+
+File Name: +dg_data/ASM/ASMPARAMETERFILE/REGISTRY.253.790861037+
+RMAN-07518: Reason: Foreign database file DBID: 0 Database Name:+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/system.666.791914845 RECID=442 STAMP=791978374+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.678.791913821 RECID=443 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.679.791913821 RECID=444 STAMP=791978375+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/undotbs1.689.791913821 RECID=445 STAMP=791978375+
+cataloged datafile copy+
+...+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.498.791939115 RECID=830 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/mytablespace.674.791914359 RECID=831 STAMP=791978408+
+cataloged datafile copy+
+datafile copy file name=+DG_DATA/sin/datafile/med_dat.499.791939115 RECID=832 STAMP=791978408+
+datafile 1 switched to datafile copy+
+input datafile copy RECID=442 STAMP=791978374 file name=+DG_DATA/sin/datafile/system.666.791914845+
+datafile 2 switched to datafile copy+
+input datafile copy RECID=443 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.678.791913821+
+datafile 3 switched to datafile copy+
+input datafile copy RECID=444 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.679.791913821+
+datafile 4 switched to datafile copy+
+input datafile copy RECID=445 STAMP=791978375 file name=+DG_DATA/sin/datafile/undotbs1.689.791913821+
+...+
+datafile 389 switched to datafile copy+
+input datafile copy RECID=830 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.498.791939115+
+datafile 390 switched to datafile copy+
+input datafile copy RECID=831 STAMP=791978408 file name=+DG_DATA/sin/datafile/mytablespace.674.791914359+
+datafile 391 switched to datafile copy+
+input datafile copy RECID=832 STAMP=791978408 file name=+DG_DATA/sin/datafile/med_dat.499.791939115+
+contents of Memory Script:+
+{+
+set until scn 46167049411;+
+recover+
+clone database+
+delete archivelog+
+;+
+}+
+executing Memory Script+
+executing command: SET until clause+
+Starting recover at 22-AUG-12+
+starting media recovery+
+archived log for thread 1 with sequence 65832 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.7+
+91978259+
+archived log for thread 1 with sequence 65833 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65833.514.7+
+91978259+
+archived log for thread 1 with sequence 65834 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65834.515.7+
+91978259+
+archived log for thread 1 with sequence 65835 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65835.516.7+
+91978259+
+archived log for thread 1 with sequence 65836 is already on disk as file +DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65836.581.7+
+91978295+
+archived log file name=+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259 thread=1 sequence=65832+
+released channel: c1+
+released channel: c2+
+released channel: c3+
+released channel: c4+
+Oracle Error:+
+ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below+
+ORA-01194: file 1 needs more recovery to be consistent+
+ORA-01110: data file 1: '+DG_DATA/sin/datafile/system.666.791914845'+
*+released channel: a1+*
*+released channel: a2+*
*+RMAN-00571: ===========================================================+*
*+RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============+*
*+RMAN-00571: ===========================================================+*
*+RMAN-03002: failure of Duplicate Db command at 08/22/2012 09:52:27+*
*+RMAN-05501: aborting duplication of target database+*
*+RMAN-03015: error occurred in stored script Memory Script+*
*+RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '+DG_DATA/sin/archivelog/2012_08_22/thre+*
*+ad_1_seq_65832.513.791978259'+*
*+ORA-00308: cannot open archived log '+DG_DATA/sin/archivelog/2012_08_22/thread_1_seq_65832.513.791978259'+*
+Recovery Manager complete.+
the error is always the same, a previous backup with RMAN was taken on tape on the source database (production).
Please help me to find what is wrong here!!

Hi mseberg
that's exactly i'm doing:
1. Create an Oracle Password File for the Auxiliary Database
a. done, passwd file created*
2. Create the Directory Structure on the remote server
a. done, all the admin structure wa created.*
3. Oracle Net Setup ( you need an entry for the CLONE in your TNSNAMES.ORA on both servers ) ( I use SID_LIST_LISTENER entry for static )
a. done, i have the entries working on my tnsnames.ora (source and target with static listeners)*
4. Create an Initialization Parameter File for the Auxiliary Instance ( I use Parameters DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to change locations)
a. done, this is my initialization file:*
*.audit_file_dest='/u01/app/oracle/admin/sin/adump'*
*.audit_trail='db'*
*.compatible='11.2.0.0.0'*
*.db_block_size=8192*
*.db_create_file_dest='DG_DATA'+*
*.db_domain=''*
*.db_files=2048*
*.db_name='sin'*
*.db_recovery_file_dest='DG_DATA'+*
*.db_recovery_file_dest_size=20G*
*.diagnostic_dest='/u01/app/oracle'*
*.dispatchers='(PROTOCOL=TCP) (SERVICE=sinXDB)'*
*.log_archive_format='%t_%s_%r.dbf'*
*.memory_target=7340032000*
*.open_cursors=300*
*.processes=2000*
*.remote_login_passwordfile='EXCLUSIVE'*
*.sessions=2205*
*.undo_tablespace='UNDOTBS1'*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/')+
LOG_FILE_NAME_CONVERT=('/u04/oradata/sin/','DG_DATA/',+*
+'/u05/oradata/sin/','+DG_DATA/',+
+'/u03/oradata/sin/','+DG_DATA/',+
+'/u02/oradata/sin/','+DG_DATA/')+
and this is my command from RMAN:
run*
*+{+*
allocate channel c1 type disk;*
allocate channel c2 type disk;*
allocate channel c3 type disk;*
allocate channel c4 type disk;*
allocate auxiliary channel a1 type disk;*
allocate auxiliary channel a2 type disk;*
set newname for datafile 1 to 'DG_DATA';+*
set newname for datafile 2 to 'DG_DATA';+*
set newname for datafile 3 to 'DG_DATA';+*
set newname for datafile 4 to 'DG_DATA';+*
set newname for datafile 5 to 'DG_DATA';+*
set newname for datafile 6 to 'DG_DATA';+*
set newname for datafile 7 to 'DG_DATA';+*
set newname for datafile 8 to 'DG_DATA';+*
set newname for datafile 9 to 'DG_DATA';+*
set newname for datafile 10 to 'DG_DATA';+*
+...+
set newname for datafile 390 to 'DG_DATA';+*
set newname for datafile 391 to 'DG_DATA';+*
duplicate target database to "sin" from active database nofilenamecheck*
DB_FILE_NAME_CONVERT=('/u10/oradata/sin/','DG_DATA/',+*
+'/u11/oradata/sin/','+DG_DATA/',+
+'/u07/oradata/sin/','+DG_DATA/',+
+'/u08/oradata/sin/','+DG_DATA/',+
+'/u09/oradata/sin/','+DG_DATA/');+
+}+
do you think the problem may be in the name of the database?, I am using the same name in the auxiliary
and when I get the error, I have the same dbid in both databases (source and destination)
Thanks
MM

Configuring Standby Database from non ASM to ASM

Hi All,
i am trying to configure a standby database from non ASM file system to ASM file system.
my primary database having datafiles in /u02,/u03,/u04 etc, and my Standby database having filesystem in ASM diskgroup DATA.
can anyone of you help me in setting up of parameters db_file_name_convert and log_file_name_convert etc,;
thanks in Advance,
TEJAS

Hi,
You can check this. May it help you
http://gavinsoorma.com/2010/04/creating-an-asm-duplicate-database-from-a-non-asm-database/

Creation of Logical Standby Database Using RMAN ACTIVE DATABASE COMMAND

Hi All,
I am in confusion how to create logical standby database from primary database using rman active database command.
What i did:-
Create primary database on machine 1 on RHEL 5 with Oracle 11gR2
Create standby database on machine 2 on RHEL 5 With Oracle 11gR2 from primary using RMAN active database command
Trying to create logical standby database on machine 3 on RHEL 5 with Oracle 11gR2 using RMAN active database command from primary.
The point which confuse me is to start the logical standby in nomount mode on machine 3 with which pfile like i create the pfile for standby database do i need to create the pfile for logical standby db.
I done the creation of logical standby database by converting physical standby to logical standby database
I am following the below mentioned doc for the same:
Creating a physical and a logical standby database in a DR environment | Chen Guang&#039;s Blog
Kindly guide me how to work over the same or please provide me the steps of the same.
Thanks in advance.

Thanks for your reply
I already started the logical standby database with pfile in nomount mode. And successfully completed the duplication of database. by mentioning the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT parameter.
But i am not able to receive the logs on the above mentioned blog i run the sql command to check the logs but getting "no rows selected"
My primary database pfile is:
pc01prmy.__db_cache_size=83886080
pc01prmy.__java_pool_size=12582912
pc01prmy.__large_pool_size=4194304
pc01prmy.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01prmy.__pga_aggregate_target=79691776
pc01prmy.__sga_target=239075328
pc01prmy.__shared_io_pool_size=0
pc01prmy.__shared_pool_size=134217728
pc01prmy.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01prmy/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01PRMY/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01PRMY/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.fal_client='PC01PRMY'
*.fal_server='PC01SBY'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='SERVICE=pc01sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pc01sby'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='DEFER'
*.log_archive_dest_state_3='DEFER'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
My logical standby pfile is:-
pc01ls.__db_cache_size=92274688
pc01ls.__java_pool_size=12582912
pc01ls.__large_pool_size=4194304
pc01ls.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
pc01ls.__pga_aggregate_target=79691776
pc01ls.__sga_target=239075328
pc01ls.__shared_io_pool_size=0
pc01ls.__shared_pool_size=125829120
pc01ls.__streams_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/pc01ls/adump'
*.audit_trail='db'
*.compatible='11.1.0.0.0'
*.control_files='/u01/app/oracle/oradata/PC01LS/controlfile/o1_mf_91g3mdtr_.ctl','/u01/app/oracle/flash_recovery_area/PC01LS/controlfile/o1_mf_91g3mf6v_.ctl'
*.db_block_size=8192
*.db_create_file_dest='/u01/app/oracle/oradata'
*.db_domain=''
*.db_file_name_convert='/u01/app/oracle/oradata/PC01SBY/datafile','/u01/app/oracle/oradata/PC01PRMY/datafile'
*.db_name='pc01prmy'
*.db_unique_name='pc01ls'
*.db_recovery_file_dest='/u01/app/oracle/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=pc01prmyXDB)'
*.log_archive_config='DG_CONFIG=(pc01prmy,pc01sby,pc01ls)'
*.log_archive_dest_1='LOCATION=/u01/app/oracle/flash_recovery_area/PC01PRMY/ VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=pc01prmy'
*.log_archive_dest_2='LOCATION=/u01/app/oracle/flash_recovery_area/PC01LS/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_3='SERVICE=pc01ls LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=pc01ls'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_max_processes=30
*.log_file_name_convert='/u01/app/oracle/oradata/PC01SBY/onlinelog','/u01/app/oracle/oradata/PC01PRMY/onlinelog'
*.open_cursors=300
*.pga_aggregate_target=78643200
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=236978176
*.undo_tablespace='UNDOTBS1'
Kindly advice over the same

_file_name_convert for normal restore

Hi,
Can I use db_file_name_convert and log_file_name_convert for normal RMAN restore.I know that the same can be used with duplicate command to restore the datafiles to a new location .But I want to use the same for normal database restore/recovery when the filesystem is different on the target and destination machines

db_file_name_convert & log_file_name_convert is to tell controlfile that earlier the files are in a location now its in different location..
this link will tell you the usage of parameter..
http://download.oracle.com/docs/cd/B13789_01/server.101/b10770/rcmsynta31.htm
http://download.oracle.com/docs/cd/B10501_01/server.920/a96536/ch144.htm#REFRN10038
Thanks

Creating physical standby using rman fails with ORA-19558: error de-allocat

Dear All,
We are creating physical stadnby database from 2 node RAC ( 2 node RAC to standalone physical standby).
While in the rman duplicate process we are getting below error, we were not able to sorted out..
No third party storage has been used ....
DB version : 11gR2 and the OS is RHEL5
Appreciate if any one hepl us to resolve this issue ...
Thanks in advance ...
RMAN-03009: failure of backup command on prmy1 channel at 10/05/2011 17:59:26
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03113: end-of-file on communication channel
Edited by: 889828 on 2011/10/06 2:17 AM

The problem is well decribed in your alert log.....you are using Oracle Managed File names which means you will not be able to duplicate the database as RMAN won't be able to automatically generate new names for the files using the DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT initialization parameters.
Youll have to use the SET NEWNAME command to specify the names of the database files. Done this a few times , and I don't recommend using OMF specifically beacuse of this hassle.
WARNING: OMF is enabled on this database. Creating a physical standby controlfile, when OMF is enabled on the primary database, requires manual RMAN intervention to resolve OMF
datafile pathnames.
NOTE: Please refer to the RMAN documentation for procedures describing how to manually resolve OMF datafile pathnames.
Problem handling is described in
Oracle® Database Backup and Recovery Reference
10g Release 2 (10.2)
Part Number B14194-03

DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT

Similar Messages

Maybe you are looking for