Recent content by usertale

  1. U

    Removing 'debug information'

    Where do I find the Preferences you are refering to? thank u.
  2. U

    Removing 'debug information'

    I have compiled my code and tested it with the debugger. Now I want to deploy - how do you remove the debug information? I still see the 'Add Debug Information' checked when I right-click on the object ... I want to remove this ... thank u
  3. U

    PL/SQL Developer 7.1.5 'Compare Soure' missing??

    I have PL/SQL Developer 7.1.5 and I can not find the tool 'Compare Soure'. Please don't tell me it has been removed? Where is it?
  4. U

    DBMS_OUTPUT cause debugger to hang.

    BEGIN DBMS_OUTPUT.ENABLE(1000000); DBMS_OUTPUT.PUT_LINE(Program started at ' || TO_CHAR(SYSDATE, 'DD-MON-YY HH:MI:SS')); run_proc(1); END; / The above code in a test script causes the debugger to hang, waiting on an (internal) PIPE call. Is this a bug??
  5. U

    Find Database Objects 'BREAK' button

    Version 7.1.4.1390
  6. U

    Find Database Objects 'BREAK' button

    Find Database Objects 'BREAK' button does not work too well....hasv to kill my PSD session to get it killed...is this a bug?? thank u
  7. U

    Debugger hanging

    Addendum: Ran some DBA queries and looks like my session is waiting on a dbms-pipe message, but the message isn
  8. U

    Debugger hanging

    I am getting a debugger issue in PL/SQL Developer
  9. U

    stopping JOBS and then restarting via PL/SQL Dev

    An example would be to do something like the followning job PL/SQL: declare v_job_status VARCHAR2(1) := 'N'; begin -- check job status select broken into v_job_status from dba_jobs where job = (select /*+ RULE */ job from dba_jobs_running where sid = userenv('SID'))...
  10. U

    stopping JOBS and then restarting via PL/SQL Dev

    Never got any feedback from the following circa 1/8/08: ========================================= You mentioned "It is always a good idea for the programmer to check inside the job itself (for instance at the beginning of a loop) whether the job is broken. If the job is broken, the program must...
  11. U

    stopping JOBS and then restarting via PL/SQL Dev

    You mentioned "It is always a good idea for the programmer to check inside the job itself (for instance at the beginning of a loop) whether the job is broken. If the job is broken, the program must be exited. In this way the code will eventually stop when the code inside the job finds out that...
  12. U

    stopping JOBS and then restarting via PL/SQL Dev

    Actually, if you check the 'Broken' checkbox and hit the 'Apply' button ,the job will stop. Reverse the process and the job will start rerunning. Thx.
  13. U

    stopping JOBS and then restarting via PL/SQL Dev

    Hello... How do I stop a Oracle Job in PL/SQL Dev? And then how do I restart the job? Can I just use the 'broken' check box? thx.
Back
Top