Please note the above RU updates that will address the issue. 17.2 RU2 and higher, as well as 17.3 RU9 and higher.
If you are experiencing this behavior please open a case in support informing you about this article, and attaching to the case the following information to assist in our investigation:
Enable the following trace/processes in your environment:
pdm_trace bpvirtdb_srvr on
pdm_trace bpvirtdb_srvr size 100000
pdm_trace bpvirtdb_srvr watch sqltrans.c 2156
pdm_trace bpvirtdb_srvr attach domsrvr
pdm_trace domsrvr size 100000
Traces should be written automatically due to the watch setting.
Monitor the environment for at least one day. As soon as the slow-process starts please write down the time so that we can be more assertive in our analysis of traces.
To turn off trace, including attached processes, run:
pdm_trace bpvirtdb_srvr off
Collect pdm_trace for domsrvr and bpvirtdb_srvr and stdlog files and attach to the case open in the stand.