I understand that advanced queues currently aren't supported in OGG but there is an enhancement request for future support.
We are replicating multiple schemas, but need to handle AQ separately. As far as documented, in schema export mode advanced queue tables and all its dependencies are exported,
however, in table mode those queues dependencies have to be manually exported.
Now this next phase involves mapping queues and all its dependencies need to be mapped, but I'm not finding a consistent way to do that.
Already tried
- querying dba_queues (provides information on queue name and queue table).
- extract queue metadata through dbms_metadata (passing AQ_QUEUE and AQ_QUEUE_TABLE as types)
But those methods don't seem to provide a consistent way to detect queue underlying dependencies. Furthermore, the queues aren't following a naming convention, so I can't just
do a select ... like '%' and assume the resulting objects are the only ones to be exported.
What strategy can I use to find necessary information to safely export queues?
Another information is that all these queues are fully consumed every night, so would it be an option to just recreated the queues on the target database instead of doing export import?