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: migration of database

Re: migration of database

From: Daniel A. Morgan <dmorgan_at_exesolutions.com>
Date: Thu, 11 Jan 2001 22:48:29 -0800
Message-ID: <3A5EA8BD.6D1F1CEF@exesolutions.com>

> When migrating a database from the development to
> the production area do dba's generally copy the entire
> database or run scripts to create the tablespaces/tables ect?

Reasonable people may disagree. But the rule at Fortune 500s where I have worked is that you NEVER ... EVER ... build a production database from anything other than a single driving script that may contain the entire build or that calls other subscripts that together compose the entire build.

The advantages are many:

  1. Configuration management is assured as the build scripts can be archived.
  2. The structure build can be tested in multiple independent environments.
  3. No introduction of logical or physical database errors that could be recreated in a build based upon an export-import or physical copying.
  4. The ability to on-the-fly resize and rename any database object.
  5. The ability to create a spool file containing a full copy of the build and any error messages generated.

The script may be hand written, reverse engineered, or created using a CASE tool such as Designer or ERwin.

Daniel A. Morgan Received on Fri Jan 12 2001 - 00:48:29 CST

Original text of this message

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