RMAN Duplication without a connection

I have so many names for this. Essentially thought the initial impetus was doing an RMAN duplication without any connection between the systems. That quickly led to many interesting things I had to figure out – mainly – why does ASM copy not work. Most everyone I asked said it didn’t work for them either and they used the filesystem or something else. In the end I discovered it is just a matter of understanding ASM copy. So, without further ado, I’ll just dump all the words I collected doing this and hope it is useful.

Short List

This is a simple list of the things you need to do to get through this process. I hope I have it all as this was quick and not supposed to be a thorough presentation.

  • Setup listener with hard-coded entry for the target/auxiliary database
  • Setup tnsnames to for dedicated connection to the target/auxiliary
  • Determine files needed
  • Copy files from source to target/auxiliary
  • Prepare the auxiliary (nomount,single instance)
  • Cleanup old files
  • Determine time to recover to
  • RMAN duplicate using “until time” and “backup location”
  • Fix your control files and create spfile
  • Convert back to RAC

Fun with RMAN duplication without a connection

This is long and I’d love to format it nicely for you, but I just don’t have the time. Either way it is a good example of some of these issues.

Pre-work

This post is to assist you in the case you want to duplicate a RAC to another RAC.
Specifically I was wanting to find out what was needed to do this without having the backups mounted on the target and without a database connection.
That is – there is no connection from the source to the target, and no recovery catalog database.
If you have the connections it is much simpler, especially when using the slick “DUPLICATE TARGET DATABASE … FROM ACTIVE DATABASE”
The real trick to this process is realizing that you don’t need the backups with the original names, in fact, the name of the files does not matter (as you’ll see.)

Please note that Oracle terminology in RMAN can make this confusing.
In RMAN the database you are backing up is the Target. This makes sense, but when doing “duplicate” it can be confusing.
In this document I talk about:
“the Source” – that is the RMAN Target, the database I’m using to make a new database.
“the Target” – that is the RMAN Auxiliary , the database I’m creating as a duplicate of the source.

TNSNAMES.ORA
You need this in the Target (RMAN Auxiliary) server tnsnames.ora – so you can later “connect auxiliary”:
Add dedicated server entries to DB Home in tnsnames.ora (for DB home on whatever server you plan to connect from)
VODWSTG_D =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = kdb-ch2-a1s.sys.comcast.net)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = vodwstg)
)
)

LISTENER.ORA
You need this in the Target (RMAN Auxiliary) grid listener.ora
Static entries to listener on source so you can connect in nomount mode
lsnrctl reload seems to blow up listener so I stopped and started the listener resource on that node only
note: Case is important in global_dbname and sid_name – It MUST match that of database sid.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME =vodwstg)
(ORACLE_HOME =/u01/oracle/11.2.0.3/db/)
(SID_NAME = vodwstg_1)
)
)

First determine files needed to duplicate the database

RMAN> list backup of archivelog all;

BS Key  Size       Device Type Elapsed Time Completion Time
——- ———- ———– ———— —————
879     1.06M      DISK        00:00:00     13-MAY-13
BP Key: 879   Status: AVAILABLE  Compressed: YES  Tag: TAG20130513T185335
Piece Name: +FRA/vodwprd/backupset/2013_05_13/annnf0_tag20130513t185335_0.433.815338417

List of Archived Logs in backup set 879
Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
—- ——- ———- ——— ———- ———
1    938     10888351934687 13-MAY-13 10888351935346 13-MAY-13
2    782     10888351934691 13-MAY-13 10888351935325 13-MAY-13
3    944     10888351934683 13-MAY-13 10888351935351 13-MAY-13

Based on this we can duplicate to SCN 10888351935325 which is the lowest SCN in all logs in this last backup of archivelogs.


Starting restore at 13-MAY-13
using channel ORA_DISK_1
channel ORA_DISK_1: starting validation of datafile backup set
channel ORA_DISK_1: reading from backup piece +FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237
channel ORA_DISK_1: piece handle=+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237 tag=TAG20130513T180036
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: validation complete, elapsed time: 00:06:25
Finished restore at 13-MAY-13

So, what is needed to restore/recover?
We need from TAG20130513T180036 for the datafile, to TAG20130513T185335 for the archivelog backups.

RMAN> list backup summary;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
——- — — – ———– ————— ——- ——- ———- —

876     B  F  A DISK        13-MAY-13       1       1       YES        TAG20130513T180036
877     B  A  A DISK        13-MAY-13       1       1       YES        TAG20130513T185136
878     B  F  A DISK        13-MAY-13       1       1       NO         TAG20130513T185145
879     B  A  A DISK        13-MAY-13       1       1       YES        TAG20130513T185335

