Analytics JMS queue Errors and Event Router Stops Writing To Dw_stg_data
(Doc ID 2217280.1)
Last updated on MAY 30, 2019
Applies to:Oracle Knowledge - Version 22.214.171.124 and later
Information in this document applies to any platform.
When the Analytics Event Router stops moving data for a long period of time the JMS queue can stop functioning correctly. Then Oracle Knowledge instances will receive errors.
First check the instance logs to see if the instances can reach the JMS queue or if this is an Analytics event router issue.
Analytics event router server can crash for a number of reasons:
- If there is error data in the JMS queue and no error queue set up. It is required that a JMS error queue also be set up.
- If the event router cannot connect to the Dw_stg_data table. Check the Analytics event router instance log.
- When the queue fills up and then the ICs go down getting an Analytics error with a jms queue full message. In this case the analytics events are collected in the .dat files need to be backed up and then processed when the system can be brought back up. In order to restart the Analtyics event router server more memory is needed than when starting it with a mostly empty queue.
We recommend that the Analtyics Event router run with 2G - 3G of memory to account for any Event router outages or issues.
If the server stops running then some events are lost. Some events can be recovered with the help of Oracle support.
How Can We Get Lost Events To DW_STAGE While Analytic Router Server was Down? (Doc ID 2348213.1)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document