It becomes even more relevant when you consider that DBMS_OUTPUT, unlike most Oracle supplied PL/SQL packages, is sensitive to the client on which it is running. This becomes relevant when you consider that IDS includes an Oracle Client, complete with SQL*Plus. However, it seems like the Application Server guys didn’t get the memo because the original 10g versions of both the Oracle 10g Application Server and the Internet Developer Suite are actually 9.0.4.0.1. Oracle when through one of their periodic “lining up” of versions when 10g database came out. This manifests itself when you’re using an early version of Oracle’s Internet Developer Suite 10g. There are times when I have considered all of these possibilities when dealing with recalcitrant databases, but on this occasion the answer is a bit less dramatic : Oracle seem to have trouble telling the difference between 9 and 10. Was it something you said, has Oracle just forgotten how to count, or does DBMS_OUTPUT just hate you ? It can therefore be puzzling, when you still get a pesky ORU-10028 line length overflow for a line that isn’t anywhere near this limit. I’d better explain that a bit before you begin to wonder if I really should learn to use a calculator ( or even take my shoes and socks off to count past 10).įor many years, DBMS_OUTPUT.PUT_LINE had a line-length limit of 255 characters.īy the time the Oracle 10g R2 databases came along, this had been beefed up to 32767. The answer is – when it’s 255 or, to put it another way, when 9 = 10.
0 kommentar(er)
