"Seems like we reached our max memory_limit"...how do you know?
Are we talking Q Capture memory_limit or Q Apply memory_limit?
For Q capture:
"The memory_limit parameter specifies the amount of memory that a Q
Capture program can use to build transactions in memory."
"You might need to increase the memory limit if the Q Capture
program is spilling transactions to disk or virtual I/O."
" If the TRANS_SPILLED column in the IBMQREP_CAPMON table has a
value greater than 0 (you can also view this value in the Q Capture
Throughput window in the Replication Center), try increasing the
For Q Apply:
"The memory_limit parameter determines the amount of memory that a
Q Apply program can use as a buffer to process transactions from
one receive queue. "
"When the memory limit is reached, the browser thread stops getting
messages from the receive queue and waits for agent threads to
apply more transactions to the target table to free memory. If a
single transaction is large enough to exceed the memory limit, the
browser thread applies partial rows of the transaction before
processing more rows of the same transaction. Both of these actions
"The MONSTER_TRAN column measures the number of transactions that
exceeded the memory limit."
> On 28 December 2018 at 21:24 Rui Chen
<[login to unmask email]> wrote:
> Seems like we reached our max memory_limit, but
interestingly trans_spilled always stays at 0. Does that mean no
new tx captured while QCap saturated its memory? How does QCapture
program behave while it exhausted available memory? Naively i would
expect none-zero trans_spilled, but what do i know..... There's no
info logged in QCap program log, nor any monster_transaction
reported on IBMQREP_APPLYMON (not a surprise though) ...
> We are also considering doubling our memory_limit
(currently at 2GB, far away from the 100GB upper limit....), and we
do have more than enough free memory to allocate (O(100)GB free
memory). Curious if someone had unpleasant experience with
high memory_limit.... thanks
> Oh, and Happy New Year everyone!
> -----End Original Message-----