Comments on: Scripts for showing execution plans via plain SQL and also in Oracle 9i

By: Oracle Query Optimizer Vanishing Acts « Charles Hooper's Oracle Notes

Oracle Query Optimizer Vanishing Acts « Charles Hooper's Oracle Notes — Sat, 04 Feb 2012 03:51:58 +0000

[...] How about testing the real thing… actually executing the SQL statements in the test case script on an older version of Oracle Database – will you receive the same execution plans? I tested Oracle Database 10.2.0.5 and obtained the same execution plans as I saw with 11.2.0.2. Anyone with access to Oracle Database 10.1, 9.2, 9.0.1, or 8.1.7 that is able to test the above script? The DBMS_XPLAN.DISPLAY_CURSOR function is not available in Oracle Database versions prior to 10.1, so you will need to be creative to display the execution plan (AUTOTRACE may show the wrong execution plan - you might experiment with a solution offered by Tanel Poder for Oracle Database 9i). [...]

By: Venkat

Venkat — Mon, 14 Nov 2011 11:57:15 +0000

Hi tanel,

Do you have that xmsh & xm scripts. i have downloaded long back and misplaced. We need it for 9i db tuning.

Thanks
Venkat

By: Tanel Poder

Tanel Poder — Thu, 26 May 2011 11:13:31 +0000

@D Owen

Get the zip file with all scripts here:

http://tech.e2sn.com/oracle-scripts-and-tools

By: D Owen

D Owen — Thu, 26 May 2011 10:37:16 +0000

Hi Tanel,
has the link to the scripts been changed, I get a 404 whilst looking for them here and on your e2sn site.

Thanks

By: JC Dauchy

JC Dauchy — Wed, 10 Nov 2010 10:19:37 +0000

I noticed the comment about 9i, I saw also a page on Jonathan Lewis website about this behaviour. It took me time since I could believe there was a problem on xms script.

Thanks

By: Tanel Poder

Tanel Poder — Tue, 09 Nov 2010 18:29:07 +0000

@JC Dauchy

Thanks,

The problem is not really in xms.sql, it does what it’s supposed to do – it shows the plan for last cursor executed in the session. If you enable dbms_output buffer fetching using set serveroutput on (or some of the scripts do this) then sqlplus will always try to fetch the dbms_output buffer using a call to DBMS_OUTPUT.GET_LINES… and xms ends up showing that as it’s the last command executed by sqlplus.

So, yep, “set serveroutput off” will disable that behaviour and xms will see the right statement in prev_hash_value…

Also, on 9i xms won’t work at all as the prev_hash_value doesn’t work properly on 9i. On 9i you’d have to identify the hash value of statement of interest yourself and run @xmsh

By: JC Dauchy

JC Dauchy — Tue, 09 Nov 2010 14:46:43 +0000

Just a wee thing, I’ve just spent one day trying to understand why the “xms.sql” script was not finding the right last SQL, I noticed that setting :

=> set serveroutput off

Correct the problem, otherwise the previous SQL was always ‘DBMS_OUTPUT…’
This migth help someone..
Anyway, awesome scripts.

By: Sometimes things are easy (Part 1): How to fix wrapped execution plan text? | Tanel Poder's blog: Core IT for Geeks and Pros

Mon, 18 Jan 2010 16:26:40 +0000

[...] http://blog.tanelpoder.com/2009/05/26/scripts-for-showing-execution-plans-via-plain-sql-and-also-in-... [...]

By: Plans gone AWRy – an invASHtigation « OraStory

Plans gone AWRy – an invASHtigation « OraStory — Tue, 29 Dec 2009 16:37:48 +0000

[...] If you do hit these display issues then you might prefer to pull your plans from dba_hist_sql_plan for example using a variation of Tanel’s script here. [...]

By: Dakshin

Dakshin — Wed, 28 Oct 2009 08:25:09 +0000

is there a way to get older SQL Plans from history tables? Thanks.