In the RMAN script:

ORACLE_SID=`echo $NB_ORA_POLICY |sed 's/.*_//'`

where the policy name is RMAN_prod_(database_name)  This way I have one 
RMAN script for each *version* of Oracle, even when I have 6 databases 
running the same version I'm not maintaining 6 RMAN scripts.  By verison, 
I mean 10g or 9i, not 10.2.0.2.

Although, Wayne T Smith's comment about multiple App schedules has me 
thinking, perhaps I don't work closely enough with my DBAs.  I may have 
some room for improvement.  I currently have Full backups and Archive logs 
on the same retention, which isn't really a bad thing, but it would be 
nice to split off a Level 1.


----Original message----
Date: Sat, 25 Nov 2006 18:13:49 -0500
From: "Martin, Jonathan \(Contractor\)" <JMARTI05 at intersil.com>
Subject: Re: [Veritas-bu] Oracle RMAN backups

I'm not an RMAN / Oracle guru here and I work pretty closely with my DBAs 
to
make our backups work but my testing with 5.1 MP4 shows that the schedule
retention overrides the default-application-backup.  Further, how exactly 
do
you run both a full and incremental in the same policy?  If your policy
calls full_backup.cmd (.sh) and that calls RMAN - how does RMAN or the
script know which schedule Netbackup is running?  Is this a scripting
function you are using?  I use two policies to call full versus 
incremental
backups because I run two backup scripts, full_backup and incr_backup
.cmd/sh.  I guess you could customize your RMAN script to run a different
command based on some sort of system input / variable?!  Anyhow, we're
upgrading to 6.0 here in the next month or two and I'm going to have to
tackle this problem then.

-Jonathan


-- 
Joe Royer / SysAdmin / Digital Motorworks / 512-692-1028


This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.