Friday, April 24, 2009

WARNING: AQ_TM_PROCESSES is set to 0. System operation might be adversely affected

Dear Friends, If your getting below "Warning" message frequently in the alert.log file... "WARNING: AQ_TM_PROCESSES is set to 0. System operation might be adversely affected." Kindly check the following metalink note: 428441.1 Solution: The parameter "AQ_TM_PROCESSES" should not be set "0" or "Unset". Set it atlest for "1". It is dynamic parameter so no need to bounce the db server. SQL>alter system set AQ_TM_PROCESSES=1;

(http://dbataj.blogspot.com/2009/04/warning-aqtmprocesses-is-set-to-0.html)

13) To find locked SQL query in Oracle? Solution: SELECT sql_text FROM v$sql WHERE sql_id IN (SELECT sql_id FROM v$session WHERE sid IN (SELECT sid FROM v$lock WHERE (id1,id2,TYPE) IN (SELECT id1, id2, TYPE FROM v$lock WHERE request > 0))) (http://weoracle.blogspot.com/ )

Re: WARNING: AQ_TM_PROCESSES is set to 0. System operation might be adversely a mseberg Jul 20, 2011 3:01 PM (in response to 873387) In 10.2, it is recommended to leave the parameter aq_tm_processes unset and let the database auto-tune the parameter. Setting aq_tm_processes parameter explicitly to zero which disables the time monitor process (qmn), can disrupt the operation of the database due to several system queue tables used when the standard database features are used. Hey, check your post from yesterday too and I come back with a fix for this Best Regards

mseberg Before you do anything read this : "Warning: Aq_tm_processes Is Set To 0" Message in Alert Log After Upgrade to 10.2.0.3 or Higher [ID 428441.1]

Run this as sysdba declare mycheck number; begin select 1 into mycheck from v$parameter where name = 'aq_tm_processes' and value = '0' and (ismodified <> 'FALSE' OR isdefault='FALSE'); if mycheck = 1 then dbms_output.put_line('The parameter ''aq_tm_processes'' is explicitly set to 0!'); end if; exception when no_data_found then dbms_output.put_line('The parameter ''aq_tm_processes'' is not explicitly set to 0.'); end; / If it is set to zero try to clear it. alter system reset aq_tm_processes scope=spfile Beware this requires a database bounce. If you find this helpful please mark it so Edited by: mseberg on Jul 20, 2011 9:55 AM PS This isn't a fire, you can wait to deal with it if you can stand the error messages that will keep coming. Edited by: mseberg on Jul 20, 2011 10:00 AM

(https://forums.oracle.com/thread/2257907 )
Saturday, 1 May 2010

oracle WARNING: AQ_TM_PROCESSES is set to 0

in alert log <<<< replication_dependency_tracking turned off (no async multimaster replication found) WARNING: AQ_TM_PROCESSES is set to 0. System operation might be adversely affected. Completed: ALTER DATABASE OPEN

as per metalink 428441.1

SQL> declare 2 mycheck number; 3 begin 4 select 1 into mycheck from v$parameter where name = 'aq_tm_processes' and value = '0' 5 and (ismodified <> 'FALSE' OR isdefault='FALSE'); 6 if mycheck = 1 then 7 dbms_output.put_line('The parameter ''aq_tm_processes'' is explicitly set to 0!'); 8 end if; 9 exception when no_data_found then 10 dbms_output.put_line('The parameter ''aq_tm_processes'' is not explicitly set to 0.'); 11 end; 12 / PL/SQL procedure successfully completed. SQL> set serveroutput on SQL> / The parameter 'aq_tm_processes' is explicitly set to 0! PL/SQL procedure successfully completed.

conn / as sysdba

SQL> alter system set aq_tm_processes = 1 scope=spfile ; System altered.

re start database then check the value

SQL> col TYPE format a15 set linesize 200

SQL> show parameter aq_tm_processes NAME TYPE VALUE ------------------------------------ --------------- -----------------------------aq_tm_processes integer 1 Posted by Anuj Singh at Saturday, May 01, 2010 (http://anuj-singh.blogspot.com/2010/05/oracle-warning-aqtmprocesses-is-set-to.html)

If you get WARNING while starting up your database:

WARNING: AQ_TM_PROCESSES is set to 0. System operation might be adversely affected.

You can do these steps based on Metalink Document: 428441.1

SQL> connect / as sysdba SQL> alter system reset aq_tm_processes scope=spfile sid='*'; SQL> shutdown immediate; SQL> startup;

It works for me

(http://ericwijaya.wordpress.com/2009/11/06/warning-aq_tm_processes-is-set-to-0-systemoperation-might-be-adversely-affected/)

In 10.2, it is recommended to leave the parameter aq_tm_processes unset and let the database autotune the parameter. Setting aq_tm_processes parameter explicitly to zero which disables the time monitor process (qmn), can disrupt the operation of the database due to several system queue tables used when the standard database features are used. You cannot determine if aq_tm_processes is set explicitly to zero just by querying v$parameter. A check to see if the parameter is explicitly zero is: connect / as sysdba set serveroutput on declare mycheck number; begin select 1 into mycheck from v$parameter where name = 'aq_tm_processes' and value = '0' and (ismodified <> 'FALSE' OR isdefault='FALSE'); if mycheck = 1 then dbms_output.put_line('The parameter ''aq_tm_processes'' is explicitly set to 0!'); end if; exception when no_data_found then dbms_output.put_line('The parameter ''aq_tm_processes'' is not explicitly set to 0.'); end; /

If it is set to zero, it is recommended to unset the parameter. alter system reset aq_tm_processes scope=spfile sid='*'; However, this requires bouncing the database if unable to do so alter system set aq_tm_processes = 1;

(http://asanga-pradeep.blogspot.com/2008/06/aqtmprocesses-is-set-to-0.html )