Exporting the execute explain plan

Hi-
Is there a way to export the explain plan (in a pretty print format) from SQL Developer 1.0.0 - copying and pasting doesn't work. For large plans it is almost un-readable.
Thanks in Advance.

We have a Explain Plan print bug in the development process for 1.1
Sue

Similar Messages

  • Unable to Execute Explain Plan for the selected SQL

    When working with several SQL statements in one SQL Worksheet you execute the specific statement by selecting it and pressing F9.
    The same is not possible for the explain plan though.
    If you select the first SQL statement and press F6, the explain plan is executed correctly. If you try the same for any other statement, all you get is 'No SQL statement entered.' on the status bar.
    Maciej

    It is available.
    Type this in.
    create table xx (yy number(10));
    create table zz (aa number(10));
    select * from xx;
    select * from zz;Run all these statements by pressing f5.
    Place the cursor on 'select * from xx;'.
    Press f6 gives you a plan.
    Place the cursor on 'select * from zz;'
    press f6 gives you a different plan.
    The problem seems to be that F6 is still suffering from a statement selection bug which is already fixed for f9. That is selecting a whole statement results in failure to recognise a statement and the 'No statement entered' message.

  • How to export results of explain plan?

    A colleague tells me that in an older version of SQLDeveloper (1.2.1, perhaps?), he was able to export the results of the explain plan operation (I don't know what export forms were available). In the current version (1.5.1), it generates a tree component with information I can look at, but there's no way to write out these results in any form. Am I missing something?

    HOW TO TRANSPORT A SQL TUNING SET [ID 456019.1]
    Modified 08-SEP-2008 Type HOWTO Status PUBLISHED
    In this Document
    Goal
    Solution
    Applies to:
    Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.1.0.6
    Information in this document applies to any platform.
    10.2.X,11.1.X
    Goal
    The Purpose of This Note is to Show the Steps needed to Transport a Sql Tuning Set from
    One Database server to another Database Server.
    Solution
    The Sql Tuning Set name is small_sh_sts_4.It is on 10.2.0.2.0 Database server.
    It has 4 sqls .
    select sql_id, substr(sql_text,1, 15) text
    from dba_sqlset_statements
    where sqlset_name = 'small_sh_sts_4'
    order by sql_id;
    SQL_ID TEXT
    4qdz7j26mdwzb SELECT /*+ my_q
    6y289t15dqj9r SELECT /*+ my_q
    ckm14c67njf0q SELECT /*+ my_q
    g37muqb81wjau SELECT /*+ my_q
    1) Create the Staging Table ON THE SOURCE SYSTEM ( IN this case 10.2.0.2.0 ) .
    execute DBMS_SQLTUNE.CREATE_STGTAB_SQLSET(table_name =>'TEST');
    PL/SQL procedure successfully completed.
    SQL> select count(*) from test;
    COUNT(*)
    0
    2) Popluate the table TEST using DBMS_SQLTUNE.PACK_STGTAB_SQLSET THE SOURCE SYSTEM (IN this case 10.2.0.2.0 )
    execute DBMS_SQLTUNE.PACK_STGTAB_SQLSET(sqlset_name => 'small_sh_sts_4',staging_table_name => 'TEST');
    PL/SQL procedure successfully completed.
    select count(*) from test;
    SQL> select count(*) from test;
    COUNT(*)
    4
    3) Export the table table test on THE SOURCE SYSTEM ( IN this case 10.2.0.2.0 )
    and move the table to the Destination Server
    and Import it . The staging table TEST can also be moved using
    the mechanism of choice such as datapump or database link.
    While exporting the table you will see something like
    About to export specified tables via Conventional Path ...
    Table(T) or Partition(T:P) to be exported: (RETURN to quit) > TEST
    . . exporting table TEST 4 rows exported
    . . exporting table TEST_CBINDS 0 rows exported
    . . exporting table TEST_CPLANS 34 rows exported
    Import on the Destination system ( IN this CASE it was 11.1.0.6.0 )
    While Importing the table you will see something like
    . importing SH's objects into SH
    . importing SH's objects into SH
    . . importing table "TEST" 4 rows imported
    . . importing table "TEST_CBINDS" 0 rows imported
    . . importing table "TEST_CPLANS" 34 rows imported
    Import terminated successfully without warnings.
    SQL> select count(*) from test;
    COUNT(*)
    4
    Verify the contents of DBA_SQLSET or USER_SQLSET on the Destination system
    Select NAME,CREATED,STATEMENT_COUNT FROM DBA_SQLSET;
    4) Unpack the table using DBMS_SQLTUNE.UNPACK_STGTAB_SQLSET on the Destination system ( IN this CASE it was 11.1.0.6.0 )
    execute DBMS_SQLTUNE.UNPACK_STGTAB_SQLSET( sqlset_name => '%',-
    replace => TRUE,-
    staging_table_name => 'TEST');
    Select NAME,OWNER,CREATED,STATEMENT_COUNT FROM DBA_SQLSET;
    NAME CREATED STATEMENT_COUNT
    small_sh_sts_4 24-AUG-07 4
    Related
    Products
    •Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition

  • "Execute Explain Plan" button disabled

    I'm using the 1.1.3 version of SQL Developer included in the Oracle 11g distribution for Windows.
    After connecting to a database and executing a query, I am unable to view its execution plan because the explain plan button is greyed-out. The connected user has the PLAN_TABLE table in its schema.

    Are all the buttons grayed out on the worksheet or just the explain plan button? If you look at your worksheet, is the drop list on the right hand side populated? i.e does it display your user connection? If not, select your connection in the drop kist and the icons will change from gray to available.
    You say in your message that you upgraded to 1.1. I assume you did a fresh install in a new directory.
    Regards
    Sue

  • Saving/exporting autotrace and explain plan

    Is it at all possible to export or save the explain plan and/or autotrace information from Oracle SQL Developer to text?

    You must first click Explain icon or Autotrace Icon to generate them before you can check under the tab.

  • Invalid column name when executing explain plan

    SQL Developer version 4.0, SQL Worksheet, Windows 2000, Database 9.2.0.6.
    When attempted to run a explain plan on a simple two table join query, it generates error invalid column name. Removed aliases and simplify query to one table row count, and still get the same error. Even tried the schema owner and got the same error.
    I decided to check the explain plan table and found out that it was from an older version. Recreated the explain plan table and was able to run the explain plan.
    I'm just posting this in the event somebody else runs into the same problem.

    This was fixed in the 4.1 or 1215 build. Please update by downloading or check for updates.
    -thanks
    kris

  • How to get the complete explain plan stored in a particular OUTLINE

    Hi,
    How do I get the complete text of the explain plan stored in a particular outline? I have the name of the outline.
    I can't run the query which has this outline as it is on production.I want to know which tables/views will have the explain plan text?
    Thanks,
    Sach
    Edited by: user631085 on Mar 29, 2009 11:27 PM
    Edited by: user631085 on Mar 29, 2009 11:29 PM
    Edited by: user631085 on Mar 29, 2009 11:29 PM

    You can access the _OUTLINES views.
    Pelase refer the following and look for 'Viewing Outline Data':
    http://youngcow.net/doc/oracle10g/server.102/b14211/outlines.htm

  • Explain plan not working

    When I run the explain plan by pressing F6 or the execute explain plan button I get the message "Failed to query plan_table" "invalid column name".
    However I can do a select * from plan_table
    I'm using version 1.5.4 with the latest patch set.
    Any ideas?

    Getting an invalid column name when performing an explain plan suggests that you have an old plan table structure, compared to what SQL Developer is expecting for your DB version. This can easily happen where your DB has been upgrade without keeping the plan table up to date.
    Do you get any "old plan table" messages if you execute the "select * from table(dbms_xplan.display_cursor);"?
    theFurryOne

  • Understanding the COST column of an explain plan

    Hello,
    I executed the following query, and obtained the corresponding explain plan:
    select * from isis.clas_rost where cour_off_# = 28
    Description COST Cardinality Bytes
    SELECT STATEMENT, GOAL = FIRST_ROWS               2     10     1540
    TABLE ACCESS BY INDEX ROWID     ISIS     CLAS_ROST     2     10     1540
    INDEX RANGE SCAN     ISIS     CLAS_ROST_N2     1 10     
    I don't understand how these cost values add up. What is the significance of the cost in each row of the explain plan output?
    By comparison, here is another plan output for the following query:
    select * from isis.clas_rost where clas_rost_# = 28
    Description COST Cardinality Bytes
    SELECT STATEMENT, GOAL = FIRST_ROWS               1     1     154
    TABLE ACCESS BY INDEX ROWID     ISIS     CLAS_ROST     1     1     154
    INDEX UNIQUE SCAN     ISIS     CLAS_ROST_U1     1 1     
    Thanks!

    For the most part, you probably want to ignore the cost column. The cardinality column is generally what you want to pay attention to.
    Ideally, the cost column is Oracle's estimate of the amount of work that will be required to execute a query. It is a unitless value that attempts to combine the cost of I/O and CPU (depending on the Oracle version and whether CPU costing is enabled) and to scale physical and logical I/O appropriately). As a unitless number, it doesn't really relate to something "real" like the expected number of buffer gets. It is also determined in part by initialization parameters,session settings, system statistics, etc. that may artificially increase or decrease the cost of certain operations.
    Beyond that, however, cost is problematic because it is only as accurate as the optimizer's estimates. If the optimizer's estimates are accurate, that implies that the cost is reasonably representative (in the sense that a query with a cost of 200 will run in less time than a query with a cost of 20000). But if you're looking at a query plan, it's generally because you believe there may be a problem which means that you are inherently suspicious that some of the optimizer's estimates are incorrect. If that's the case, you should generally distrust the cost.
    Justin

  • How enable the explain plan in JDeveloper?

    Can you tell me how to get explain plan in JDeveloper?
    Thanks in advance.

    If you are using jdev 11 just open a sql work sheet, type in your statement or query and hit F6 (Execute Explain Plan) or the third button from the right in the work sheet toolbar.
    Timo

  • Need steps to capture a particular explain plan using the store outlines

    Hi,
    I have got the needed explain plan using hints in my query. I need to capture it using stored outlines.
    I am using Oracle 10.2.0.3.
    Can someone provide me the steps to capture this plan using an Stored Outline?I dont want to use any other method.
    Thanks,
    Sach

    I have got the needed explain plan using hints in my query. I need to capture it using stored outlines.Do you mean creating outline?
    Can someone provide me the steps to capture this plan using an Stored Outline?I dont want to use any other method?[http://www.oracle-base.com/articles/misc/Outlines.php]
    [http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_6005.htm]
    Edited by: Anantha on Apr 2, 2009 9:07 AM

  • Execution Time & Explain Plan Variations

    I have a scenario here. I have 2 schemas; schema1 & schema2. I executed a lengthy SELECT statement of 5 TABLE JOIN in these 2 schemas. I am getting totally different execution time (one runs at 0.3 seconds & the other at 4 seconds) and a different Explain Plan. I assume that, since its the same SELECT statement in these schema, I should get the same Explain Plan. What could be the reason for these dissimilarities? Oracle Version: 9.2.0.8.0. I am ready to share the Explain Plan of these 2 schemas. But they are of length around 300 lines.
    Thank you.

    There are many factors come in to play here.
    1.) Size of all tables involved are same
    2.) structures are also same
    3.) Also indexes are same
    4.) Also stats are up to date on both
    5.) Constraints and other factors are also same.
    regards
    PravinAnd a few more.
    6) session environments are the same
    7) bind variable values are the same - or were at first execution
    I'd change 4 to read Optimizer statistics are the same. (not up to date which is a bit vague).
    In short if you are using the CBO and feed in the exact same inputs you will get the exact same plan, however typically you won't get the exact same inputs and so may get a different plan. If your query has a time element and the two queries are hard parsed at different times it may actually be impossible to get the same input - for example the percentage of a table that is returned by a predicate like
    timestamp_col > sysdate - 1 will be estimated differently depending on the time of parsing for the same data.
    That all said looking at the plans might reveal some obvious differences, though perhaps it might be better to point at a URL that holds the plans given the length you say they are.
    Niall Litchfield
    http://www.orawin.info/
    null

  • Explain Plan from TKPROF trace file.

    Hello,
    My procedure is taking time for that i have trace on in procedure fo find explain plan of particular query.
    Using below statement Trace is on.
       EXECUTE IMMEDIATE 'ALTER SESSION SET SQL_TRACE = TRUE';
       EXECUTE IMMEDIATE 'ALTER SESSION SET TIMED_STATISTICS = TRUE';Now for getting expalin plan from TKPROF i have used below statement but for some query i have found explain paln and some case i cant found explain plan.
    tkprof mf_ora_23773.trc mf_ora_23773.txt explain =abc/abc
    can u please help me to analyze where i m wrong?
    Thanks.

    First of all, you should best avoid using the explain= clause on the tkprof command line.
    This will run explain plan on the statement in the trace file, and that explain plan can even be wrong, as there is no information on datatypes in the trace file.
    The real explain plan data is flushed to the trace file, when the program issues commit or rollback. Oracle always issues an implicit commit when the program disconnects, so when you run the program to completion you should have explain plan output in your trace files.
    You won't get explain plan output if you don't have access to the objects in the SQL statement. Also recursive SQL won't produce explain plan result.
    One would need to see part of your trace file to verify your assertion the explain clause doesn't always work.
    Sybrand Bakker
    Senior Oracle DBA

  • How to see an explain plan?

    Hi all,
    I'm looking to tune one sql sentence of my application. To do it, I've used the sqltune package. When I see the report, I obtain the actual explain plan and, finally the suggestion to use an SQL Profile.
    How can I see the new explain plan of this option before apply it?
    I attach the report result for your information:
    SELECT DBMS_SQLTUNE.report_tuning_task('analisis_matriculation_view') AS recommendations FROM dual;SQL> SQL> SQL>
    RECOMMENDATIONS
    GENERAL INFORMATION SECTION
    Tuning Task Name : analisis_matriculation_view
    Tuning Task Owner : A9
    Scope : COMPREHENSIVE
    Time Limit(seconds) : 3600
    Completion Status : COMPLETED
    Started at : 08/11/2010 09:33:18
    Completed at : 08/11/2010 10:23:16
    Number of SQL Profile Findings : 1
    Schema Name: A9
    SQL ID : gd8b5pwyj0yu8
    SQL Text : SELECT PO.ID POID, BO.ID BOID, MAT.AGENT_ID AGENTID,
    MAT.AGENCY_ID AGENCYID, MAT.ID MATID,MAT.PARTNERBRANCH_ID
    PBRANCHID, MAT.DOSSIERNUMBER, MAT.DOSSIERVERSION,
    MAT.FILINGDATE,MAT.TELEMATIC, MAT.MANUALDGTTAXCODE,
    MAT.ASSIGNDGTTAX, MAT.STATUS, MAT.PLATENUMBER,MAT.REJECTIONCAUSE,
    MAT.REJECTIONNOTES, MAT.COLOR, MAT.CREATEDON, MAT.MODIFIEDON,
    FO.COLOR,AG.MEMBERID, US.NAME AGENTNAME, US.SURNAME
    AGENTSURNAME, US.SURNAME2 AGENTSURNAME2, US.NIF AGENTNIF,AY.NAME
    AGENCYNAME, VD.SERIALNUMBER, VOWN.NAME OWNERNAME, VOWN.SURNAME
    OWNERSURNAME,VOWN.SURNAME2 OWNERSURNAME2, UPPER(VOWN.NAME) || '
    ' || UPPER(VOWN.SURNAME) || ' ' || UPPER(VOWN.SURNAME2)
    OWNERFULLNAME,VOWN.FISCALID OWNERNIF, FO.ID FOLDERID, FO.NAME
    FOLDERNAME, FO.STATUS FOLDERSTATUS, IVTM.ID IVTMID,IVTM.STATUS
    IVTMSTATUS, IVTM.FINALAMOUNT IVTMAMOUNT, IVTM.IVTMCOLLECTOR,
    F576.ID F576ID,F576.PAYMENTCOMPLETEREFNUMBER NRC576,
    F576.MATRICULATIONCODE CEM576, F576.AEATELECTRONICCODEMANUAL
    CEM576MANUAL,F576.NRCMANUAL NRC576MANUAL, F06.ID F06ID,
    F06.MATRICULATIONCODE CEM06, F06.AEATELECTRONICCODEMANUAL
    CEM06MANUAL,F06.NRE NRE06, F06.NREMANUAL NRE06MANUAL, F05.ID
    F05ID, F05.MATRICULATIONCODE CEM05, F05.AEATELECTRONICCODEMANUAL
    CEM05MANUAL FROM A9_MATRICULATION MAT INNER JOIN A9_AGENT AG ON
    (MAT.AGENT_ID = AG.ID) INNER JOIN A9_USER US ON (AG.ID = US.ID)
    INNER JOIN A9_BRANCHOFFICE BO ON (AG.BRANCHOFFICE_ID = BO.ID)
    INNER JOIN A9_PROFESSIONALORDER PO ON (BO.PROFESSIONALORDER_ID =
    PO.ID) INNER JOIN A9_AGENCY AY ON (MAT.AGENCY_ID = AY.ID) INNER
    JOIN A9_VEHICLEDATA VD ON (MAT.VEHICLEDATA_ID = VD.ID) INNER
    JOIN A9_VEHICLEOWNER VOWN ON (VOWN.MATRICULATION_ID = MAT.ID)
    LEFT JOIN A9_MATRICULATIONFOLDER FO ON
    (MAT.MATRICULATIONFOLDER_ID = FO.ID) LEFT JOIN A9_IVTM IVTM ON
    (MAT.IVTM_ID = IVTM.ID)LEFT JOIN A9_FORM576 F576 ON
    (MAT.FORM576_ID = F576.ID) LEFT JOIN A9_FORM05 F05 ON
    (MAT.FORM05_ID = F05.ID) LEFT JOIN A9_FORM06 F06 ON
    (MAT.FORM06_ID = F06.ID) WHERE VOWN.MAINOWNER = 1 AND MAT.VALID
    = 1 AND US.DELETEDON IS NULL AND PO.DELETEDON IS NULL AND
    BO.DELETEDON IS NULL AND AY.DELETEDON IS NULL AND VOWN.DELETEDON
    IS NULL AND FO.DELETEDON IS NULL AND IVTM.DELETEDON IS NULL AND
    VD.DELETEDON IS NULL AND F576.DELETEDON IS NULL AND
    F05.DELETEDON IS NULL AND F06.DELETEDON IS NULL AND
    MAT.DELETEDON IS NULL ORDER BY DOSSIERNUMBER DESC
    FINDINGS SECTION (1 finding)
    1- SQL Profile Finding (see explain plans section below)
    Se ha encontrado un plan de ejecucion potencialmente mejor para esta
    sentencia.
    Recommendation (estimated benefit: 35,82%)
    - Puede aceptar el perfil SQL recomendado.
    execute dbms_sqltune.accept_sql_profile(task_name =>
    'analisis_matriculation_view', replace => TRUE);
    EXPLAIN PLANS SECTION
    1- Original With Adjusted Cost
    Plan hash value: 1271206505
    Id      Operation      Name      Rows      Bytes      TempSpc      Cost (%CPU)      Time
    0      SELECT STATEMENT           4728K      2015M           783K (1)      02:36:41
    1      SORT ORDER BY           4728K      2015M      4346M      783K (1)      02:36:41
    * 2      HASH JOIN           4728K      2015M      1857M      333K (1)      01:06:48
    * 3      HASH JOIN           4728K      1803M      1736M      231K (1)      00:46:14
    * 4      HASH JOIN           4728K      1682M           133K (1)      00:26:42
    * 5      TABLE ACCESS FULL      A9_AGENCY      1076      34432           8 (0)      00:00:01
    * 6      FILTER                               
    * 7      HASH JOIN OUTER           5029K      1635M      1568M      133K (1)      00:26:42
    * 8      FILTER                               
    * 9      HASH JOIN OUTER           5029K      1510M      235M      45724 (2)      00:09:09
    * 10      FILTER                               
    * 11      HASH JOIN RIGHT OUTER           846K      226M      7792K      23780 (2)      00:04:46
    12      TABLE ACCESS FULL      A9_MATRICULATIONFOLDER      185K      5613K           731 (2)      00:00:09
    * 13      FILTER                               
    * 14      HASH JOIN RIGHT OUTER           846K      201M      6784K      12190 (2)      00:02:27
    15      TABLE ACCESS FULL      A9_FORM06      192K      4517K           1340 (3)      00:00:17
    * 16      FILTER                               
    * 17      HASH JOIN RIGHT OUTER           65680      14M      2784K      9769 (2)      00:01:58
    18      TABLE ACCESS FULL      A9_FORM05      91913      1705K           592 (2)      00:00:08
    * 19      HASH JOIN           65680      12M           8360 (2)      00:01:41
    * 20      HASH JOIN           560      37520           25 (8)      00:00:01
    * 21      HASH JOIN           560      14560           10 (10)      00:00:01
    * 22      HASH JOIN           8      112           7 (15)      00:00:01
    * 23      TABLE ACCESS FULL      A9_PROFESSIONALORDER      6      30           3 (0)      00:00:01
    * 24      TABLE ACCESS FULL      A9_BRANCHOFFICE      16      144           3 (0)      00:00:01
    25      TABLE ACCESS FULL      A9_AGENT      1053      12636           3 (0)      00:00:01
    * 26      TABLE ACCESS FULL      A9_USER      2245      92045           14 (0)      00:00:01
    * 27      TABLE ACCESS FULL      A9_MATRICULATION      123K      16M           8333 (2)      00:01:41
    28      TABLE ACCESS FULL      A9_FORM576      899K      30M           8158 (2)      00:01:38
    29      TABLE ACCESS FULL      A9_IVTM      1207K      29M           7562 (3)      00:01:31
    * 30      TABLE ACCESS FULL      A9_VEHICLEDATA      979K      25M           9552 (1)      00:01:55
    * 31      TABLE ACCESS FULL      A9_VEHICLEOWNER      983K      44M           7771 (2)      00:01:34
    Predicate Information (identified by operation id):
    2 - access("VOWN"."MATRICULATION_ID"="MAT"."ID")
    3 - access("MAT"."VEHICLEDATA_ID"="VD"."ID")
    4 - access("MAT"."AGENCY_ID"="AY"."ID")
    5 - filter("AY"."DELETEDON" IS NULL)
    6 - filter("IVTM"."DELETEDON" IS NULL)
    7 - access("MAT"."IVTM_ID"="IVTM"."ID"(+))
    8 - filter("F576"."DELETEDON" IS NULL)
    9 - access("MAT"."FORM576_ID"="F576"."ID"(+))
    10 - filter("FO"."DELETEDON" IS NULL)
    11 - access("MAT"."MATRICULATIONFOLDER_ID"="FO"."ID"(+))
    13 - filter("F06"."DELETEDON" IS NULL)
    14 - access("MAT"."FORM06_ID"="F06"."ID"(+))
    16 - filter("F05"."DELETEDON" IS NULL)
    17 - access("MAT"."FORM05_ID"="F05"."ID"(+))
    19 - access("MAT"."AGENT_ID"="AG"."ID")
    20 - access("AG"."ID"="US"."ID")
    21 - access("AG"."BRANCHOFFICE_ID"="BO"."ID")
    22 - access("BO"."PROFESSIONALORDER_ID"="PO"."ID")
    23 - filter("PO"."DELETEDON" IS NULL)
    24 - filter("BO"."DELETEDON" IS NULL)
    26 - filter("US"."DELETEDON" IS NULL)
    27 - filter("MAT"."VALID"=1 AND "MAT"."DELETEDON" IS NULL)
    30 - filter("VD"."DELETEDON" IS NULL)
    31 - filter("VOWN"."DELETEDON" IS NULL AND "VOWN"."MAINOWNER"=1)
    2- Using SQL Profile
    Plan hash value: 1408211821
    Best regards,
    dbajug
    Edited by: dbajug on Aug 11, 2010 6:31 AM

    Hi all,
    the aswer is on this post:
    Re: Explain plan
    Regards,
    dbajug

  • Simple Explain Plan

    Oracle 11g R2,
    Windows 7 OS.
    I would like to know, how oracle is using the view in the below explain plan and is it possible to skip using of view in below explain plan(but i don't want to go for NO_INDEX or FULL hints).I purpose fully didn't pasted the time,bytes,rows parameters.Only thing is view is used, and upon this i want clarity
    select e.employee_id,e.first_name from employees e;
    OPERATION                 OPTIONS              OBJECT_NAME           COST      
    SELECT STATEMENT                                                        3      
    VIEW                                           index$_join$_00          3      
                                                   1                               
    HASH JOIN                                                                      
    INDEX                     FAST FULL SCAN       EMP_EMP_ID_PK            1      
    INDEX                     FAST FULL SCAN       EMP_NAME_IX              1       One more thing i would like to add, this is just sample HR schema(default schema) in oracle.View "EMP_DETAILS_VIEW" is already present in this schema, which selects first_name,last_name etc.. from employee table.
    Thanks.
    Edited by: 902629 on Dec 15, 2011 10:40 AM

    Execute alter session set "_INDEX_JOIN_ENABLED"=FALSE; and execute the query.
    help reading an explain plan
    Thanks

Maybe you are looking for