E-IB: Dynamic Slave Configuration Does Not Recover After Application Server Restart
Last updated on MARCH 30, 2017
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.53 and later
Information in this document applies to any platform.
Application messaging server is marked as a Dynamic Slave domain on the IB Failover page, This means that by default this domain is given a failover priority of 2 within any Failover group. If the primary domain goes down, the Dynamic Slave domains becomes the primary domain until the initial primary domain with a failover group/priority of 1/1 is rebooted. The current domain that was marked as the Dynamic Slave will not recover to that original state without manual intervention on the IB Failover page.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms