Robj /status_dm for Shared Memory Cannot Handle Values in Excess of 2GB (Doc ID 2968689.1)

Last updated on AUGUST 21, 2023

Applies to:

Symptoms

The following fields report values in bytes in the output of PCM_OP_READ_OBJ when reading "0.0.0.1 /status_dm 0", which in the case of dm_oracle, it allows values up to 192GB. 

0 PIN_FLD_DM_BIGSIZE_HWM INT [0] -1717986816
0 PIN_FLD_DM_BIGSIZE_MAX_USED INT [0] 5075408
0 PIN_FLD_DM_BIGSIZE_USED INT [0] 378688

Settings for this dm_oracle are as follows:
- dm dm_shmsize 34359738368
- dm dm_bigsize 8589934592

As can be seen in the BIGSIZE_HWM flist field above, the value is reported incorrectly because it does not fit in the 32-bit INT field.


EXPECTED BEHAVIOR
-----------------------
Need consistency in the output of /status_dm, i.e. all in 1024 byte block counts for all these fields. 

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. In testnap, read object 0.0.0.1 /status_dm 0

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.