Re: Migration/Refresh tool
From: DA Morgan <damorgan_at_psoug.org>
Date: Fri, 06 Jan 2006 12:29:52 -0800
Message-ID: <1136579389.162085_at_jetspin.drizzle.com>
>
>
> Daniel,
>
> do you really advocate merging production into a test/development
> instance?!?
>
> And Magnus, you said you wanted to
>
>
>
> Surely, you mean the other way around? Propagate changes in QTY to PRD?
> If not, I hope you have:
> - a sound quality assurance check procedure
> - good source control mechanisms
> - excellent change management procedures
> - RMAN documentation - look up Clone Database.
Date: Fri, 06 Jan 2006 12:29:52 -0800
Message-ID: <1136579389.162085_at_jetspin.drizzle.com>
Frank van Bortel wrote:
> DA Morgan wrote:
>
>> >>First thought is that you should collapse the four databases on the >>single server into four schemas in a single database: Problem solved. >>
>
>
> Daniel,
>
> do you really advocate merging production into a test/development
> instance?!?
>
> And Magnus, you said you wanted to
>
>>>What I want to do is refresh the data/structure changes from PRD to the >>>others on different intervals such as weekly, monthly, quarterly.
>
>
> Surely, you mean the other way around? Propagate changes in QTY to PRD?
> If not, I hope you have:
> - a sound quality assurance check procedure
> - good source control mechanisms
> - excellent change management procedures
> - RMAN documentation - look up Clone Database.
If the OP identified the other databases as test/developement I missed it and thus agree with you completely. I didn't read it that way.
My take was that PRD (production) was the source of information being parceled out to four other databases used for reporting, data mining, or other purposes.
If I'm wrong I'll not be surprised as it has been a hectic day.
-- Daniel A. Morgan http://www.psoug.org damorgan_at_x.washington.edu (replace x with u to respond)Received on Fri Jan 06 2006 - 21:29:52 CET