Looking for suggestions - how find cause of sql invalidations
From: Chris Taylor <christopherdtaylor1994_at_gmail.com>
Date: Tue, 18 Jul 2017 10:37:03 -0500
Message-ID: <CAP79kiRhd3Q7zG_PNyPZ06WB_=pq2ETmTmqJQtXojR+P361DBw_at_mail.gmail.com>
DB: 12.1.0.2
OS: Red Hat Enterprise Linux Server release 6.8 (x86_64)
Date: Tue, 18 Jul 2017 10:37:03 -0500
Message-ID: <CAP79kiRhd3Q7zG_PNyPZ06WB_=pq2ETmTmqJQtXojR+P361DBw_at_mail.gmail.com>
DB: 12.1.0.2
OS: Red Hat Enterprise Linux Server release 6.8 (x86_64)
TL;DR: How to find cause of high sql invalidations when nothing obvious is
happening (such as stats or table ddl).I've checked last_analyzed from DBA_TAB_PARTITIONS and that the table hasn't been analyzed during the period of invalidations.
Much of the SQL being executed against this table is "EXECUTE IMMEDIATE" from within pl/sql.
One of the code blocks does have an IF statement that would do a "LOCK TABLE" if the condition is met (I can't tell if that condition is being met however). Would a LOCK TABLE cause invalidations?
Any suggestions on how to crack this particular egg?
Chris
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jul 18 2017 - 17:37:03 CEST