why duplicate fails with RMAN-05001: auxiliary filename /u01

[kytemaniac]

Hi

currently my db version is as follow:

Code: Select all

SQL*Plus: Release 10.2.0.1.0 - Production


my auxiliary db instance pfile initvbox3 is as follow:

Code: Select all

db_name=vbox3
control_files='/u01/app/oracle/oradata/vbox3/control01.ctl','/u01/app/oracle/oradata/vbox3/control02.ctl','/u01/app/oracle/oradata/vbox3/control03.ctl'
DB_FILE_NAME_CONVERT=(/u02/oradata/vbox/, /u01/app/oracle/oradata/vbox3/)
LOG_FILE_NAME_CONVERT=(/u01/app/oracle/oradata/vbox/, /u01/app/oracle/oradata/vbox3/)


my rman script for duplicate command is as follow

Code: Select all


pool log to '/home/oracle/scripts/rman/rman_duplicate.log'

duplicate target database to vbox3
pfile=/u01/app/oracle/product/10.2.0/db_1/dbs/initvbox3.ora
#logfile '/u01/app/oracle/oradata/vbox3/redo01.log' SIZE 50M REUSE,
#logfile '/u01/app/oracle/oradata/vbox3/redo02.log' SIZE 50M REUSE,
#logfile '/u01/app/oracle/oradata/vbox3/redo03.log' SIZE 50M REUSE
;

spool log off
exit



this is how I invoke rman

Code: Select all


[oracle@source ~]$ rlwrap rman target / auxiliary sys/kyt3db4@vbox3

Recovery Manager: Release 10.2.0.1.0 - Production on Fri Mar 15 00:48:15 2013

Copyright (c) 1982, 2005, Oracle.  All rights reserved.

connected to target database: VBOX (DBID=279698111)
connected to auxiliary database: VBOX3 (not mounted)

RMAN> @/home/oracle/scripts/rman/rman_duplicate.rman

RMAN> spool log to '/home/oracle/scripts/rman/rman_duplicate.log'RMAN> RMAN> 2> 3> 4> 5> 6> RMAN> RMAN>
Spooling for log turned off

Recovery Manager10.2.0.1.0

RMAN> exit

Recovery Manager complete.
[oracle@source ~]$




here's the outcome of the spool file

Code: Select all


Spooling started in log file: /home/oracle/scripts/rman/rman_duplicate.log

Recovery Manager10.2.0.1.0

RMAN>
RMAN> duplicate target database to vbox3
2> pfile=/u01/app/oracle/product/10.2.0/db_1/dbs/initvbox3.ora
3> #logfile '/u01/app/oracle/oradata/vbox3/redo01.log' SIZE 50M REUSE,
4> #logfile '/u01/app/oracle/oradata/vbox3/redo02.log' SIZE 50M REUSE,
5> #logfile '/u01/app/oracle/oradata/vbox3/redo03.log' SIZE 50M REUSE
6> ;
Starting Duplicate Db at 15-MAR-13
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=37 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/15/2013 00:48:17
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename /u01/app/oracle/oradata/vbox/redo03.log conflicts with a file used by the target database
                                                              1,0-1         Top



May I know what's wrong with my duplicate command, from http://docs.oracle.com/cd/B19306_01/bac ... m#i1006237

I've made a directory on the auxiliary host

mkdir -p /u01/app/oracle/oradata/vbox3

I don't understand why the duplicate command fails

in fact on the auxiliary host i did the following

Code: Select all

Renaming Online Logs in RMAN DUPLICATE DATABASE


while I understand it is the presence of such files that cause such errors

Code: Select all

[oracle@destination ~]$ ls -lrth /u01/app/oracle/oradata/vbox/
total 171M
-rw-r----- 1 oracle oinstall  51M Sep 14 00:39 redo03.log
-rw-r----- 1 oracle oinstall  51M Sep 14 00:39 redo02.log
-rw-r----- 1 oracle oinstall  51M Sep 14 00:49 redo01.log
-rw-r----- 1 oracle oinstall 6.8M Mar 14 21:25 control03.ctl
-rw-r----- 1 oracle oinstall 6.8M Mar 14 21:25 control02.ctl
-rw-r----- 1 oracle oinstall 6.8M Mar 14 21:25 control01.ctl
[oracle@destination ~]$




what I don't understand is that I've already invoke LOG_FILE_NAME_CONVERT, yet it never converts. Would really appreciate if someone could point out what's wrong?

thanks a lot!

[Tim...]

