1. dbms_system.ksdwrt, write to your trace_file 2. re-write your procedure as a pipelined function, so you can output in realtime 3. use dbms_pipe to send messages to another process which will listen and output (but how, it will still again be a plsql block) 4. use dbms_application_info to populate v$session-longops suitably 5. utl_file 6. run your script in debug mode, put a watch on rowcount and keep refreshing in the debug session :) ok ... i am sure there will be more options You can do it using output buffer, but unfortunately SQLPLUS does not give you a way to access *that* output buffer until your plsql block has done execution, so your choices are limited. Raj On Tue, Oct 9, 2012 at 1:59 PM, Ricard Martínez <ricard.martinez@xxxxxxxxx> wrote: > Hello > Yup thats right, but i mean a way to do it in the output buffer without using > a table or utl_file. > Also dbms_application_info doesnt seems to fit neither. > Any more suggestions? -- //www.freelists.org/webpage/oracle-l