1

I have a PL/SQL block I'm running that looks something like this

BEGIN
   dbms_output.put_line('11');
   schema.some_package.process_data(i);
   dbms_output.put_line('22');
END;

When I run this block, the DBMS Output returns absolutely nothing. If I comment out the process_data procedure call, then it returns the 11, 22 as expected. The procedure is not raising any exceptions and appears to be processing correctly.

The process_data procedure does call many other procedures and too much code to share here, but does anyone have suggestions as to what I should be looking for that would be clearing ALL queued output, even output called after the procedure in my block?

1

1 Answer 1

2

The behaviour you describe would happen if something in your stack calls dbms_output.disable(). That suppresses all output until you call dbms_output.enable().

Re-enabling output doesn't recover the suppressed output because disable() purges the buffer as well as disabling subsequent calls to put_line(), get_line(), etc

Sign up to request clarification or add additional context in comments.

1 Comment

Thank you, this put me down the right path and I found a call to DBMS_SESSION.RESET_PACKAGE which was the culprit.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.