In a busy Q Rep env with many bi-di Q subs, there may lots of P2PNORECAPTURE signal insert into IBMQREP_SIGNAL control table by Q Apply program.
As per design, Q Capture delete up to 10000 rows at a time for one prune interval.
When the average P2PNORECAPTURE insert speed faster than Q Capture house keeper cleanning speed, IBMQREP_SIGNAL table may growing very big.
Although we know reduce the parameter of prune_interval could help to solve the issue， customer think it will be helpful to get a message if this situation appears with a hint to reduce the pruning interval, like print a warning message to prompt customer that they may take a consideration to reduce the prune interval, otherwise data may accumlated and signal table will grow big
|Who would benefit from this IDEA?||avoid signal table grow too big|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions