Question
Cognizant Technologies Solutions US
CA
Last activity: 6 Feb 2020 9:35 EST
pr_sys_statusnodes table empty
Hello Team,
am seeing pr_sys_statusnodes table is empty even after JVM recycle, db user id which we using has access to this table. Will anyone please let me know what are the consequences that occur and how can we update this table with entries.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
US
what is your database platform and pega platform version?
Cognizant Technologies Solutions US
CA
Hello Kevin,
We are on Oracle12c with Pega v8.1.1
Thanks
Proximus
BE
Hello,
Can you please check whether this table is not existing in both DATA & RULES schema.
Then it could be that your synonym table is pointing to the table not used by the system leading to an empty table.
Regards
Anthony
Cognizant Technologies Solutions US
CA
Thanks Anthony, Kevin for reply. we recycled JVM's by truncating db cache.. now am seeing entries. But still not sure why earlier table was empty.
Pegasystems Inc.
US
Hi,
This table holds the node(s) information and each record represents a node(JVM) in order to form a cluster.
Please note that in 8.x versions, upon clean shutdown of any node will remove its own record from this table and restarting the node will insert the record in the table again.
Let me know if this clarifies!
Proximus
BE
Dear Harish,
Could you please clarify what is meant behind a "clean shutdown" and the difference with a normal shutdown?
is this linked to prconfig/initialization/rebuildlocalcachesonnodestart/default which is either true or false?
Then, if the entry is removed from the table during clean shutdown, does it mean that the nodeID changes? if not, where is it stored? Thank you
Regards
Anthony
Pegasystems Inc.
US
Hi,
1). An app server shutdown command going through a proper shutdown hook to end the JVM process without needing to force kill the Java process is a clean shutdown (normal), unlike the force shutdown.
Eg:- Running shutdown.bat/sh for Tomcat.
2). rebuildlocalcachesonnodestart setting is not linked to this process. It influences whether to rebuild local caches on each JVM start.
3). Node entry gets removed upon clean shutdown and it doesn't mean that nodeID will get changed. NodeID is stored as an instance of "Data-Admin-Nodes" under pr_data_admin table.
Let me know if this answers your queries.