Re: what is the main purpose of cloning a database.

From: Howard Latham <howard.latham_at_gmail.com>
Date: Thu, 18 Dec 2008 18:46:56 +0000
Message-ID: <713d96d10812181046x25be4b57na5e9f4fab9bfb8af@mail.gmail.com>


Clone databases
to

1. create a test
2. create another live database for new customer
3. test backups
4. create dev environmemt
5. move to another box
6. move to another Os
7. create a standby

There I've started the definitive list. !

2008/12/18 Wolfgang Breitling <breitliw_at_centrexcc.com>:
> At a prior employer I did daily exports of the metadata of all Peoplesoft
> databases ( Financials, HR, Student Admin ) which I could use to create a
> database without transaction data. Modeled after the old AUD databases. A
> few times that came in handy to recover code the developer failed to save to
> file-based projects when a development database was refreshed. No need to
> have a full clone for just the metadata.
>
> At 04:44 PM 12/17/2008, Nuno Souto wrote:
>>
>> Sure is. What I'd like to see is Peoplesoft HR for example
>> install all its metadata in another schema than PSMAN.
>> Then it's a simple matter of cloning the schema for simple
>> code checks and testing. Much better than 25000 tables...
>> Unfortunately, I still have to see one single Peoplesoft
>> installation - all the way to Peopletools 8.4.10 - where
>> that is the case.
>>
>> Most unfortunate. But it makes for a great test of the
>> backup/cloning mechanism! Can't complain. ;)
>
> Regards
>
> Wolfgang Breitling
> Centrex Consulting Corporation
> www.centrexcc.com
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

-- 
Howard A. Latham
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Dec 18 2008 - 12:46:56 CST

Original text of this message