> Of course, you can explain plan into your own table. In this case, I've got about 6 different users/schema owners and it's a pretty low usage db. A central plan_table makes a little more sense in this case. It's not that the plan_table as a gtt is not a good idea (in most cases it is), it's that those cases where a central plan_table and preserving the explain plans are desirable, you get bit unexpectedly. I'm just glad I found it out before I went through the 100 or so queries that I was wanting to keep. That would have sent me to screaming and yelling to the closest bar. Gee, now that I mention it, not documenting GTT plan_table is a potentially GREAT thing! > > > > > Okay, Pete. Where's the doc on this one? ;) > > Coming with the next weekly tip. > > -- > Mladen Gogala ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------