How to identify a user flooding Enterprise Replication (ER) send/receive queues with transactions
This document applies only to the following language version(s):
This document can be used to identify a user flooding Enterprise Replication (ER) send/receive queues with transactions
Several occasions when ER/CDR queues become 'flooded' with transactions, it is critical to identify the user(s) triggering Data Manipulation Language (DML) SQL statements which consume a lot of logical log area that can cause the DDR Block situation and hang the Informix instance.
A user triggered a huge transaction causing several logical logs to be filled and ER sync to hang.
Diagnosing the problem
1. Look at 'onstat -g rqm sendq'
2. Check the progress table and look for the 'group id' with the largest bytes queued;
3. The 'group id' is really the 'replicate id';
4. Look for the replicate id from 'onstat -g cat' to find the table used in that replicate;
5. With the table partnum information, now you can use one of the following options to find the session id or userthread:
- onstat -g opn
- sqltrace history
Looking 'onstat -g rcv full" from one of the target servers also lists replicated id's and bytes received.
Resolving the problem
After finding the user/session id, cancell the userthread/session causing the flood.
More support for:
Software version: 11.1, 11.5, 11.7
Operating system(s): AIX, HP-UX, Linux, Solaris
Software edition: All Editions
Reference #: 1572991
Modified date: 05 November 2013
Translate this page: