Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: moving a "development"database to a "production" server.

Re: moving a "development"database to a "production" server.

From: Van Messner <vmessner_at_bestweb.net>
Date: 2000/08/11
Message-ID: <bx%k5.244$kM2.38863@newshog.newsread.com>#1/1

You'll have to judge whether you feel you have enough experience, but you might take a look at advanced replication. It specifically allows you replicate a database.

Van

"fro_doe" <fro_doeNOfrSPAM_at_hotmail.com.invalid> wrote in message news:0de771cc.4ce66d11_at_usw-ex0103-018.remarq.com...
> Given that the OSes and the Oracle software are the same, you can
> shutdown the database, then rcp or backup/restore the datafiles,
> logfiles, controlfiles, and init.ora to the new server. You
> should be able to open the database without any additional
> changes.
>
> There may be some Net8 files (tnsnames.ora, listener.ora) that
> need to be modified for the new host.
>
> I wouldn't recommend copying the entire filesystem. OUI with 8i
> uses an inventory to store/determine the installed products on
> the system. It is a binary file that is, for all intents and
> purposes, uneditable. So, if this inventory file becomes
> mismatched with the software you have on the system (because,
> say, the stuff in ORACLE_HOME was copied from one
> system/filesystem to another), the only way to get things in
> order again is to reinstall the software. This is not something
> you want to do in a production environment. Why is it a problem
> having software that is not reflected in the inventory? For one,
> upgrades (including patchsets) use the inventory to determine the
> installed version. So, you can not upgrade to the latest
> patchset if the inventory knows nothing about your ORACLE_HOME.
> Resolution - reinstall the software. The one thing I'm not sure
> of is whether or not the inventory associates a hostname with
> installed software as well. If not, given you have identical
> directory structures, copying the entire tree, including
> inventory, may work, but I wouldn't take the chance.
>
> Another suggestion is to make sure the software on the new
> production server can run a default database before moving the
> development database over. There may be some config issue (e.g.
> kernel parameters) that will prevent any database from running.
> It's nice to find those things before it's go time.
>
> Good luck, Doug.
>
>
> -----------------------------------------------------------
>
> Got questions? Get answers over the phone at Keen.com.
> Up to 100 minutes free!
> http://www.keen.com
>
Received on Fri Aug 11 2000 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US