RE: Maintaining Advanced Queue IOT/Index Objects: _aq_tm_scanlimit
From: <fmhabash_at_gmail.com>
Date: Wed, 7 Sep 2016 11:17:01 -0400
Message-ID: <57d02f6d.075a240a.43909.c287_at_mx.google.com>
Thank you
Date: Wed, 7 Sep 2016 11:17:01 -0400
Message-ID: <57d02f6d.075a240a.43909.c287_at_mx.google.com>
Agreed.
We worked with MOS’s advanced queing group and they had to dig for information on this parameter. The ‘_aq_tm_scanlimit’ parameter sets a limit on the number of blocks QManagers recycle from the tail end of index/IO segments. Our databases has it set to 0, but MOS requested that we set it to 256.
We also confirmed it is dynamic if changed to > 0. In reverse, it is recommended to restart the instance.
As for the 3 known bugs, 2 are simply harmless as they only cause error messages to go to the alert logs and they can be ignored.
We are testing this change and I can share the final outcome when done.
Thank you
From: Powell, Mark
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Sep 07 2016 - 17:17:01 CEST
- image/png attachment: A231F2304386490F8842A5905D144184.png