Using “list backup tag=…”, I should need:
Piece Name: +FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237
Piece Name: +FRA/vodwprd/backupset/2013_05_13/annnf0_tag20130513t185136_0.316.815338297
Piece Name: +FRA/vodwprd/autobackup/2013_05_13/s_815338305.321.815338305
Piece Name: +FRA/vodwprd/backupset/2013_05_13/annnf0_tag20130513t185335_0.433.815338417

Copy file from source to target

ASMCMD [+FRA/VODWPRD/BACKUPSET/2013_05_13] > cp +FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237 sys@kdb-ch2-a3s.sys.comcast.net.+ASM3:+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237
Enter password: *********
copying +FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237 -> kdb-ch2-a3s.sys.comcast.net:+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237
ASMCMD-8016: copy source->’+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237′ and target->’+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237′ failed

huh? that error isn’t very helpful. Let’s look the alert log
Mon May 13 19:10:43 2013
Errors in file /u01/oracle/grid/diag/asm/+asm/+ASM3/trace/+ASM3_ora_30958.trc:
ORA-15046: ASM file name ‘+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237′ is not in single-file creation form

Oh yes, only Oracle can create files with database incarnation and file number.
Of course if you had just specified the target directory you would have had the same result as it implies the full file name.

OK, maybe without the incarnation and file number:
ASMCMD [+] > cp +FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237 sys@kdb-ch2-a3s.sys.comcast.net.+ASM3:+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0
Enter password: *********
copying +FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237 -> kdb-ch2-a3s.sys.comcast.net:+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0
ASMCMD-8016: copy source->’+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237′ and target->’+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0’ failed

It errored again, let us look at the log file again:
Mon May 13 19:10:43 2013
Errors in file /u01/oracle/grid/diag/asm/+asm/+ASM3/trace/+ASM3_ora_30958.trc:
ORA-15046: ASM file name ‘+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237’ is not in single-file creation form

Huh? I did not specify single-file creation form. Strangely enough, it is because the target directory isn’t there.
So, on the target system create the directories in asmcmd, then try it again:

ASMCMD [+] > cp +FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237 sys@kdb-ch2-a3s.sys.comcast.net.+ASM3:+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0
Enter password: *********
copying +FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0.429.815335237 -> kdb-ch2-a3s.sys.comcast.net:+FRA/vodwprd/backupset/2013_05_13/nnndf0_tag20130513t180036_0
ASMCMD [+] >

That looks better. Let’s take a look on the target system:

ASMCMD [+] > ls -ls +FRA/VODWPRD/BACKUPSET/2013_05_13
Type       Redund  Striped  Time             Sys  Block_Size   Blocks        Bytes        Space  Name
N                                                   nnndf0_tag20130513t180036_0 => +FRA/ASM/BACKUPSET/nnndf0_tag20130513t180036_0.1043.815339727
ASMCMD [+] > ls -ls +FRA/ASM/BACKUPSET/nnndf0_tag20130513t180036_0.1043.815339727
Type       Redund  Striped  Time             Sys  Block_Size   Blocks        Bytes        Space  Name
BACKUPSET  UNPROT  COARSE   MAY 13 19:00:00  Y          8192  1952109  15991676928  15992881152  nnndf0_tag20130513t180036_0.1043.815339727

Well, it appears to be there. Oracle copied to its own location with a full file name and then created an alias for us.
Hey, at least it is there. So, I copied over all the other files too.

Now, if we CATALOG the files as they are on the target system, RMAN should know what is in them and hopefully the name won’t matter.
On the target now:
RMAN> catalog backuppiece ‘+FRA/ASM/BACKUPSET/nnndf0_tag20130513t180036_0.1043.815339727’;
using target database control file instead of recovery catalog
ORA-19870: error while restoring backup piece +FRA/asm/backupset/nnndf0_tag20130513t180036_0.1043.815339727
ORA-19691: +FRA/asm/backupset/nnndf0_tag20130513t180036_0.1043.815339727 is from different database: id=3140027952, name=VODWPRD

Hmmm…. this would be worth looking into more (tried setting dbid before and after connect but does not work); however,
Since we know where the backup resides on the target, maybe we should try the duplicate using the BACKUP LOCATION clause.

Prepare the Auxiliary

Unless you’re really sure you can lose the current Target database (if you had one already), run an RMAN backup of your database before you blow it away.

