|
|
| Re: Buffer limit in DBMS_OUTPUT [message #365545 is a reply to message #365485] |
Thu, 15 October 1998 06:49   |
Richard T
Messages: 1
Registered: October 1998
|
Junior Member |
|
|
I dont think the dbms_output.disable/enable will do what you want -
In this lump of code, messages 1-10 will be thrown away by the disable befre they are displayed.
DECLARE
v_dir VARCHAR2(2000) := NULL;
BEGIN
FOR i in 1..30 LOOP
dbms_output.put_line('Loop '||to_char(i));
IF i = 10 THEN
dbms_output.put_line('About to disable...');
dbms_output.disable;
dbms_output.enable (1000000);
dbms_output.put_line('After disable/enable...');
END IF;
END LOOP;
END;
/
Your best bet to avoid limits might be to write to a a database pipe and have a dbpipe reader process for display or logging. This is more complicated, but offers more flexibility.
|
|
|
|
| How can I display messages in Oracle? [message #365755 is a reply to message #365485] |
Wed, 19 January 2000 08:45 |
Sandra Sofia Camacho
Messages: 1
Registered: January 2000
|
Junior Member |
|
|
I'm writting to you because I'm working in an Oracle application that needs to display messages by screen.
I understand you are working in something related, so I would really appreciate if you can tell me if the DBMS_OUTPUT procedure offers this capability, and how can I do this.
Thankyou so much for your cooperation,
Sincerely,
Sandra Sofia Camacho
Systems and Computer Engineer
Monomeros Colombo Venezolanos S.A
Barranquilla, Colombia
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
