Forall exception rollback

Question

Hi Guys,
I have a forall statement that I want to continue processing if it hits an exception, and rollback anything it fails on. I have limits set so I am only lifting 300 records at a time, but if only one record fails in the forall, then i want the other 299 to process and commit, and only rollback that one failure..is it possible? This is using oracle 10g.
Example snippet below, the "dots" are just were I have removed unneeded code for this example. I want to know if I can add a rollback in the EXCEPTION that will rollback the forall failure for the one saved exception, and the "commit" will commit the remaining 299 that were success?
BEGIN
LOOP
FETCH cursor1
BULK COLLECT INTO table1 LIMIT 300;
IF table1.COUNT > 0
THEN
BEGIN
FORALL i IN 1 .. table1.COUNT SAVE EXCEPTIONS
END IF;
EXIT WHENtable1.COUNT = 0;
table1.DELETE;
END LOOP;
CLOSE cursor1;
COMMIT;
EXCEPTION
WHEN OTHERS
THEN
ROLLBACK;
END;
Edited by: fixxxer on 13-Oct-2011 01:36

Answer 1

You can not do INSERT and DELETE using same FORALL statelemt. For that you have to create seperate copy of Collection.
If you want to ROLLBACK everything thnen omit the SAVE EXCEPTION statement in FORALL.
You can gothrough below FORALL restriction...
Restrictions
The following restrictions apply to the FORALL statement:
•You cannot loop through the elements of an associative array that has a string type for the key.
•Within a FORALL loop, you cannot refer to the same collection in both the SET clause and the WHERE clause of an UPDATE statement. You might need to make a second copy of the collection and refer to the new name in the WHERE clause.
•You can use the FORALL statement only in server-side programs, not in client-side programs.
•The INSERT, UPDATE, or DELETE statement must reference at least one collection. For example, a FORALL statement that inserts a set of constant values in a loop raises an exception.
•When you specify an explicit range, all collection elements in that range must exist. If an element is missing or was deleted, you get an error.
•When you use the INDICES OF or VALUES OF clauses, all the collections referenced in the DML statement must have subscripts matching the values of the index variable. Make sure that any DELETE, EXTEND, and so on operations are applied to all the collections so that they have the same set of subscripts. If any of the collections is missing a referenced element, you get an error. If you use the SAVE EXCEPTIONS clause, this error is treated like any other error and does not stop the FORALL statement.
•You cannot refer to individual record fields within DML statements called by a FORALL statement. Instead, you can specify the entire record with the SET ROW clause in an UPDATE statement, or the VALUES clause in an INSERT statement.
•Collection subscripts must be just the index variable rather than an expression, such as i rather than i+1.
•The cursor attribute %BULK_ROWCOUNT cannot be assigned to other collections, or be passed as a parameter to subprograms.