Now we need to put the auxiliary into single instance mode.
backup the existing init file
cp initvodwstg_1.ora initvodwstg_1.dupback
Create a new init file to modify for single instance
create pfile=’initvodwstg_1.single’ from spfile;
Modify that file
remove:
local instance parameters <e.g. vodwstg_?.__*>
*.cluster_database=TRUE
*.instance_number=?
*.local_listener=’?’
*.thread=?
add, if needed:
*.db_file_name_convert=’+DATA/VODWPRD’,’+DATA/VODWSTG’
*.log_file_name_convert=’+DATA/VODWPRD’,’+DATA/VODWSTG’,’+FRA/VODWPRD’,’+FRA/VODWSTG’
*.undo_management=’AUTO’
*.undo_retention=3600
*.undo_tablespace=’UNDOTBS1’
To get around having only 1 controlfile at the end, modify control files to multiple file format, e.g.
*.control_files=’+DATA’,’+FRA’

Shutdown RAC database
srvctl stop database -d vodwstg
Copy in single instance pfile
cp initvodwstg_1.single initvodwstg_1.ora
Try starting as single instance
sqlplus / as sysdba
startup nomount pfile=’initvodwstg_1.ora’

Auxiliary:
Now cleanup the datafiles and controlfiles for your database
should all be in +DATA. Check v$datafile, and control_files param
Be careful not to get another database.

 

Duplicate to the Auxiliary

on target:

RMAN> duplicate database vodwprd to vodwstg until scn 10888351935325 backup location ‘+FRA/VODWPRD/BACKUPSET/2013_05_13′;
Starting Duplicate Db at 13-MAY-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/13/2013 20:28:11
RMAN-05501: aborting duplication of target database
RMAN-05542: Only UNTIL TIME can be used with DUPLICATE without TARGET and CATALOG connections

Oh geez.

vodwprd> select scn_to_timestamp(10888351935325) from dual;

SCN_TO_TIMESTAMP(10888351935325)
—————————————————————————
13-MAY-13 06.53.26.000000000 PM

RMAN> duplicate database vodwprd to vodwstg until time “to_date(’13-MAY-13 06.53.26PM’,’dd-mon-yy hh:mi:sspm’)” backup location ‘+FRA/VODWPRD/BACKUPSET/2013_05_13′;
Starting Duplicate Db at 13-MAY-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/13/2013 20:33:54
RMAN-05501: aborting duplication of target database
RMAN-05574: CONTROLFILE backup not found for database VODWPRD created before to_date(’13-MAY-13 06.53.26PM’,’dd-mon-yy hh:mi:sspm’) in +FRA/VODWPRD/BACKUPSET/2013_05_13

Hmm, let’s go find that on the Source.

RMAN> list backup of controlfile;

BS Key  Type LV Size       Device Type Elapsed Time Completion Time
——- —- — ———- ———– ———— —————
878     Full    18.83M     DISK        00:00:00     13-MAY-13
BP Key: 878   Status: AVAILABLE  Compressed: NO  Tag: TAG20130513T185145
Piece Name: +FRA/vodwprd/autobackup/2013_05_13/s_815338305.321.815338305
Control File Included: Ckp SCN: 10888351934883   Ckp time: 13-MAY-13

Note: Be sure to find one prior to the time (or SCN specified). In this case this was 2 control file backups prior to the last taken.
Another Note: You only “connect as auxiliary” as you don’t have access to the Source or an RMAN Catalog.

