copy database 3

[maswien]

I want duplicate a database on a different server. I am pretty clear about the process. But the issue is that the source database is 9.2.0.5 and the target machine only have 9.2.0.7 installed.

Do I need to upgrade the source database to 9.2.0.7 before I copy over the database?

Thanks!

 

[SantaMufasa]

What is your plan/methodology for copying the database? Do you plan to copy database data files, perform exp-imp/data pump, or some other method?

Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]

 

[maswien]

Hi SantaMufasa ,

Not the export and import because the database is about 50G and there is no extra staging space. I want copy the data file over to another server and recreate the control files and redo logs. This is documented in the metalink.

But I am not sure about the release number, don't know if it will be a issue.

 

[SantaMufasa]

Maswien,

You should be okay provided that once you copy over the files to the 9.2.0.7 instance, and you do a "startup" on the database, that you run the data-dictionary upgrade script, "$ORACLE_HOME/rdbms/admin/catupgrd.sql" (as KarlUK recently noted).

Let us know your findings.

Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]

 

[maswien]

Thanks Mufasa, this is desirable answer for me!

 

[karluk]

That previous thread was talking about patching 10.2.0.1.0 to either 10.2.0.2.0 or 10.2.0.3.0. For that particular upgrade the appropriate catalog script is catupgrd.sql. That's almost certainly not the right script to run when going from 9.2.0.5.0 to 9.2.0.7.0. The readme notes for the 9.2.0.7.0 on HP-UX indicate that the right script is catpatch.sql. Probably it's the same on your platform.

Maswien, I think SantaMufasa is right that you can move the database files to the new server and then upgrade to 9.2.0.7.0, but you really need to download the appropriate installation documentation for guidance. Get the readme doc for the 9.2.0.7.0 patch set from Metalink and follow it to the letter. There are a few things you need to check before running catpatch.sql. That includes checking that there is enough free space in the system tablespace and that shared_pool_size and java_pool_size are both set to at least 150mb.

 

[karluk]

Another thing to check is that the same Oracle software is installed on both the 9.2.0.5.0 and 9.2.0.7.0 servers. If you have some Oracle components on the 9.2.0.5.0 server that aren't installed on the 9.2.0.7.0 server, you most likely will have to install them before moving the database. You can check what software is installed on each server by running the Oracle Universal Installer on both. The very first screen has an option to show what's installed.

 

[SantaMufasa]

Thanks, KarlUK, for again providing excellent guidance. I'll update my notes accordingly.

Please hava

.

Mufasa
(aka Dave of Sandy, Utah, USA)
[I provide low-cost, remote Database Administration services: www.dasages.com]

 

[maswien]

Thanks Karl!

 

[maswien]

Karl,

You are right that the installation on the target server is a standard edition 9.2.0.7 but the source database is 9.2.0.5 enterprise edition.

In this case, do I any other option to get the job done without exp/imp the database?

Thanks