Hi.

The convert functions work on a "'search','replace'", or "'search','replace','search','replace'" basis, so you have to make sure that all paths in the source DB 'search' have a destination path 'replace'.

I would suggest that your convert parameter are not actually set to what you think they are.

Change them to:

Code: Select all

DB_FILE_NAME_CONVERT='/u02/oradata/vbox/', '/u01/app/oracle/oradata/vbox3/'
LOG_FILE_NAME_CONVERT='/u01/app/oracle/oradata/vbox/', '/u01/app/oracle/oradata/vbox3/'

Cheers

Tim...

[kytemaniac]

my duplcate fails with the following

Code: Select all

Spooling started in log file: /home/oracle/scripts/rman/rman_duplicate.log

Recovery Manager10.2.0.1.0

RMAN>
RMAN> duplicate target database to vbox3
2> pfile=/u01/app/oracle/product/10.2.0/db_1/dbs/initvbox3.ora
3> #logfile '/u01/app/oracle/oradata/vbox3/redo01.log' SIZE 50M REUSE,
4> #logfile '/u01/app/oracle/oradata/vbox3/redo02.log' SIZE 50M REUSE,
5> #logfile '/u01/app/oracle/oradata/vbox3/redo03.log' SIZE 50M REUSE
6> ;
Starting Duplicate Db at 15-MAR-13
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=38 devtype=DISK

contents of Memory Script:
{
   set until scn  673031;
   set newname for datafile  1 to
 "/u01/app/oracle/oradata/vbox3/system01.dbf";
   set newname for datafile  2 to
 "/u01/app/oracle/oradata/vbox3/undotbs01.dbf";
   set newname for datafile  3 to
 "/u01/app/oracle/oradata/vbox3/sysaux01.dbf";
   set newname for datafile  4 to
 "/u01/app/oracle/oradata/vbox3/users01.dbf";
   set newname for datafile  5 to
 "/u01/app/oracle/oradata/vbox3/example01.dbf";
   set newname for datafile  6 to
                                                              31,1          11%
"/u01/app/oracle/oradata/vbox3/ggs_data01.dbf";
   restore
   check readonly
   clone database
   ;
}
executing Memory Script

executing command: SET until clause
executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME
Starting restore at 15-MAR-13
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 /u01/app/oracle/oradata/vbox3/system01.dbf
restoring datafile 00002 to /u01/app/oracle/oradata/vbox3/undotbs01.dbf
restoring datafile 00003 to /u01/app/oracle/oradata/vbox3/sysaux01.dbf
restoring datafile 00004 to /u01/app/oracle/oradata/vbox3/users01.dbf
restoring datafile 00005 to /u01/app/oracle/oradata/vbox3/example01.dbf
restoring datafile 00006 to /u01/app/oracle/oradata/vbox3/ggs_data01.dbf


channel ORA_AUX_DISK_1: reading from backup piece /u02/flash_recovery_area/VBOX/backupset/2013_03_14/o1_mf_nnndf_TAG20130314T215016_8n3odskl_.bkp
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/u02/flash_recovery_area/VBOX/backupset/2013_03_14/o1_mf_nnndf_TAG20130314T215016_8n3odskl_.bkp tag=TAG20130314T215016
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:35
Finished restore at 15-MAR-13
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "VBOX3" RESETLOGS ARCHIVELOG
  MAXLOGFILES     16
  MAXLOGMEMBERS      3                                               
  MAXDATAFILES      100
  MAXINSTANCES     8
  MAXLOGHISTORY      292
 LOGFILE
  GROUP  1 ( '/u01/app/oracle/oradata/vbox3/redo01.log' ) SIZE 50 M  REUSE,
  GROUP  2 ( '/u01/app/oracle/oradata/vbox3/redo02.log' ) SIZE 50 M  REUSE,
  GROUP  3 ( '/u01/app/oracle/oradata/vbox3/redo03.log' ) SIZE 50 M  REUSE
 DATAFILE
  '/u01/app/oracle/oradata/vbox3/system01.dbf'
 CHARACTER SET AL32UTF8

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/15/2013 23:52:43
RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE failed
ORA-01130: database file version 10.2.0.1.0 incompatible with ORACLE version 10.2.0.0.0
ORA-01110: data file 1: '/u01/app/oracle/oradata/vbox3/system01.dbf'

RMAN>
RMAN> spool log off



on the source db

Code: Select all

compatible              string    10.2.0.1.0
SYS@vbox>show parameter compatible

