1. I really want to find out want when wrong in SQL Developer so I know what to avoid next time. Surely there must be some kind of log file on what happened
2. I have found that many sripts will run in SQL Plus that do not run in various other guis like EM's SQL worksheet or the other SQL Developer. I have also found that some scripts will run in some gui's but not others. So running the script in SQL Plus will not resolve the issue of what happened to lock up SQL Developer and why. (If there was a problem with the script than it should have run those parts of the script it could and thrown errors in the output window like it did on the previous run.)
I do not want to run this script with SQL Plus until it is the last alternative for getting the job done .
Main Topics
Browse All Topics





by: MikeOM_DBAPosted on 2009-11-04 at 12:37:53ID: 25743635
Login to the server and run the script using sqlplus.
-- or --
From your client run the script using sqlplus.
PS: Remember to set "SPOOL ..." command to capture errors.