Amit and Stuart,
This support article doesn't mention that this issue doesn't happen randomly. It happens when the number of reads (or possibly writes) on the RSS shown by 'onstat -g smx ses' reaches 4,294,967,296 (2^32). 'onstat -z' won't help here. Therefore you will only see this on busier systems and at fairly regular intervals in time, dependent on activity. Knowing this you can monitor it and schedule a restart at a more convenient time.
Ben.
------------------------------
Benjamin Thompson
------------------------------
Original Message:
Sent: Thu January 08, 2026 03:34 AM
From: Marcus Haarmann
Subject: BlockLogXmit status
APAR IT45413, solved in 14.10 xC11 according to the documentation
Original Message:
Sent: 1/8/2026 1:39:00 AM
From: AMIT PATEL
Subject: BlockLogXmit status
Dear All,
Happy New Year to All.
I'm working on Informix 14 on Solaris 5.


We get one issue mostly in every 3 months around for replication issue between Primary Server and RSS server and get the status on Primary server as "BlockLogXmit" and we need to restart the RSS node, and it impact the application connected with the RSS node.

How can we avoid these situation? in 2025 we faced this situation around 4 times. Kindly suggest.
Thanks
Amit Patel
------------------------------
AMIT PATEL
------------------------------