Re: Got Questions: Golden Gate replication between cloned environments

Hi

We snapshot OLTP and the DWH (source and target. What we do is(all steps are scripted)

1. stop goldengate in source (2 nodes OLTP RAC)
2. stop goldengate in target (Single Instance DWH
3. snapshot OLTP database disks
4. snapshot source GoldenGate disks
5. snapshot DWH database disks
6. snapshot target GoldenGate disks
7. startup goldengate in source
8. startup goldengate in target
9. startup source cloned database and goldengate in the QA environment (there are some post snap scripts which change IP, database parameters)
10. startup target cloned database and goldengate in the QA environment (there are some post snap scripts which change IP, database parameters)

This have been working since 2013 and we have setup a few more this year and works OK.

BR

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free.
www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Dec 1, 2017 at 4:02 PM, Chris Taylor < christopherdtaylor1994_at_gmail.com> wrote:

> Additional details.
>
> 1. To clone the environments we snapshot the storage protection group and
> provide the snapshot as the cloned db (Pure Storage Array - take snapshot
> of Prod Disk Group, and mount that snapshot on Dev/Staging/QA servers as a
> dev/staging or QA database)
> The cloned copies (OLTP and DW) are in sync initially but eventually the
> OLTP and DW Dev/Staging/QA environments get out of sync:
>
> OLTP Prod -- GGate --> DW Prod
> (Clone Copies Below)
> OLTP Dev --> DW Dev (no GGate)
> OLTP Staging --> DW Staging (no GGate)
> OLTP QA --> DW QA (no GGate)
>
>
> 2. Env:
> DB = 12.1.0.2 64-bit
> OS = RHEL 7
> GGate Version = 12.1.2.1.170117
>
>
>
> On Fri, Dec 1, 2017 at 8:46 AM, Dave Herring <gdherri_at_gmail.com> wrote:
>
>> Through in a few version and env details while you're at it. I wouldn't
>> think your scenario would be impacted to much with the release but we've
>> had different issues where the release was critical in getting the
>> requirement to work.
>>
>> On Fri, Dec 1, 2017 at 8:42 AM, Ls Cheng <exriscer_at_gmail.com> wrote:
>>
>>> Hi Chris
>>>
>>> I have setup in a few environments where QA environment is refreshed
>>> using Storage Snapshots, works good. How are you refreshing the
>>> environments?
>>>
>>> Thank you
>>>
>>>
>>> On Fri, Dec 1, 2017 at 3:38 PM, Chris Taylor <
>>> christopherdtaylor1994_at_gmail.com> wrote:
>>>
>>>> We have Golden Gate replication in production and there is some
>>>> discussion about using Golden Gate replication in the cloned production
>>>> copies (Dev, Staging, QA).
>>>>
>>>> We refresh Dev/Staging/QA monthly.
>>>>
>>>> I don't know Golden Gate very well (beginner/intermediate) but I'm
>>>> thinking this won't work in the cloned environments as the clones would
>>>> lose the Golden Gate Extract process each time the clone happened and the
>>>> SCNs would get out of sync anyway.
>>>>
>>>> Questions
>>>> 1. Am I wrong in thinking this?
>>>> 2. Is there a way to keep Golden Gate running in cloned environments
>>>> without a lot of manual intervention?
>>>>
>>>> I'd like to hear any of the technical issues related to such a setup.
>>>>
>>>> Thanks,
>>>> Chris
>>>>
>>>>
>>>
>>
>>
>> --
>> Dave
>>
>
>

--
http://www.freelists.org/webpage/oracle-l