[Veritas-bu] RMAN - Duplicate Database with Veritas to new server
Earlier this year I was asking about Duplicate Database problems with
NetBackup and Oracle.
Here's the thread from the Oracle-L list. I think I asked on this list as
well.
http://www.freelists.org/archives/oracle-l/05-2007/msg00324.html
Well, it's back, and this time with a solution.
It seems I've spent a lot of time lately chasing down NetBackup
idiosyncrasies.
This is NetBackup 5.1 MP5 on Windows 2003.
If interested, read the referenced thread, it isn't very long.
Here's the solution.
This does NOT work:
RUN
{
allocate auxiliary channel C1 device type 'sbt'
parms="ENV=(NB_ORA_POLICY=ORA_client,NB_ORA_SCHED=OracleBackup,NB_ORA_CLIENT=client,NB_ORA_SERV=nbu)";
allocate auxiliary channel C2 device type 'sbt'
parms="ENV=(NB_ORA_POLICY=ORA_client,NB_ORA_SCHED=OracleBackup,NB_ORA_CLIENT=client,NB_ORA_SERV=nbu)";
set until time "to_date('08/07/2007 06:08:00','mm/dd/ hh24:mi:ss')";
DUPLICATE TARGET DATABASE TO ORCL;
}
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03002: failure of Duplicate Db command at 08/07/2007 13:41:22
RMAN-03015: error occurred in stored script Memory Script
ORA-19507: failed to retrieve sequential file,
handle="APP_T20070806_db_s1075_p1_t629896012", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Backup file not found in NetBackup
catalog
RMAN> **end-of-file**
This however, DOES work:
RUN
{
allocate auxiliary channel C1 device type 'sbt';
allocate auxiliary channel C2 device type 'sbt';
send
"NB_ORA_POLICY=ORA_client,NB_ORA_SCHED=OracleBackup,NB_ORA_CLIENT=client,NB_ORA_SERV=nbu";
set until time "to_date('08/07/2007 06:08:00','mm/dd/ hh24:mi:ss')";
DUPLICATE TARGET DATABASE TO ORCL;
}
Setting up the parameters with the ALLOCATE CHANNEL command does not work
with DUPLICATE
DATABASE and NetBackup.
Using the SEND command to set the parameters does work.
This is a problem that has been reported in the past on MetaLink, and I
thought Veritas had it fixed, as
it does work now for making backups and with automatic channels.
Apparently they missed a spot.
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] RMAN - Duplicate Database with Veritas to new server
On 5/16/07, ryeddu <[EMAIL PROTECTED]> wrote: Did you make the modification son the Netbackup Master server, for an alternate (destsination) client to see the Source client. There is and altnames directory created on the master server. I see I missed this message earlier. Thanks, already familiar with altnames, that wasn't the problem. Never did get the DUPLICATE to work, though a restore did work. Strange. I've done this before, but I have found strange problems before with NBU and RMAN. -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] RMAN - Duplicate Database with Veritas to new server
So I'm trying to run a duplicate database with RMAN
and having some trouble getting it to work.
Platform:
(Target Database)
Node A: PRD
RH Linux 4
Oracle 9.2.0.6
Veritas client 5.1
Oracle owner: oraprod
(Auxiliary Instance)
Node B: DEV
RH Linux 4
Oracle 9.2.0.6
Veritas client 5.1
Oracle owner: oradev
Veritas Master Server: Windows 2003, Veritas 5.1 MP5
Here is what is not working:
Login to RMAN:
$ORACLE_HOME/bin/rman target nbu/[EMAIL PROTECTED] auxiliary / nocatalog
Run duplicate script:
The ENV variables are set to the values used when the backup was created on
Node A.
run {
allocate auxiliary channel clone_db_2 device type 'sbt'
parms="ENV=(NB_ORA_CLIENT=PRD,NB_ORA_POLICY=ORA_PRD_full,NB_ORA_SERV=nbu_server,NB_ORA_SCHED=Daily-Full)";
set newname for datafile 1 to
'/u01/oracle/dev/devdata/dbf/prod_system_01.dbf';
...
set newname for datafile 46 to
'/u01/oracle/dev/devdata/dbf/sysdba01.dbf';
set until time "to_date('05/05/2007 12:00:00','mm/dd/
hh24:mi:ss')";
DUPLICATE TARGET DATABASE TO DEV
LOGFILE
GROUP 1
...
SIZE 20M;
}
The syntax of the script is fine - no parsing errors occur.
Unnecessary bits have been edited out for conciseness.
Output:
connected to target database: PROD (DBID=15620415)
using target database controlfile instead of recovery catalog
connected to auxiliary database: DEV (not mounted)
RMAN>
RMAN>
RMAN> run {
2>
3>
4>
5>
6> allocate auxiliary channel clone_db_2 device type 'sbt'
7>
parms="ENV=(NB_ORA_CLIENT=PRD,NB_ORA_POLICY=ORA_PRD_full,NB_ORA_SERV=nbu_server,NB_ORA_SCHED=Daily-Full)";
8>
9> set newname for datafile 1 to
'/u01/oracle/dev/devdata/dbf/prod_system_01.dbf';
...
54> set newname for datafile 46 to
'/u01/oracle/dev/devdata/dbf/sysdba01.dbf';
55>
56> set until time "to_date('05/05/2007 12:00:00','mm/dd/
hh24:mi:ss')";
57>
58> DUPLICATE TARGET DATABASE TO DEV
59> LOGFILE
60>GROUP 1
61> (
...
74> ) SIZE 20M;
75>
76> }
allocated channel: clone_db_2
channel clone_db_2: sid=11 devtype=SBT_TAPE
channel clone_db_2: VERITAS NetBackup for Oracle - Release 5.1 (2006040520)
executing command: SET NEWNAME
...
executing command: SET until clause
Starting Duplicate Db at 08-MAY-07
printing stored script: Memory Script
{
set until scn 2000109207;
set newname for datafile 1 to
"/u01/oracle/dev/devdata/dbf/prod_system_01.dbf";
set newname for datafile 2 to
...
"/u01/oracle/dev/devdata/dbf/noetix_views_01.dbf";
set newname for datafile 46 to
"/u01/oracle/dev/devdata/dbf/sysdba01.dbf";
restore
check readonly
clone database
;
}
executing script: Memory Script
executing command: SET until clause
...
executing command: SET NEWNAME
Starting restore at 08-MAY-07
channel clone_db_2: starting datafile backupset restore
channel clone_db_2: specifying datafile(s) to restore from backup set
restoring datafile 1 to /u01/oracle/dev/devdata/dbf/prod_system_01.dbf
...
restoring datafile 00046 to /u01/oracle/dev/devdata/dbf/sysdba01.dbf
released channel: clone_db_2
RMAN-00571: ===
RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===
RMAN-00571: ===
RMAN-03002: failure of Duplicate Db command at 05/08/2007 14:52:13
RMAN-03015: error occurred in stored script Memory Script
ORA-19507: failed to retrieve sequential file,
handle="bk_PROD_u77igrh59_s1255_p1_t621659305", parms=""
ORA-27029: skgfrtrv: sbtrestore returned error
ORA-19511: Error received from media manager layer, error text:
Backup file not found in
NetBackup catalog
RMAN>
RMAN> **end-of-file**
This problem seems to be an evironment or permissions problem.
The auxiliary node can browse the backups from the target node via
the netbackup command 'bplist', so the netbackup backup catalog
is visible for backups from other nodes.
The file that is shown as not found in the backup catalog is indeed
there, and can be seen as per previous comments about bplist.
A straight restore of the DEV database was initiated to ensure that
the communications from Node B to the NetBackup server were
functioning properly.
Running the job from Node A ( owner of the backup files) gets
the same results.
I have successfully run done similar database duplicate jobs,
the difference being that the duplicate database was on the
same node.
Several notes on MetaLink, Veritas support site, and googling
have yielded a number of things to check, but no help.
So, if you have some insights into this issue, please feel free to share.
Thanks,
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
