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: Production & Development Environment

Re: Production & Development Environment

From: Tsurng-Chen Chern <maxchern_at_kazakhstan.it.earthlink.net>
Date: 1997/08/16
Message-ID: <Pine.SOL.3.96.970816085309.11302A-100000@kazakhstan.it.earthlink.net>#1/1

One question, what is the size of your data? I mean both the database file size, and the actual data size.

You see, if your data size is close to the data base file size, backup will be faster than export. However, your database will get fragmented in no time.

If you reserve a lot of space in the database, so that the file size is way larger than the actual data size, will then, export will be faster than backup.

I don't think anybody with 20 G database would like to ftp the database over to anywhere.

On 15 Aug 1997, BRAJB wrote:

> In our situation, we support the following environments
>
> 1: Production
> 2: Production Fix (Used for tech support mirrored once a week)
> 3. New Development (Controlled Mirror - point in time)
> 4. System Test (Controlled Mirror - point in time)
>
> The method of refreshing is as follows:
> 1. Production (Backup controlfile to trace)
> 2. Shutdown the Production DB
> 3. Shutdown the Target DB
> 4. Ftp (binary) files to target server
> 5. Copy the backed up control file to the target db and edit
> to rename appropriate filestructures (if different) and rename
> the db sid. (I really only did this once, but have to keep it up
> to date if the production database required added datafiles)
> 6. Create a script to remove the old datafiles and control files, copy
> the datafiles then recreate the control files with pointers to new
> locations.
>
> This process takes me about 1 hour to complete for one database. I had
> previously done it with export import which took about 4 hours. Where the
> production database would outgrow the testing environments I would
> frequently run into tablespace problems. with this method, it is much
> cleaner. The downfall is the downtime required for this process.
>
>
>
>
>

Max Chern, Unix Software Engineer     |  Voice: 818-296-5014
EarthLink Network, Inc.               |  Fax:   818-296-5113
maxchern_at_earthlink.net                |  3100 New York Dr., Ste 201
http://www.earthlink.net/             |  Pasadena, CA 91107
Received on Sat Aug 16 1997 - 00:00:00 CDT

Original text of this message

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