Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

2 Answers
2

ORU-10027 will appear if you are using a lot of dbms_output.put_line in your PL/SQL with a small buffer amount. If you are just debugging then you should set this to a large amount (dbms_output.enable(10000000) is traditional though from 10g onwards it can be unlimted: dbms_output.enable(null)) but try to remove them when going to production.

The OP doesn't seem to be using dbms_output.put_line in their problem. Maybe their snippet is incomplete?
–
FrustratedWithFormsDesignerFeb 14 '12 at 15:40

From the OP's previous question it looks like lc_history2 is a view, so maybe that calls a function that produces output?
–
Alex PooleFeb 14 '12 at 17:28

@AlexPoole: Hmmm so maybe the function is trying to write some output that may or may not be related to the query itself (like debugging statements) and that's failing on a buffer overflow, causing the query on the view to fail with a PL/SQL error... ?
–
FrustratedWithFormsDesignerFeb 14 '12 at 18:23

1

@FrustratedWithFormsDesigner - that's just my guess, but yes. Seems more likely than the posted query being pulled out of a PL/SQL block I think.
–
Alex PooleFeb 14 '12 at 18:26

If you are executing from a script, you could try adding set serveroutput on size UNLIMITED at the begining. Beware though, I don't think the UNLIMITED feature is supported in versions of Oracle older than 10 (but I'm not sure, you'll have to test this). If UNLIMITED is not supported, just set a very large size.