Metalink Note 73431.1 has an RMAN Compatibility Matrix. Target RMAN Catalog DB Catalog Schema 9.2.0 >=9.0.3 >=8.1.x >= RMAN executable
An RMAN920 schema can be created in an Oracle 8.1.6 database that contains the recovery catalog for Oracle 9.2.0 databases.
Have Fun :)
DENNIS WILLIAMS wrote:
Jared - Excellent point. My understanding is that the RMAN catalog must run on an Oracle version equal or greater than the target instances. Has anyone found this requirement to be a big pain? I am looking to configuring RMAN on another set of servers, but they are Oracle 9.2 and my current RMAN server is 8.1.6, and would need an O.S. upgrade to move to 9.2.
Dennis Williams
DBA, 80%OCP, 100% DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-----Original Message----- Sent: Thursday, May 29, 2003 8:20 PM To: Multiple recipients of list ORACLE-L
Dennis,
The cron job can run on B only if it is the same version of Oracle that is on A.
Jared
DENNIS WILLIAMS <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 05/29/2003 03:14 PM Please respond to ORACLE-L
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
cc: Subject: RE: RMAN - Remote vs Local Backups
Walter - What you describe is the standard RMAN configuration. Box B
contains the RMAN catalog, therefore it must command the backup. And so the
cron job must run on Box B. But the actual backup occurs on the target
machine (A in your example). If you back up to tape, you must have an MML
(Media Management Library). You can also back up to disk (that is what I
do).
Since the actual backup occurs on the target machine, not much network
traffic is involved. RMAN sends some commands, the target sends some status
back, and that is about it.
Dennis Williams DBA, 80%OCP, 100% DBA Lifetouch, Inc. [EMAIL PROTECTED]
-----Original Message----- Sent: Thursday, May 29, 2003 4:30 PM To: Multiple recipients of list ORACLE-L
Thanks Tim, Dennis and Ron for your feedback. I appreciate it.
Let me clarify what I'm seeking. In my example, I am using a centralized catalog which is on its own dedicated database/server and backups are to tape. BCV's are not involved.
Normally, in my experience, RMAN backups are initiated from the target
server via a cron job. But, I've seen a case where a cron job for an RMAN
backup was run from a box that was different from the database server
machine. I find this configuration strange and confusing because it implies
this was done for a "reason" and makes life difficult to find out where all
the backups are running from.
In the scenario of backing up the database on box A via an rman/cron job on
box B, is this particular configuration more network resource intensive and
therefore slower versus the backup being initiated from the same machine as
t
-- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Chip INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
