Fix for TOAD error ORA-02404: specified plan table not found

TOAD can report error “ORA-02404: specified plan table not found” when trying to display execution plans:

TOAD Error

Two options to fix:

  1. Run script toadprep.sql. This creates the table toad_plan_table, among other things, and is meant to be run by a user with DBA privileges.
    or
  2. Change TOAD to use the same plan table (= plan_table) that other applications use. Do this in TOAD through the View -> Options -> Oracle -> General window, then change the Explain Plan Table name to “plan_table”, removing the “TOAD_” from the beginning:

TOAD fix

Plan_table itself ought to be in every database, although in versions 9i and earlier that required DBA intervention, was not created by default. See next post for details on that.

TOAD error fix from:

May 23, 2007

  • Its absolutely good!!!!!!!
    Thanks alot for giving me a described solution for this error …

  • I can confirm that the option 2 fix works for Toad 7.5 against a 10g database.

    I’ve been wondering about this for some time. I’ve been using Toad for ages on a 8.1.7 Oracle database, and since the beginning of this year I’ve been using it on a 10g database as well.

    The “Explain Plan” didn’t work in 10g and while I knew I should fix it I hadn’t had the need. This afternoon I finally needed to evaluate which of two selects was more efficient. Hence a web search that brought me to this page.

    In the process, the Explain Plan view helped me realise that I had forgotten a join between two tables which caused one of the statements to do a full table scan instead of an index scan. Yay!

  • Excelente!!! funcion贸 a la primera, muchas gracias.

    Saludos.
    Santiago, Chile.

  • Hi
    I tried the second option and it worked..
    now i can see explain plans.
    I didnt have a clue where to look for toadprep.sql…does anyone has a clue?

  • To Load and Execute TOADPREP.SQL

    1. Connect as System or a DBA.

    2. Go to File > Open File.

    3. Open your TOAD > TEMPS folder.

    4. Double-click TOADPREP.SQL.

    5. The TOADPREP.SQL loads into your SQL Editor.

    6. Execute each statement in the script by clicking on the statement and pressing .

    If this is your first time running the TOADPREP.SQL script and you execute a Drop statement, you receive an error message. This is because there is nothing to drop. You can click OK and continue. However, you can just skip all the drop statements (don’t execute the drop statements), since TOAD has nothing to drop.

    7. For the Connect statement, you need to modify the statement for your connection.

    8. When you exit, TOAD will ask you if you want to save changes. Click Yes.

    Quest Software

  • I tried to fix my problem with the second option but it thrown me the following error message.

    The following files specified on the Executables tab could not be found:

    SQL*Loader

    Ping

    I appreciate your help. Thanks in advance.

  • thanks!!!

    i stumbled upon this link when googling. tried your suggestion, and it works great!
    thank you. this really helps.

  • Thanks a lot!!!!….Option 2 has worked out with out any errors….

  • Gracias, la segunda opci贸n me funcion贸 a la perfecci贸n.

    Saludos.

  • Thanks I am a new at using TOAD but I only spent a couple of second to apply the solution without a hitch. A very straight for ward answer and good explanation to the problem.

  • It really worked. solution is stright to the point.
    thanks a lot for sharing the tips.

  • This really worked for me .Thanks alot for providing this solution.Also please guide me to analyse this explain plan so as to optimise performance of the query.

  • We have Toad Version 7.6.0.11, but cannot locate the TOADPREP.SQL file in the TOAD installed location.
    If we remove the TOAD_ prefix to the Explain Plan Table, we got the following error message:
    “The following files specified on the Executables tab could not be found:
    Ping”.
    SOLUTION
    =======
    Go to the Executables node on the same dialog box and in click the search button next to the Ping text box. My previous value of “C:\WINNT\system32\PING.EXE” got updated to “C:\WINDOWS\system32\PING.EXE” and this fixed the problem.

  • Leave a Reply

    Your email address will not be published. Required fields are marked *