RE: Reloads and Invalids - Check and Avoid
From: Allen, Brandon <Brandon.Allen_at_OneNeck.com>
Date: Mon, 15 Mar 2010 09:48:43 -0700
Message-ID: <64BAF54438380142A0BF94A23224A31E11950643E9_at_ONEWS06.oneneck.corp>
There may be more advanced methods, but here are a few basic ways to reduce reloads and invalidations:
Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.
Date: Mon, 15 Mar 2010 09:48:43 -0700
Message-ID: <64BAF54438380142A0BF94A23224A31E11950643E9_at_ONEWS06.oneneck.corp>
There may be more advanced methods, but here are a few basic ways to reduce reloads and invalidations:
Reloads - either increase the size of your shared pool, or decrease the number of distinct SQL statements in order to reduce the load on your shared pool; consider using bind variables where appropriate to promote sharing of cursors
Invalidations - minimize changes to your database objects, changes to permissions, and updating statistics during busy times as these activities will cause all dependent cursors to be invalidated (note that in 10g+ dbms_stats.auto_invalidate may reduce the amount of invalidations from updating stats).
Regards,
Brandon
Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Mar 15 2010 - 11:48:43 CDT