Notice 2017-01-01 01:01:01.123456 12345 123456789 Command server: Configured shared memory size of 268435456 is > 1048575, assuming unit of bytes (connecting from SERVER_NAME) [module que]
Notice 2017-01-01 01:01:01.123456 12345 123456789 Cop: Configured shared memory size of 268435456 is > 1048575, assuming unit of bytes [module que]
Notice 2017-01-01 01:01:01.123456 12345 123456789 Capture: Configured shared memory size of 268435456 is > 1048575, assuming unit of bytes (capturing from ORASID) [module que]Notice 2017-01-01 01:01:01.123456 12345 123456789 Reader: Configured shared memory size of 268435456 is > 1048575, assuming unit of bytes (from ORASID) [module que]
Notice 2017-01-01 01:01:01.123456 12345 123456789 Export: Configured shared memory size of 268435456 is > 1048575, assuming unit of bytes (exporting to SERVER queue SERVER) [module que]
If 268435456 bytes was previously specified in the paramdb, SharePlex will consider this value as 268435456 Mbytes. As this value is considered too high, SharePlex writes a notification message in the event log.
In 8.6.4, parameters SP_QUE_POST_SHMSIZE and SP_QUE_Q_SHMSIZE changed from bytes to Mbytes.
It is intended for customers to alter the parameters to a megabyte value. SharePlex converts internally, however, it will not change parameter values in the paramdb.
There is an aspect of estimation involved in the internal conversion ( i.e. is the smallest value intended to be in bytes or megabytes?), the queue code logs notice messages indicating that SharePlex is assuming the value to be in bytes.
WORKAROUND:
SharePlex Queues parameters:
Parameter Name Actual Value Units Set At
------------------------------ ------------------------------------ ------- ---------------
