applying patchset before/after database move

I'm soon going to be moving a couple of db's from separate servers and consolidating them on one new server. One is currently on 8.1.7.4 and it will be no problem as I will just export/import it into the new 9.2 database. The other one though, is currently running on 9.2.0.5 and I am contemplating bringing it up to 9.2.0.7 when I move it, and am trying to decide the best way to do this.

Normally in a situation like this I do the following:

1.take the latest online (OS) backup and copy it to the new machine,

2.start it up and recreate the controlfile, issue a "recover until cancel using backupcontrolfile",

3.shut the "old" database down after archiving all the logs, then apply the logs to the new database and open it with resetlogs.

This makes for a very fast move with little downtime as all I have to do is then change the alias in my names server to point at the new machine and its good to go.

What I am wondering is, if I patch the oracle software to 9.2.0.7 before I start up the new database and apply logs to it, then run the catpatch.sql script against it (after all the logs are applied and I open it with resetlogs) will this be ok? Or should I just patch it to the same level (9.2.0.5), restore the online backup to it as described above and get it up and running, then just allow for more downtime to apply the 9.2.0.7 patch from scratch.

OTOH, since this particular database will likely be my first 10G upgrade   (hopefully in the near future) I may just decide to leave it at 9.2.0.5. until then.. Received on Wed Jan 04 2006 - 17:50:30 CST