It is possible that the note is unpublished because it was wrong. I remember seeing it on metalink on one occasion, and sending someone a test case that showed that outlines still worked with cursor_sharing if you RAN the code, rather than trying to do 'create ...'. (It's how I'd been doing my 'go_faster' hint for months). Regards Jonathan Lewis http://www.jlcomp.demon.co.uk/faq/ind_faq.html The Co-operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/seminar.html Optimising Oracle Seminar - schedule updated Sept 19th ----- Original Message ----- From: "Wolfson Larry - lwolfs" <lawrence.wolfson@xxxxxxxxxx> To: <lawrence.wolfson@xxxxxxxxxx>; <breitliw@xxxxxxxxxxxxx>; "Oracle Discussion List" <oracle-l@xxxxxxxxxxxxx> Sent: Monday, December 20, 2004 6:51 PM Subject: RE: Stored outline problems I got a reply back from Oracle Support. They referenced an unpublished Note 132547.1 Using Stored Outlines, Which mentions on page 4: "Stored outlines are not used when: o A hint in the stored outline becomes invalid. o CURSOR_SHARING = FORCE CURSOR_SHARING = FORCE disables the use of stored outlines. CURSOR_SHARING was introduced in Oracle8i Release 2. It internally replaces literals values in queries with bind variables, thus allowing these statements to be shared. -- //www.freelists.org/webpage/oracle-l