Question about managing AQ - How to efficiently purge the exception queue
edited Dec 12, 2013 4:51AM in GoldenGate, Streams and Distributed Database (MOSC) 2 commentsAnswered
I'm experiencing a problem with the AQ system. The exception queue has not been purged for quite some time.
The QUEUE is using a table named QUEUE1 as the underlying table. Unfortunately there is a QUEUE table that the 'PURGE_EXCEPTION_QUEUE' procedure is 'purging'. (We just discovered that the QUEUE wasn't using the QUEUE table!).
I've discovered that the QUEUE1 table has over 74 million rows in the 'EXPIRED' state going back over 4 years. The corresponding history table has > 500 million rows. It is unclear if this is causing any real problems but my gut feel is that we need to clean up this data.
0