NAME                 TYPE    VALUE
------------------------------------ ----------- ------------------------------
compatible              string    10.2.0.1.0
SYS@vbox>



Code: Select all

SYS@vbox3>show parameter compatible

NAME                 TYPE    VALUE
------------------------------------ ----------- ------------------------------
compatible              string    10.2.0




I don't understand in both source and destination
source target database

Code: Select all

SYS@vbox>select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE   10.2.0.1.0   Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production



destination / auxiliary

Code: Select all

SYS@vbox3>select * from v$version;

BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE   10.2.0.1.0   Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production

SYS@vbox3>



in the end I even set the compatible parameter for init parameter file as follow

Code: Select all


db_name=vbox3
  2 control_files='/u01/app/oracle/oradata/vbox3/control01.ctl','/u01/app/oracle    /oradata/vbox3/control02.ctl','/u01/app/oracle/oradata/vbox3/control03.ctl'
  3 DB_FILE_NAME_CONVERT=('/u02/oradata/vbox/', '/u01/app/oracle/oradata/vbox3/'    )
  4 LOG_FILE_NAME_CONVERT=('/u01/app/oracle/oradata/vbox/', '/u01/app/oracle/ora    data/vbox3/')
  5 compatible=10.2.0.1.0



my rman command file is as follow

Code: Select all

spool log to '/home/oracle/scripts/rman/rman_duplicate.log'

duplicate target database to vbox3
pfile='/u01/app/oracle/product/10.2.0/db_1/dbs/initvbox3.ora'
#logfile '/u01/app/oracle/oradata/vbox3/redo01.log' SIZE 50M REUSE,
#logfile '/u01/app/oracle/oradata/vbox3/redo02.log' SIZE 50M REUSE,
#logfile '/u01/app/oracle/oradata/vbox3/redo03.log' SIZE 50M REUSE
;

spool log off
exit




honestly speaking I don't know what's wrong? May I know how to resolve the above issue? in the end still have error.

thanks

[Tim...]

Hi.

Well, the error message is very explicit and you showed that the compatible version was indeed too low on the destination database.

After setting the compatible parameter explicitly in the auxillary instance, did you restart the instance and test the compatible setting before trying again?

Cheers

Tim...

[kytemaniac]

Now I'm able to resolve that error, but here comes another error.....

Code: Select all

