I use one catalog for all my databases. You have to have a catalog in a
separate database if you are going to backup the catalog database using rman
but that is the only time I have ever heard of using more than one catalog.
I must say, most of the Oracle support analysts, at least, don't underst
I have two repositories in test and will have 2 in production. One to
backup the databases (an instance unto itself) and one to backup the RMAN
instance (schema within one of the lesser instances). In a perfect world
where you have acres of dasd and unlimited everything, I guess it might be
clea
I am fairly new to RMAN, but here is my $.02. Use a separate RMAN db for each version
of db's to be backed up (e.g. rman817, rman901, ...). In each RMAN db, I would create
a separate schema, same name as Oracle_SID for each db. This model makes scripting,
maintenance, and upgrades simple. N
Pat,
This makes no sense to me. I have one Rman catalog for all our databases
that are at the same release level.
I can see separate Rman catalogs for different release levels, but even this
is not necessary. Lower levels of Rman work with higher levels of the Rman
repository.
Hope this helps
Pat
There are several reasons to have multiple catalog, but the most
importen one is that gives the possibility to upgrade the catalog
without interfering
with other database backup's. There is as well the benefit if you at
some time is going to query the catalog using Sql you will not have t
Hi Pat,
to cut to the chase here is how we do it in our shop
..
we have :
1. East Coast: we have bunch of DB's & 1 tape server
2. West Coast: we have bunch of DB's & 1 tape server
Rman Strategy:
We have two catalogs, one which caters to all db's on
east coast and backs ups db's on east coast ta
