Print Thread
DBMS_OUTPUT cause debugger to hang.
#29508 03/19/08 07:37 AM
Joined: Nov 2007
Posts: 13
Dallas, TX USA
U
Member
OP Offline
Member
U
Joined: Nov 2007
Posts: 13
Dallas, TX USA
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??


Thanks very much!
Re: DBMS_OUTPUT cause debugger to hang.
#29509 03/19/08 03:25 PM
Joined: Aug 1999
Posts: 22,487
Member
Offline
Member
Joined: Aug 1999
Posts: 22,487
You could try the following:

1. Increase the shared pool size.

The Oracle Debugger seems to have some stability issues when there is not enough free memory in the shared pool.

2. Disable the call stack.

Go to Tools > Preferences > Debugger and disable the "Update call stack after each step".

3. Check for user trace files on the server.

It may be that the server process has died. Check if a trace file exist that is related to the problem, and if so, send it to me.


Marco Kalter
Allround Automations

Moderated by  support 

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.4
(Release build 20200307)
Responsive Width:

PHP: 7.1.33 Page Time: 0.098s Queries: 13 (0.025s) Memory: 2.4981 MB (Peak: 3.0399 MB) Data Comp: Off Server Time: 2024-12-04 05:30:30 UTC
Valid HTML 5 and Valid CSS