Question
Vodafone
IN
Last activity: 25 Nov 2019 4:08 EST
VBD is causing OOM memory error
Our client uses Pega 7.3.1 and PM 7.31.
When we restart vbd servers, we could observed oom memory. we tried increasing memory till 12 GB.
I could see there is a hotfiy for 7.2.1 version.
is the same fix available for Pega 7.3.1 as well?
***Moderator Edit-Vidyaranjan: Updated Platform Capability***
Pegasystems Inc.
IN
What is the hotfix no? So that I can check, is there any corresponding hotfix for PEGA 7.3.1.
Tata Consultancy services
HU
Pegasystems Inc.
IN
The hotfix was fixed in 7.3, it might be a different root cause for the issue you are facing.
Pegasystems Inc.
IN
By the way these are the changes as part of HFix-31877:
We will reduce the amount of memory required by implementing the following: - Only loading the columns from the IH Fact table that correspond to dimensions or measurements, as they are defined in Data-Decision-IH-Config. Custom columns added for non-VBD purposes will therefore not get loaded by VBD. - We will reduce the possibility of Dimensions using more memory than is reasonable, by limiting their size to 10K entries per dimension.
Pegasystems Inc.
IN
You need to observe the PegaRULES and PegaRULES-ALERT logs which are generated on the VBD node at the point of the issue and see if you can get any clue.
You can also take the thread dump and you can analyze the thread dump using several tools which are available online or offline to find out the root cause of the issue.