Parallel Transaction recovery caught exception 30319

Question

Hi,
Database - Oracle 11.1.0.7
Server - RHEL 5.2
A load process which was to load 7 milllion records was killed after 4 hours because it had several errors in the alert log -
22238:ORA-04030: out of process memory when trying to allocate 10504 bytes (pga heap,kgh stack)
After the process was killed, even after 3 hours, there were several trc files being generated with the error -
Dead transaction 0x0001.04a.00005b78 recovered by 32 server(s)
SMON: Parallel transaction recovery tried
Parallel Transaction recovery caught exception 30319
and
Parallel Transaction recovery server caught exception 10388
*** 2010-10-07 20:40:01.124
*** SESSION ID:(2993.32762) 2010-10-07 20:40:01.124
*** SERVICE NAME:(SYS$BACKGROUND) 2010-10-07 20:40:01.124
Does this means that the smon recovery failed? If so, what can I do for this? I need to kick off the load process again.
these are some other queries I ran -
select l.message,l.sql_id,l.totalwork,l.sofar,l.*
from v$session_longops l
where time_remaining is not null and time_remaining > 0
Row#     MESSAGE     SQL_ID     TOTALWORK     SOFAR     SID     TIME_REMAINING     ELAPSED_SECONDS
1     Table Scan: prdb.prpeet: 156648 out of 843440 Blocks done     3w1cxu6vbz4jn     843440     156648     2956     8707     1986
2     Index Fast Full Scan: prdb.prpeet: 15 out of 216076 Blocks done     7cacc3d07d041     216076     15     2953     3442572     239
3     Index Fast Full Scan: prdb.prpeet: 192281 out of 206419 Blocks done     d2cu3p7tmuz0z     206419     192281     2953     37     509
4     Index Fast Full Scan: prdb.prpeet: 198899 out of 216076 Blocks done     f7whmwp813kf8     216076     198899     2953     46     531
5     Index Fast Full Scan: prdb.prpeet: 5 out of 216076 Blocks done     dwf4gghk4mq0z     216076     5     2953     604999     14
6     Index Fast Full Scan: prdb.prpeet: 7 out of 216076 Blocks done     dwf4gghk4mq0z     216076     7     2953     864276     28
7     Index Fast Full Scan: prdb.prpeet: 6 out of 216076 Blocks done     7cacc3d07d041     216076     6     2953     504163     14
8     Index Fast Full Scan: prdb.prpeet: 9 out of 216076 Blocks done     7cacc3d07d041     216076     9     2953     1128350     47
9     Index Fast Full Scan: prdb.prpeet: 13 out of 216076 Blocks done     7cacc3d07d041     216076     13     2953     1961187     118
Can someone please tell me what I need to do so that I can restart the load?
Thanks.

Answer 1

I do -
OPEN cur_n1_C1 ;
LOOP
FETCH cur_n1_C1 BULK COLLECT INTO vt_C1 LIMIT 1000000;
FOR i IN vt_C1.FIRST .. vt_C1.LAST LOOP
INSERT /*+ APPEND */ INTO prpeet
VALUES
END LOOP ;
COMMIT;
END IF ;
END LOOP;
CLOSE cur_n1_C1 ;
EXCEPTION
So, will this commit be a problem? I am loading around 7 million records.
Also,
I ran the v$session_longops query again now and this is what it says -
select l.message,l.sql_id,l.totalwork,l.sofar,l.sid, l.time_remaining, elapsed_seconds
from v$session_longops l
where time_remaining is not null and time_remaining > 0
Row#     MESSAGE     SQL_ID     TOTALWORK     SOFAR     SID     TIME_REMAINING     ELAPSED_SECONDS
1     Sort Output: : 55613 out of 122712 Blocks done          122712     55613     2987     490     406
3     Table Scan: prdb.prpeet: 160239 out of 843440 Blocks done     3w1cxu6vbz4jn     843440     160239     2956     21071     4942
Does this mean it will finish in 21071 seconds?
Edited by: user12158503 on Oct 7, 2010 9:41 PM