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

From: SHEEHAN, JEREMY <JEREMY.SHEEHAN_at_fpl.com>
Date: Thu, 18 Dec 2008 07:53:59 -0500
Message-ID: <8833494F383585499CB855121711D263091504D138@JBXEXVS02.fplu.fpl.com>


I had monthly Oracle Apps clones that were done on 3 environments at my last job. As long as you have a good plan for a clone, then you should be fine.

Jeremy
 Consider the environment. Please don't print this e-mail unless you really need to.

-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Wolfgang Breitling Sent: Wednesday, December 17, 2008 8:26 PM To: dbvision_at_iinet.net.au; 'ORACLE-L'
Subject: Re: what is the main purpose of cloning a database.

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

i0zX+n{+i^ Received on Thu Dec 18 2008 - 06:53:59 CST

Original text of this message