Thanks
Mohammed Amine HLIMI, August 05, 2016 - 9:09 pm UTC
Thanks for the feedback.
I know, using DBMS_SHARED_POOL.PURGE will force a Hard parse the next time the query is executed, but I wanted the quickest way to close all open CURSORs related to some problematic query (from another session) without killing the session. But it seems impossible: "PGA-Private SQL area" <> "SGA-Shared Pool-Shared SQL Area".
Of course killing the session will close all related open cursors, it just took a little time before it reflects in my query of v$sesstat ... I wanted to edit the question to remove this part but couldn't :)
Anyway thank you again for the answer.