Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
I am doing a lot of work in a database I don’t have access to the explain plan
tables for. Getting this access is turning out to be more of a headache than it
is worth. Is there a way to turn off Explain Plan when I debug so I don’t always
have to click through the fact that the tables are missing?
Is there a way to turn off Explain Plan when I debug
I was hoping someone else with more knowledge would answer this but it seems to
have slipped under the radar. So… I’ll try and answer with what I
know.
First… you can set Toad to make use of a specific schemas’ explain
plan. In short: if you create the explain plan in the schema you are using, you
can then point Toad at that explain plan. Problem with getting access to the
explain plan tables solved. You should be able to do that by using the
“Server Side Objects Wizard” in Toad, selecting to create the
objects in a specific schema, then entering the specific schema and database
information you use for your work.
However, your issue seems strange to me. It seems strange because I’m not
altogether sure what the explain plan functionality has to do with Oracle
debugging.
As a test on the explain plan functionality, could you try the following:
*** code start ***
Set autotrace on;
Select sysdate from dual;
*** code end ***
What happens? If you see an explain plan, create the explain table with Toad and
see if the issues you were running into disappear. If you can do a straight
– outside debug – explain plan without errors, but still get error
messages inside debug, then I’d guess you have a different issue.