# QUEUE\_TO\_QUEUE parameter not generated

**URL:** <https://forums.toadworld.com/t/queue-to-queue-parameter-not-generated/55338>\
**Category:** Toad for Oracle & DevOps Toolkit\
**Created:** [May 19, 2022, 8:59pm UTC](https://forums.toadworld.com/t/queue-to-queue-parameter-not-generated/55338 "2022-05-19T20:59:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rwiggins](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/rwiggins/32/289_2.png) [@rwiggins](https://forums.toadworld.com/u/rwiggins)\
**Post date:** [May 19, 2022, 8:59pm UTC](https://forums.toadworld.com/t/queue-to-queue-parameter-not-generated/55338/1 "2022-05-19T20:59:51Z")

</div>

When I generate scripts for AQ queues that propagate to remote AQ queues, the Toad-generated PL/SQL block omits the `QUEUE_TO_QUEUE` parameter of the `dbms_aqadm.add_subscriber` procedure. Comparing AQ queues doesn't notice differences in these parameters either. Still this way in 16.0.90.1509. I've added it below for illustration.

```auto
DECLARE
  aSubscriber sys.aq$_agent;
BEGIN 
  aSubscriber := sys.aq$_agent('SUBR_WMXP021_AQDN_OUTBOUND',
                              '"WMXPROP"."WMXP021_AQDN_OUTBOUND"@WMXP021.WORLD',
                              0);
  dbms_aqadm.add_subscriber
     ( queue_name => 'OMXOUTBOUND.WMXP021_AQDN_OUTBOUND'
      ,subscriber => aSubscriber
      ,queue_to_queue => TRUE);
END;
/

```

Thanks!

Rick

---

<div class="post-metadata">

**Author:** ![rwiggins](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/rwiggins/32/289_2.png) [@rwiggins](https://forums.toadworld.com/u/rwiggins)\
**Post date:** [May 19, 2022, 9:07pm UTC](https://forums.toadworld.com/t/queue-to-queue-parameter-not-generated/55338/2 "2022-05-19T21:07:42Z")

</div>

Also, Oracle is fussy about the generated `'"WMXPROP"."WMXP021_AQDN_OUTBOUND"@WMXP021.WORLD'` value of the `destination` parameter of the call to `DBMS_AQADM.SCHEDULE_PROPAGATION` procedure too.

```auto
BEGIN 
  DBMS_AQADM.SCHEDULE_PROPAGATION (
     queue_name => 'WMXP021_AQDN_OUTBOUND'
    ,destination => '"WMXPROP"."WMXP021_AQDN_OUTBOUND"@WMXP021.WORLD'
    ,start_time => null
    ,duration => null
    ,next_time => null
    ,latency => 60);
END;
/

```

I get errors until I remove the owner, the quotes, and the `.WORLD` from the value.

---

<div class="post-metadata">

**Author:** ![JohnDorlon](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/johndorlon/32/9997_2.png) [@JohnDorlon](https://forums.toadworld.com/u/JohnDorlon)\
**Post date:** [May 19, 2022, 9:11pm UTC](https://forums.toadworld.com/t/queue-to-queue-parameter-not-generated/55338/3 "2022-05-19T21:11:08Z")

</div>

Thanks. I'll just log this for now and will try to get to it soon.

The queue\_to\_queue bit seems straightforward. I'm guessing the destination that I'm showing has that exact format in the data dictionary. Seems risky to just randomly chop out .World and quotes. That one might require some research.

---

<div class="post-metadata">

**Author:** ![rwiggins](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/rwiggins/32/289_2.png) [@rwiggins](https://forums.toadworld.com/u/rwiggins)\
**Post date:** [May 19, 2022, 9:12pm UTC](https://forums.toadworld.com/t/queue-to-queue-parameter-not-generated/55338/4 "2022-05-19T21:12:11Z")

</div>

Oracle versions 12.2 and 19c. Not a big deal, now that I've got it through my thick head that I have to remember to add it or things won't propagate.

---

<div class="post-metadata">

**Author:** ![rwiggins](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/rwiggins/32/289_2.png) [@rwiggins](https://forums.toadworld.com/u/rwiggins)\
**Post date:** [May 19, 2022, 9:23pm UTC](https://forums.toadworld.com/t/queue-to-queue-parameter-not-generated/55338/5 "2022-05-19T21:23:21Z")

</div>

> [@rwiggins](#):
>
> I get errors until I remove the owner, the quotes, and the `.WORLD` from the value.

Actually, the owner seems fine, but not quotes or the `.WORLD`. The AQ stuff is pretty ancient and probably doesn't use `DBMS_ASSERT` to validate object names. The parsing of the remote object is probably hard-coded in the `DBMS_AQADM` package. Still not a big deal to fix the generated code.