that'll show you a measure of how much rollback that is using -- don't know how to translate that directly into a "progress monitor". The v$session_longops view does.
BIG_TABLE(12,819) ospid = 4388 command = 7 program = sqlplus@aria-dev (TNS V1-V3) dedicated server=4389
Friday 14:31 Friday 14:31 last et = 5
delete from big_table
ops$tkyte@ORA817DEV> @printtbl8 'select * From v$session_longops where sid = 12 and serial# = 819 and time_remaining > -0';
SID : 12
SERIAL# : 819
OPNAME : Table Scan
TARGET : BIG_TABLE.BIG_TABLE
TARGET_DESC :
SOFAR : 110
TOTALWORK : 22822
UNITS : Blocks
START_TIME : 03-jan-2003 14:31:26
LAST_UPDATE_TIME : 03-jan-2003 14:32:01
TIME_REMAINING : 7227
ELAPSED_SECONDS : 35
CONTEXT : 0
MESSAGE : Table Scan: BIG_TABLE.BIG_TABLE: 110 out of 22822 Blocks done
USERNAME : BIG_TABLE
SQL_ADDRESS : 86879A08
SQL_HASH_VALUE : 734451454
QCSID : 0
-----------------
PL/SQL procedure successfully completed.
it works for me....