Re: Quick Question - Golden Gate PL/SQL objects (Source->Target)

It can replicate PL/SQL objects. At a previous company this was commonplace for deployments. It's not an issue in and of itself, however you do want to keep good track of objects which aren't replicated. For example; In that environment, there were two data centers. One was using even sequences, the other using odd. This was done to allow us to run in multiple DC's with little/no changes to the app (which is a mistake, but outside this discussion).

This situation made it so that we were replicating all objects except for sequences. When a deployment would run, and required the use of a sequence, the updates still required manual intervention in the standby DC. Eventually this was overcome by programmatically generating sequences.

If at all possible I would recommend avoiding that situation. The vast majority of our Goldengate issues stemmed from PL/SQL object and other DDL replication. In a green field scenario I'd push for data only replication and do what I could to persuade the company into an app/deployment rearchitecture that would allow for a data-only replication configuration.

> On Oct 3, 2017, at 10:15 AM, Chris Taylor <christopherdtaylor1994_at_gmail.com> wrote:
>
> Just a quick question - can Golden Gate replicate PL/SQL objects from SOURCE to TARGET?
>
> Genesis of the question: Code releases/migration of common objects between Source & Target - do the release scripts have to be run in both envs?
>
> Looking for thoughts/suggestions/comments/quips.
>
> Chris

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