** URGENT** How can I loop this Unnamed procedure?

Question

I have the following procedure
The total number of records is 10 million +.
I've limited the resultset to 80,000. How can I run this procedure in a loop for like 130 times.
I need to start this tonight and Have run out of time in developing a better way.
I tried a unix stript
#!/bin/ksh
let count = 3;
while count > 0;
do
sqlplus -s userid/password<<END
@sqluser6
quit
END
let count = count -1;
done
but it's not even working: error =
run_userupdate[2]: count: bad number
run_userupdate[2]: syntax error at line 5 : `<<' unmatched
My Code:
SET SERVEROUTPUT ON
DECLARE
CURSOR vt_mlr_cursor IS Select master_key, tn, user2 from vt_mlr Where user2 is not null
                                             and line_medr is null
                                             and line_aidr is null
                                             and rownum < 80001;
USERFIELD VARCHAR2(100);
R_count NUMBER := 0;
Field1 VARCHAR2(20);
Field2 VARCHAR2(20);
key VARCHAR2(10);
phone VARCHAR2(11);
BEGIN
FOR vt_mlr_record IN vt_mlr_cursor
LOOP
BEGIN
     key := vt_mlr_record.master_key;
     phone     := vt_mlr_record.tn;
     USERFIELD := vt_mlr_record.user2;
     Field1 := SUBSTR(vt_mlr_record.user2,12,4);
     Field2 := SUBSTR(vt_mlr_record.user2,28,4);
          UPDATE vt_mlr
          SET
          line_medr = Field1,
          line_aidr = Field2
          WHERE
          master_key = vt_mlr_record.master_key;
          R_count := R_count + 1;
     EXCEPTION
     when others then
     Insert into temp_reject (REJECT_KEY, REJECT_TN, REJECT_VALUE) VALUES
     (key, phone, 'USER2 ' || USERFIELD );
     R_count := R_count - 1;
END;
END LOOP;
DBMS_OUTPUT.PUT_LINE('Rows Processed: ' || R_count);
     commit;
     EXCEPTION
     when others then
     DBMS_OUTPUT.PUT_LINE('Error code ' || sqlcode || ' Error desc' || SUBSTR(sqlerrm,1,200));
END;
Thanks guys

Answer 1

Is there any reason why you can't just run this:
UPDATE vt_mlr
SET    line_medr =   SUBSTR(user2,12,4)
       , line_aidr = SUBSTR(user2,28,4)
/It's not a big update statement, and of the top of my head shouldn't generate more than 100 MB of undo (my maths is world-famous for its dodginess so YMMV).
If you've got 10 million row tables then your DBAs ought to have sized the rollback segments accordingly (even better if you're using the 9i UNDO tablespace).
Large tables are nothing to be scared off. Apart from anything else, you procedure is going to run like a three-legged dog in a vat of cold treacle.
Cheers, APC