Can't imagine why it would..... I'd have to say no, those activities are completely unrelated. It makes no sense to me that resizing a datafile would invalidate a cursor. -Mark ________________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of neil kodner [nkodner@xxxxxxxxx] Sent: Thursday, September 17, 2009 8:41 To: oracle-l@xxxxxxxxxxxxx Subject: Can resizing datafiles affect the shared pool? Recently we had an issue where queries received a non-desirable explain plan, after weeks and weeks of production use. This lead to hundreds of sessions waiting on direct path write temp. I suspect this might be related to bind variable peeking but am not 100% sure. It is interesting to note that this happened shortly after a half- dozen datafiles were resized(by someone else of course :D). Does resizing datafiles during heavy production use invalidate cursors in the shared pool? This is on a single-instance database with about 2000 connections. -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l