This content has been marked as final. Show 4 replies
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
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
If it is set to zero try to clear it.
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; /
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
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
These warnings are not coming frequently,but I saw this message in alert log and wanted to know whether this is anyway affecting our performance.I will try the change nexttime when we plan for a bounce.
I responded to your response in the other thread mseberg.I could not comeback on that issue as i'm struck with many performance issues.
If this answers this question, please remember to mark it so.
Also worth noting this is a not really a Data Guard issue and you might consider posting question like this in the General Database section.
Be warned its a tough crowd over there they expect Versions of OS, Oracle, exact error etc. I would read several postings before I add anything there.
Edited by: mseberg on Jul 20, 2011 10:30 AM
I found this message in alert.log of my production database and I followed the instruction of your thread, rebooted my database and after that no messages anymore.
Thanks for all.
Edited by: user7901599 on 26/09/2012 11:46