Permalink Submitted by dave on Tue, 07/24/2012 - 22:37.
Yes I am afraid I have, sometimes creating a "PL/SQL DBMS_OUTPUT" report works the first time, sometimes it doesn't.
The workaround I have found is to create a simple User Defined Report based on a Query, something simple like "SELECT * FROM DUAL;", that always works. Save it, close it, test it. Then open it back up and you can change the report type from "Query" to "PL/SQL DBMS_OUTPUT", delete your query text and replace it with the PL/SQL you want to use for your report.
After that the demons seem to be gone and it will behave correctly from then on.
Yes I am afraid I have,
Yes I am afraid I have, sometimes creating a "PL/SQL DBMS_OUTPUT" report works the first time, sometimes it doesn't.
The workaround I have found is to create a simple User Defined Report based on a Query, something simple like "SELECT * FROM DUAL;", that always works. Save it, close it, test it. Then open it back up and you can change the report type from "Query" to "PL/SQL DBMS_OUTPUT", delete your query text and replace it with the PL/SQL you want to use for your report.
After that the demons seem to be gone and it will behave correctly from then on.
-Dave