!! Please do not post Off Topic to this List !!
Ruth,
Iam facing the follwing problems/doubts how to upgrade the catalog now.
Please try to help me if you can:
I have Production DB in 8.1.6.2.0(64bit) on one box, and RMAN catalog
database
(8.1.6.2.0) on another box. I need to upgrade both the DBs to 8.1.7.1.0. I
have
no problem upgrading the production DB to 8.1.7.0.0 and then to 8.1.7.1.0
patch
level.
The box on which catalog DB exists has another production DB which was
upgraded
to 8.1.7.1.0. and so I CAN NOT upgrade catalog DB to 8.1.7.1.0 using normal
upgrade procedure. I must upgrade to base line release first(8.1.7.0.0) and
then patch needs to be applied. Since patch was already applied, my only
option
could be to recreate the catalog database in 8.1.7.1.0 and then DO THE FULL
IMPORT. My questions would be:
[1] Do I need to do the FULL IMPORT of the catalog database? and then issue
the
"upgrade catalog" command twice to upgrade the catalog to work with the
latest
RMAN version? [OR]
[2] Do I just recreate the empty catalog DB in 8.1.7.1.0 and then follow the
regular procedure to create RMAN schema and register the DB and then take
the
fresh cold backup to start with, followed by the regular daily incremental
backups?
[3]If I follow [2], I may loose the catalog info for 8.1.6.2.0. backups. Is
the
8.1.6.2.0 catalog data useful after upgrading the DB to 8.1.7.1.0?
Please answer my above questions and suggest an appropriate procedure to
upgrade the catalog DB to 8.1.7.1.0
-----Original Message-----
Sent: Friday, September 14, 2001 11:05 AM
To: Multiple recipients of list ORACLE-L
!! Please do not post Off Topic to this List !!
I think this is what you want to know: you should upgrade your rman
database to the highest version of the databases being backed up with rman.
Ruth
----- Original Message -----
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Friday, September 14, 2001 12:45 PM
> !! Please do not post Off Topic to this List !!
>
> Dear List Members,
>
> I have Production DB in 8.1.6.2.0(64bit) on one box, and RMAN catalog
> database
> (8.1.6.2.0) on another box. I need to upgrade both the DBs to 8.1.7.1.0.
I
> have
> no problem upgrading the production DB to 8.1.7.0.0 and then to
8.1.7.1.0
> patch
> level.
>
> The box on which catalog DB exists has another production DB which was
> upgraded
> to 8.1.7.1.0. and so I CAN NOT upgrade catalog DB to 8.1.7.1.0 using
> normal
> upgrade procedure. I must upgrade to base line release first(8.1.7.0.0)
> and
> then patch needs to be applied. Since patch was already applied, my only
> option
> could be to recreate the catalog database in 8.1.7.1.0 and then DO THE
> FULL
> IMPORT. My questions would be:
>
> [1] Do I need to do the FULL IMPORT of the catalog database? and then
> issue the
> "upgrade catalog" command twice to upgrade the catalog to work with the
> latest
> RMAN version? [OR]
>
> [2] Do I just recreate the empty catalog DB in 8.1.7.1.0 and then follow
> the
> regular procedure to create RMAN schema and register the DB and then
take
> the
> fresh cold backup to start with, followed by the regular daily
incremental
>
> backups?
>
> [3]If I follow [2], I may loose the catalog info for 8.1.6.2.0. backups.
> Is the
> 8.1.6.2.0 catalog data useful after upgrading the DB to 8.1.7.1.0?
>
> Could some one please answer my above questions and suggest an
appropriate
> procedure to
> upgrade the catalog DB to 8.1.7.1.0.
>
> Thanks,
> -- Janardhana Babu
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.com
> --
> Author: Janardhana Babu
> INET: [EMAIL PROTECTED]
>
> Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
> San Diego, California -- Public Internet access / Mailing Lists
> --------------------------------------------------------------------
> 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).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Ruth Gramolini
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
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).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Janardhana Babu
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
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).
