I am having an issue with buffer limits when running procedures. If I set the output limit to unlimited in the Dbms Output tab, I can then open a worksheet and write a piece of sql to run the procedure and the output is spooled to the tab.
The problem is when I have the procedure open and choose the run option in that window (not the run script option from a worksheet) the limit (default: 20000) appears to come back as the output no longer spools to the Dbms Output tab, it now spools to a log file in the Messages tab.
Is there a way to increase the output limit on these logs so I can get debug behaviour along with an unlimited output spool? I can always run these procedures from a standalone script but it would be really nice to have the option to run it from the edit procedure window.
I haven't tried this myself so this is just a guess, but you might try playing with the following preference setting:
Tools -> Preferences -> Environment -> Log -> Maximum Log Lines and/or Save Logs to File
Hope this helps,
This works, but I have to put this in to the run window myself, I was hoping for a setting that would stick. I will mark this helpful for now as it now allows me to do what I needed to do. I will upgrade it to correct if I don't get a better solution within a few days.