Support Article

PEGADAT.PR_SYS_STATUSNODES table updated during restarts

SA-33198

Summary



The user reports that the PEGADAT.PR_SYS_STATUSNODES table is getting updated during JVM restarts. Their Pega primary environment is a two node (JVM) cluster (both nodes pointing to the same pegaapp db). They also have a DR site with two nodes (JVM cluster) (sharing the same DB but a different db then the primary nodes) pegadat data is kept in sync between primary and DR by a OGG (Oracle Golden Gate) replication.

When the user restarts the DR nodes, a row is inserted in the PR_SYS_STATUSNODES table from primary nodes, and the system name gets updated with the primary name when the node comes back up. The same thing happens when the primary nodes are restarted; they get the system name from the DR site.

What the user has been correcting this after the restart by updating the system name, removing the rows from the PR_SYS_STATUSNODES table, and restarting the nodes again. The user is trying to find an easier way to restart their environments.


Error Messages



Not Applicable.


Steps to Reproduce

  1. Create Pega primary environment as a two node (JVM) cluster (both nodes pointing to the same pegaapp db)
  2. Create a DR site with two nodes (JVM cluster) (sharing the same DB but a different db then the primary nodes)
  3. Keep pegadat data in sync between primary and DR by a OGG (Oracle Golden Gate) replication.
  4. Restart the DR nodes. you will find the PR_SYS_STATUSNODES table gets inserted with a row from primary nodes and the system name gets updated with the primary name when the node comes back up. The same thing happens when the primary nodes are restarted, they get the system name from the DR site.


Root Cause



On prodlinapsc1/c2 the value for 'systemName' in the dynamic settings is also PERS7_PROD_US_LS which is incorrect. It should be PERS7_PROD_US_CH

Resolution

  1. Leave the system name as is and do not make any further updates to it from the Designer Studio.
  2. Delete any Dynamic System Settings instances for system name from all the primary and DR nodes.
  3. Use the 'identification/systemName' environment entry in prconfig.xml of each of the nodes and set the value as appropriate for primary and DR nodes. Below is an example for a primary node
<env name="identification/systemName" value="PERS7_PROD_US_LS" />

Published February 2, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.