Question

7
Replies
301
Views
Paul Neal (PaulN038)
DirecTV

DirecTV
US
PaulN038 Member since 2015 1 post
DirecTV
Posted: February 25, 2016
Last activity: March 4, 2016
Posted: 25 Feb 2016 15:03 EST
Last activity: 4 Mar 2016 14:40 EST
Closed

using golden gate to keep a failover database in sync

The customer maintains a complete replicate environment for failover of their PRPC application, and their first test of fail-over did not succeed.

This is PRPC 7.1.8 with DSM and ADM in use, in a clustered Linux (intel) based environment.

The Database is Oracle, and they use Golden Gate replication to keep the standby database up-to-date.

They use a split Schema.

so, there is a Pega Rules schema, a Pega Data schema, and an ADM schema.

IH tables are maintained in the Data Schema.

They initially set up all tables in all schema's to be replicated to the standby database

I advised them that you cannot simply replicate all the PRPC data in the Pega Rules Schema, as it contains environment specific data, (amongst other things).

does Pega supply a best-practices guide on which tables should not participate in a standby failover db?

Data Integration Decision Management
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.