9i to 10g migration - chicken vs the egg

[TwoProc]

I've got a "chicken vs the egg" scenario.

I've got a 9i database and a 9i RMAN catalog database. From what I've read in the past (from Oracle) they must match in version.

During the upgrade weekend to 10g, I really won't have the time to upgrade the catalog the same weekend (not easily anyway), so my preference would be to upgrade the catalog on a different weekend, if possible.

So, can I upgrade the catalog database to 10g first, and then keep running databasee 9i for another week and still be able to do backups?

That is, can a 10g database holding an RMAN catalog provide RMAN catalog backup and restore ability for a 9i database?

If you had additional experiences that would help along these lines, I would greatly appreciate knowing your opinions and experiences in this area.

Thank you!

[Yogeeraj_1 · Accepted solution]

hi john,

According to the RMAN compatibility Matrix (see Note 73431.1 - RMAN Compatibility Matrix), you can create a RMAN 10g catalog on a >=9.0.1 database.

Thus,
1. migrate your database
2. Create a new catalog for the migrated database.

Unfortunately, you will have to slightly modify your scripts if every you have hardcoded your username/passwords for connecting to the catalog.

Anyway, you will have to review the best practices for RMAN 10g and benefit from advantages sooner or later.
(unfortunately, i dont have the note number handy - please search metalink)

I will be happy to share my own experiences on our migration to 10g.

All the best!

kind regards
yogeeraj

[Steven E. Protter]

Shalom,

You can always do cold OS backups of the database if you have the time.

This will permit you to do the migration of the RMAN database in a normal, unhurried fashion.

SEP

[TwoProc]

Hi Yogeeraj,

Thanks for answering my question.

Can I do the opposite of what you suggested?
Can I host a 9i catalog on a 10g database?

I'd prefer to get the smaller of the two migrations done first (catalog before the huge db).

Thanks!

[TwoProc]

Steven, we can go back to that - in fact I do them in "tandem" - the only difference being that RMAN takes care of archive logs for me, and I've got a command to pull back indiv arch logs from the catalog when I need them. This leaves with two methods to get back a database. However, leaving off RMAN for a while gives me a massive amount of archive logs to deal with by hand, and I'll have to commit daily resources to fooling with it - that is backing them up, and figuring out which ones were in a complete state, and which ones made it to tape, etc. I used to have scripts for all of that, but it's been years and years.

[Yogeeraj_1]

hi again,

You are perfectly right! it is much better to do the RMAN migration first.

There should not be any compatibility issues. Anyway, you can try it beforehand. Unfortunately, i only have oracle 10g databases and cannot test this for you.

If you need any further assistance, please let us know.

all the best

kind regards
yogeeraj