Queues not handling delays...

Question

Question:
If the parameter that enables the Queue Monitor to handle delay intervals on queues (i.e., AQ_TM_PROCESSES) is not set to > 0, then no Queue Monitor background processes (ora_aqtm_<SID>) will be created and queues will not be able to handle delays?
Or, to put in another way, if AQ_TM_PROCESSES = 0, setting a delay on a queue for a payload will not work correctly, correct?

Answer 1

Still seems to be some debate between the developers and DBAs on whether or not AQ_TM_PROCESSES = 0 causes an issue in Oracle 10g 10.2.
This is what the Oracle Advanced Queueing Manual says:
===========================================
Prior to Oracle Database 10g, Oracle Streams AQ time manager processes were controlled by init.ora parameter AQ_TM_PROCESSES, which had to be set to nonzero to perform time monitoring on queue messages and for processing messages with delay and expiration properties specified. These processes were named QMNO-9, and the number of them could be changed using:
ALTER SYSTEM SET AQ_TM_PROCESSES=X
Parameter X ranged from 0 to 10. When X was set to 1 or more, that number of QMN processes were then started. If the parameter was not specified, or was set to 0, then queue monitor processes were not started.
Beginning in Oracle Streams AQ 10g Release 1 (10.1), this was changed to a coordinator-slave architecture, where a coordinator is automatically spawned if Oracle Streams AQ or Streams is being used in the system. This process, named QMNC, dynamically spawns slaves depending on the system load. The slaves, named qXXX, do various background tasks for Oracle Streams AQ or Streams. Because the number of processes is determined automatically and tuned constantly, you no longer need set AQ_TM_PROCESSES.
Even though it is no longer necessary to set AQ_TM_PROCESSES when Oracle Streams AQ or Streams is used, if you do specify a value, then that value is taken into account. However, the number of qXXX processes can be different from what was specified by AQ_TM_PROCESSES.
QMNC only runs when you use queues and create new queues. It affects Streams Replication and Messaging users.
No separate API is needed to disable or enable the background processes. This is controlled by setting AQ_TM_PROCESSES to zero or nonzero. Oracle recommends, however, that you leave the AQ_TM_PROCESSES parameter unspecified and let the system autotune.
Note:
If you want to disable the Queue Monitor Coordinator, then you must set AQ_TM_PROCESSES = 0 in your pfile or spfile. Oracle strongly recommends that you do NOT set AQ_TM_PROCESSES = 0. If you are using Oracle Streams, then setting this parameter to zero (which Oracle Database respects no matter what) can cause serious problems.
===========================================
Seems to me that AQ_TM_PROCESSES is no longer used as before but if used, and set to 0, it can cause issues and / or turn off the Oracle Queue Monitor....
Anybody's final vote on this matter??? Based on the manual and the responses I have heard so far, AQ_TM_PROCESSES = 0 does still matter in Oracle 10.2.