RMAN> connect auxiliary sys/********@vodwstg_d
RMAN> duplicate database vodwprd to vodwstg until time “to_date(’13-MAY-13 06.53.26PM’,’dd-mon-yy hh:mi:sspm’)” backup location ‘+FRA/VODWPRD/BACKUPSET/2013_05_13′;
Starting Duplicate Db at 13-MAY-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/13/2013 20:40:41
RMAN-05501: aborting duplication of target database
RMAN-05574: CONTROLFILE backup not found for database VODWPRD created before to_date(’13-MAY-13 06.53.26PM’,’dd-mon-yy hh:mi:sspm’) in +FRA/VODWPRD/BACKUPSET/2013_05_13

OK, let’s copy that controlfile backup, but instead of using autobackup, let us put it in the same directory as the other backup files on the Target

ASMCMD [+] > cp +FRA/vodwprd/autobackup/2013_05_13/s_815338305.321.815338305 sys@kdb-ch2-a3s.sys.comcast.net.+ASM3:+FRA/vodwprd/backupset/2013_05_13/s_815338305
Enter password: *********
copying +FRA/vodwprd/autobackup/2013_05_13/s_815338305.321.815338305 -> kdb-ch2-a3s.sys.comcast.net:+FRA/vodwprd/backupset/2013_05_13/s_815338305
ASMCMD [+] >

Now, let us try the duplicate again:

RMAN> duplicate database vodwprd to vodwstg until time “to_date(’13-MAY-13 06.53.26PM’,’dd-mon-yy hh:mi:sspm’)” backup location ‘+FRA/VODWPRD/BACKUPSET/2013_05_13’;

Starting Duplicate Db at 13-MAY-13
contents of Memory Script:
{
sql clone “create spfile from memory”;
}
executing Memory Script

channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to +data
channel ORA_AUX_DISK_1: restoring datafile 00002 to +data

contents of Memory Script:
{
Alter clone database open resetlogs;
}
executing Memory Script
database opened
Finished Duplicate Db at 13-MAY-13

Honestly, I’m a little shocked that it appears to have worked!

Find control_files and create new spfil

Here is one of those points where I ran into issues – starting in RAC mode.
The reason is that the control_files have changed and the duplicated single instance has its own local spfile.
This gave me headaches the first time around, and it is one of those places you just want to make sure of things.
Find out where your control files and spfile are:

VODWSTG> show parameter control_files

NAME                                 TYPE        VALUE
———————————— ———– ————————————————-
control_files                        string      +DATA/vodwstg/controlfile/current.331.815409617,
+FRA/vodwstg/controlfile/current.310.815409617
VODWSTG> show parameter spfile
NAME                                 TYPE        VALUE
———————————— ———– ————————————————
spfile                               string      /u01/oracle/11.2.0.3/db/dbs/spfilevodwstg_1.ora

If we check for this spfile on the file system, we discover it isn’t there:
->ll /u01/oracle/11.2.0.3/db/dbs/spfilevodwstg_1.ora
ls: cannot access /u01/oracle/11.2.0.3/db/dbs/spfilevodwstg_1.ora: No such file or directory

Since we are going to switch back to the RAC init file, that will point us to the correct spfile on ASM anyway.
The only problem that causes is that the old spfile will have the original control files in it.
Let’s see what happens.

We need to convert it back to RAC now.

Shutdown single instance
shutdown immediate
Copy original init file back
cp initvodwstg_1.dupback initvodwstg_1.ora
Start RAC database
srvctl start database -d vodwstg

VODWSTG> shutdown immediate
exit
Database closed.
Database dismounted.
ORACLE instance shut down.
VODWSTG> Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 – 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
(oracle) kdb-ch2-a1s:vodwstg_1:/u01/oracle/11.2.0.3/db/dbs
->cp initvodwstg_1.dupback initvodwstg_1.ora
(oracle) kdb-ch2-a1s:vodwstg_1:/u01/oracle/11.2.0.3/db/dbs
->cat initvodwstg_1.ora
SPFILE=’+DATA/vodwstg/spfilevodwstg.ora’
(oracle) kdb-ch2-a1s:vodwstg_1:/u01/oracle/11.2.0.3/db/dbs
->srvctl start database -d vodwstg
PRCR-1079 : Failed to start resource ora.vodwstg.db
CRS-5017: The resource action “ora.vodwstg.db start” encountered the following error:
ORA-00205: error in identifying control file, check alert log for more info
. For details refer to “(:CLSN00107:)” in “/u01/oracle/11.2.0.3/grid/log/kdb-ch2-a2s/agent/crsd/oraagent_oracle/oraagent_oracle.log”.

Yep, couldn’t start because it couldn’t find the control files. As expected.
We’ll nomount RAC instance 1

(oracle) kdb-ch2-a1s:vodwstg_1:/u01/oracle/11.2.0.3/db/dbs
->srvctl start instance -d vodwstg -i vodwstg_1 -o nomount

vodwstg> show parameter spfile
NAME                                 TYPE        VALUE
———————————— ———– ——————————–
spfile                               string      +DATA/vodwstg/spfilevodwstg.ora
vodwstg> show parameter control_files
NAME                                 TYPE        VALUE
———————————— ———– ——————————
control_files                        string      +DATA/vodwstg/controlfile/current.327.813084741,
+FRA/vodwstg/controlfile/current.1148.813084741

Notice that they aren’t the new control files we had after duplicating.

alter system set control_files = ‘+DATA/vodwstg/controlfile/current.331.815409617′,’+FRA/vodwstg/controlfile/current.310.815409617′ scope=spfile sid=’*’;

So, let us change those (if you didn’t find out what they were before shutting down the single instance, just look in ASM and find them):

vodwstg> alter system set control_files = ‘+DATA/vodwstg/controlfile/current.331.815409617′,’+FRA/vodwstg/controlfile/current.310.815409617′ scope=spfile sid=’*’;
System altered.

(oracle) kdb-ch2-a1s:vodwstg_1:/u01/oracle/11.2.0.3/db/dbs
->srvctl stop instance -d vodwstg -i vodwstg_1
(oracle) kdb-ch2-a1s:vodwstg_1:/u01/oracle/11.2.0.3/db/dbs
->srvctl start database -d vodwstg
(oracle) kdb-ch2-a1s:vodwstg_1:/u01/oracle/11.2.0.3/db/dbs
->

->srvctl status database -d vodwstg
Instance vodwstg_1 is running on node kdb-ch2-a1s
Instance vodwstg_2 is running on node kdb-ch2-a2s
Instance vodwstg_3 is running on node kdb-ch2-a3s

vodwstg> select inst_id, host_name, startup_time, status, database_status from gv$instance;

INST_ID HOST_NAME                      STARTUP_T STATUS       DATABASE_STATUS
———- —————————— ——— ———— —————–
1 kdb-ch2-a1s.sys.comcast.net    14-MAY-13 OPEN         ACTIVE
3 kdb-ch2-a3s.sys.comcast.net    14-MAY-13 OPEN         ACTIVE
2 kdb-ch2-a2s.sys.comcast.net    14-MAY-13 OPEN         ACTIVE

 

Followup

Verify you control files are laid out appropriately
Verify you have REDO Logs for each node and laid out appropriately
Verify you have UNDO tablespaces for each node (if increasing the number of nodes)
Verify you have a RAC instance running on each node of your cluster that you want them
Other good stuff…

Other…

So, now I wondered. What if the file names are completely different, or what if I have to put them on a local file system.
Will that work.

Let’s go all out, and put them on a local filesystem, and change their names.

->ll /sharedfs/tmp
total 15657608
-rw-r—– 1 oracle dba    20825600 May 14 15:58 jed1.bk
-rw-r—– 1 oracle dba     1112064 May 14 15:59 jed2.bk
-rw-r—– 1 oracle dba 15991676928 May 14 16:02 jed3.bk
-rw-r—– 1 oracle dba    19759104 May 14 16:14 jed4.bk

and then for good measure, remove all the VODWPRD files, and verify they aren’t there anymore:

ASMCMD [+FRA] > ls
JED/
VODTPRD/
VODTSTG/
VODWSTG/

Now, we should be good to try another duplication after restarting in single mode. We just need to modify the BACKUP LOCATION

RMAN> duplicate database vodwprd to vodwstg until time “to_date(’13-MAY-13 06.53.26PM’,’dd-mon-yy hh:mi:sspm’)” backup location ‘/sharedfs/tmp’;
Starting Duplicate Db at 14-MAY-13
contents of Memory Script:
{
sql clone “create spfile from memory”;
}
executing Memory Script

You can see here, that the name doesn’t matter, Oracle figures it out:

contents of Memory Script:
{

restore clone primary controlfile from  ‘/sharedfs/tmp/jed4.bk’;
alter clone database mount;

channel ORA_AUX_DISK_1: restoring datafile 00018 to +data
channel ORA_AUX_DISK_1: reading from backup piece /sharedfs/tmp/jed3.bk

Thoughts

I really hope in 12c they can make this easier still. The old days when you created an ASCII controlfile and did it by hand were much easier.
Of course, if there is something I’m doing here and there is an easier way, PLEASE let me know.

 

If your controlfiles aren’t how you like them (e.g. only one, all in one filesystem, etc.)

Change control_files=’+DATA’,’+FRA’ then nomount, “restore controlfile from ‘<current>’;”, and mount, open

alter system set control_files=’+DATA’,’+FRA’scope=spfile;
show parameter control_files
NAME                                 TYPE        VALUE
———————————— ———– ——————————
control_files                        string      +DATA/vodwstg/controlfile/curr
ent.263.812318013
srvctl stop database -d vodwstg
srvctl start instance -d vodwstg -i vodwstg_1 -o nomount
rman target /
restore controlfile from ‘+DATA/vodwstg/controlfile/current.263.812318013’;
exit
srvctl start database -d vodwstg
show parameter control_files

 

The End

One response to “RMAN Duplication without a connection

  1. Pingback: RMAN Duplication without a connection | Jed's

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s