Event_log shows the following errors
Info 2016-01-21 08:17:13.097122 126491 1938818896 Reader exited with code=1, pid = 86732 (from sourceSID)
Error 2016-01-21 08:17:13.062889 86732 3083581264 Reader: Error add user queue rv=16 que_adduser(queue_name,0x0aed0565+PR+o.sourceSID+sp_ordr+o.sourceSID) (from sourceSID) [module rim]
Notice 2016-01-21 08:17:13.054778 86732 3083581264 Reader: Shutdown SharePlex and increase the SP_QUE_MAX_QUEUES parameter (from sourceSID) [module que]
Notice 2016-01-21 08:17:13.045557 86732 3083581264 Reader: Maximum number of queues already exist (from sourceSID) [module que]
Notice 2016-01-21 08:17:12.986447 86732 3083581264 Reader: Cannot create queue queue_name (from sourceSID) [module que]
Notice 2016-01-21 08:17:11.451237 86732 3083581264 Reader: Oracle Available (from sourceSID) [module ord]
This issue is applicable to all queues, capture, read and post. In this solution we use the read process as an example.
The number of queues created exceed the maximum number of queues allowed by default or by current setting of SP_QUE_MAX_QUEUES parameter. This happens when sp_cop has a lot of queues.
RESOLUTION 1
1. Increase the value of the parameter SP_QUE_MAX_QUEUES from its current value to a value higher than the number of queues configured on the source. The number of queues is the sum of the capture, export and post queues. This parameter needs to be set to a value higher than the sum of all the queues. For example, if all your queues add up to 25, set this parameter to at least 26 as:
sp_ctrl>set param SP_QUE_MAX_QUEUES 26
2. Bounce Shareplex and start any process that has stopped with this error.
RESOLUTION 2
Perform this if your server has maxed out on memory and therefore more memory cannot be allocated.
1. Reconfigure Shareplex so that it creates fewer number of queues than specified in SP_QUE_MAX_QUEUES
2. Bounce Shareplex and start any process that has stopped with this error.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center