piece handle=/u02/flash_recovery_area/VBOX/backupset/2013_03_16/o1_mf_annnn_20130316_8n6rjms6_.bkp tag=20130316
restore not complete
Restore did not complete for archived log thread 1sequence 9 from backup piece /u02/flash_recovery_area/VBOX/backupset/2013_03_16/o1_mf_annnn_20130316_8n6rjms6_.bkp (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/16/2013 02:18:27
RMAN-03015: error occurred in stored script Memory Script
RMAN-20506: no backup of archivelog found
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 9 lowscn 673031 found to restore




but backup of archivelog from sequence 9 is available

Code: Select all

RMAN> list backup of archivelog from sequence 9;

using target database control file instead of recovery catalog

List of Backup Sets
===================

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5       52.15M     DISK        00:00:03     16-MAR-13     
        BP Key: 5   Status: AVAILABLE  Compressed: NO  Tag: 20130316
        Piece Name: /u02/flash_recovery_area/VBOX/backupset/2013_03_16/o1_mf_annnn_20130316_8n6rjms6_.bkp

  List of Archived Logs in backup set 5
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    9       673031     14-MAR-13 692738     16-MAR-13
  1    10      692738     16-MAR-13 694922     16-MAR-13



Code: Select all

ls -lrth /u02/flash_recovery_area/VBOX/backupset/2013_03_16/o1_mf_annnn_20130316_8n6rjms6_.bkp
-rw-r----- 1 oracle oinstall 46M Mar 16 02:05 /u02/flash_recovery_area/VBOX/backupset/2013_03_16/o1_mf_annnn_20130316_8n6rjms6_.bkp



Now while that error is very obvious, what I found puzzling is that backup of archivelog log is available at the host, why must rman complain

thanks a lot!

[Tim...]

Hi.

Not really sure. Is the duplicate using a different backup location? If so, has this backup been moved to that backup location along with the datafile backup?

Cheers

Tim...

[kytemaniac]

yes both of them are using the same backup location. also i have scp all the backups, in fact now I'm facing the issue of

Code: Select all

contents of Memory Script:
{
   shutdown clone;
   startup clone nomount pfile= '/u01/app/oracle/product/10.2.0/db_1/dbs/initVBOX3.ora';
}
executing Memory Script


forever hang, I don't what went wrong now, seems that my system has really run out of memory.....

again here's my rman duplicate script

Code: Select all


pool log to '/home/oracle/scripts/rman/rman_duplicate.log'

duplicate target database to 'VBOX3'
pfile='/u01/app/oracle/product/10.2.0/db_1/dbs/initVBOX3.ora'
#logfile '/u01/app/oracle/oradata/vbox3/redo01.log' SIZE 50M REUSE,
#logfile '/u01/app/oracle/oradata/vbox3/redo02.log' SIZE 50M REUSE,
#logfile '/u01/app/oracle/oradata/vbox3/redo03.log' SIZE 50M REUSE
until sequence 9
;

spool log off
exit




...need to add something more

Code: Select all

RMAN> list backup of archivelog sequence between 1 and 8;


List of Backup Sets
===================

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
1       76.85M     DISK        00:00:05     14-MAR-13     
        BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: VBOX_20130214
        Piece Name: /u02/flash_recovery_area/VBOX/backupset/2013_03_14/o1_mf_annnn_VBOX_20130214_8n3odktt_.bkp

  List of Archived Logs in backup set 1
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    6       630097     02-SEP-12 655817     10-SEP-12
  1    7       655817     10-SEP-12 672929     14-MAR-13

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
3       1.06M      DISK        00:00:00     14-MAR-13     
        BP Key: 3   Status: AVAILABLE  Compressed: NO  Tag: VBOX_20130214
        Piece Name: /u02/flash_recovery_area/VBOX/backupset/2013_03_14/o1_mf_annnn_VBOX_20130214_8n3ogjk4_.bkp

  List of Archived Logs in backup set 3
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    8       672929     14-MAR-13 673031     14-MAR-13




it seems that there' no backup of archivelog from 1 to 5

Code: Select all


RMAN> list backup of archivelog from sequence 9;


List of Backup Sets
===================

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5       52.15M     DISK        00:00:03     16-MAR-13     
        BP Key: 5   Status: AVAILABLE  Compressed: NO  Tag: 20130316
        Piece Name: /u02/flash_recovery_area/VBOX/backupset/2013_03_16/o1_mf_annnn_20130316_8n6rjms6_.bkp

  List of Archived Logs in backup set 5
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    9       673031     14-MAR-13 692738     16-MAR-13
  1    10      692738     16-MAR-13 694922     16-MAR-13




so when should i recover to?

thanks

[Tim...]

Hi.

I think you should probably take a fresh backup and start your duplication using that. At least then you will know what is going on.

If you can't do that, you can only recover to the first gap. Is the gap from before your backup? If so, then you don't care about the gap as the backup is newer than it.

Cheers

Tim...

[kytemaniac]

here's my investigation

Code: Select all

RMAN> list backup of database;

using target database control file instead of recovery catalog

List of Backup Sets
===================

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
2       Full    614.58M    DISK        00:00:49     14-MAR-13     
        BP Key: 2   Status: AVAILABLE  Compressed: NO  Tag: TAG20130314T215016
        Piece Name: /u02/flash_recovery_area/VBOX/backupset/2013_03_14/o1_mf_nnndf_TAG20130314T215016_8n3odskl_.bkp
  List of Datafiles in backup set 2
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 673010     14-MAR-13 /u02/oradata/vbox/system01.dbf
  2       Full 673010     14-MAR-13 /u02/oradata/vbox/undotbs01.dbf
  3       Full 673010     14-MAR-13 /u02/oradata/vbox/sysaux01.dbf
  4       Full 673010     14-MAR-13 /u02/oradata/vbox/users01.dbf
  5       Full 673010     14-MAR-13 /u02/oradata/vbox/example01.dbf
  6       Full 673010     14-MAR-13 /u02/oradata/vbox/ggs_data01.dbf



SCN 673010


there's no backup of archivelog for sequence between 1 and 5

Code: Select all

RMAN> list backup of archivelog sequence between 1 and 5;


while's there's backup of archivelog from sequence 6

Code: Select all


RMAN> list backup of archivelog from sequence 6;


List of Backup Sets
===================

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
1       76.85M     DISK        00:00:05     14-MAR-13     
        BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: VBOX_20130214
        Piece Name: /u02/flash_recovery_area/VBOX/backupset/2013_03_14/o1_mf_annnn_VBOX_20130214_8n3odktt_.bkp

  List of Archived Logs in backup set 1
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    6       630097     02-SEP-12 655817     10-SEP-12
  1    7       655817     10-SEP-12 672929     14-MAR-13

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
3       1.06M      DISK        00:00:00     14-MAR-13     
        BP Key: 3   Status: AVAILABLE  Compressed: NO  Tag: VBOX_20130214
        Piece Name: /u02/flash_recovery_area/VBOX/backupset/2013_03_14/o1_mf_annnn_VBOX_20130214_8n3ogjk4_.bkp

  List of Archived Logs in backup set 3
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    8       672929     14-MAR-13 673031     14-MAR-13

BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5       52.15M     DISK        00:00:03     16-MAR-13     
        BP Key: 5   Status: AVAILABLE  Compressed: NO  Tag: 20130316
        Piece Name: /u02/flash_recovery_area/VBOX/backupset/2013_03_16/o1_mf_annnn_20130316_8n6rjms6_.bkp

  List of Archived Logs in backup set 5
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    9       673031     14-MAR-13 692738     16-MAR-13
  1    10      692738     16-MAR-13 694922     16-MAR-13

RMAN> list backup of archivelog sequence between 1 and 5;



SCN 692738

so for your question Is the gap from before your backup? I don't know how to answer. if my backup is newer that the gap, what should I do with the duplicate command?

thanks

[kytemaniac]

I invoke rman from the primary/ target database

Code: Select all


[oracle@source ~]$ rlwrap rman target / auxiliary sys@VBOX3


towards the end of the spool file, I encountered the following:

Code: Select all

contents of Memory Script:
{
   shutdown clone;
   startup clone nomount pfile= '/u01/app/oracle/product/10.2.0/db_1/dbs/initVBOX3.ora';
}
executing Memory Script

database dismounted
Oracle instance shut down

connected to auxiliary database (not started)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 03/16/2013 11:18:38
RMAN-03015: error occurred in stored script Memory Script
RMAN-04014: startup failed: ORA-01078: failure in processing system parameters
RMAN-04017: startup error description: LRM-00109: could not open parameter file '/u01/app/oracle/product/10.2.0/db_1/dbs/initVBOX3.ora'



I simply don't understand why the above happens. maybe someone can enlighten me on how to resolve this? thanks

[kytemaniac]

HI this time I managed to resolve the issue, I simply invoke duplicate command at the destination/auxiliary side.

Code: Select all

[oracle@destination ~]$ rlwrap rman target sys@vbox auxiliary /



But there's some thing I want to add on is that we should also set others parameters like dump destination

on the primary side

Code: Select all

SQL> set sqlprompt "_user'@'_connect_identifier>"
SYS@vbox>show parameter dump

NAME                 TYPE    VALUE
------------------------------------ ----------- ------------------------------
background_core_dump           string    partial
background_dump_dest           string    /u01/app/oracle/admin/vbox/bdu
                   mp
core_dump_dest              string    /u01/app/oracle/admin/vbox/cdu
                   mp
max_dump_file_size           string    UNLIMITED
shadow_core_dump           string    partial
user_dump_dest              string    /u01/app/oracle/admin/vbox/udu
                   mp




on the secondary/auxiliary instance

Code: Select all


SYS@VBOX3>show parameter dump

NAME                 TYPE    VALUE
------------------------------------ ----------- ------------------------------
background_core_dump           string    partial
background_dump_dest           string    /u01/app/oracle/product/10.2.0
                   /db_1/rdbms/log
core_dump_dest              string    /u01/app/oracle/product/10.2.0
                   /db_1/dbs
max_dump_file_size           string    UNLIMITED
shadow_core_dump           string    partial
user_dump_dest              string    /u01/app/oracle/product/10.2.0
                   /db_1/rdbms/log
SYS@VBOX3>




Tim, is it advisable we actually just create a pfile from the primary/ target database and copy to the secondary/ auxiliary side, of course, we also need to edit certain parameters, before we use it to start the instance.

Tim, thanks so much for your guidance.

[Tim...]

Hi.

In my article we are duplicating to a different machine with the same file system, so we don't have to bother with a fill pfile. Notice the duplicate command include the SPFILE clause, meaning we will transfer the SPFILE as part of the process. In this case adding more parameter to the pfile is pointless as all the parameter we need are in the SPFILE.

If you are not planning on pulling across the SPFILE, for example because you are cloning to the same machine and need different parameter values, it makes sense to manually create the pfile or spfile with the correct values in advance. I will add this statement to the article to make it more clear.

Cheers

Tim...