Autonomous Transactions & error ORA-01002

Question

Either there's a bug w/ Autonomous Transactions or the documentation is incomplete because the AT is not working when
called from within Cursor Loop.
here's the outline:
CURSOR acct_cur IS ...FOR UPDATE OF a.account_nm...
FOR acct_rec IN acct_cur LOOP
fis_rte_util.print_msg (...) ---autonomous transaction writes to a logging table
---w/ commit
UPDATE ca_account_t
SET account_nm = acct_rec.account_nm....
this update statement causes a ORA-01002: fetch out of sequence exception. if
i comment out the print_msg line it works just fine. its as if the commit in the
AT is causing the problem. according to the documention, there should be no
interference between these 2 blocks.
thanks for any info or insight,
swg
null

Answer 1

Tim,
Refer to the following:
ORA-01002: fetch out of sequence
Cause: This error means that a fetch has been attempted from a cursor which is no longer valid.
Note that a PL/SQL cursor loop implicitly does fetches, and thus may also cause this error. There are a number of possible causes for this error, including:
1) Fetching from a cursor after the last row has been retrieved and the ORA-1403 error returned.
2) If the cursor has been opened with the FOR UPDATE clause, fetching after a COMMIT has been issued will return the error.
3) Rebinding any placeholders in the SQL statement, then issuing a fetch before reexecuting the statement.
Action:
1) Do not issue a fetch statement after the last row has been retrieved - there are no more rows to fetch.
2) Do not issue a COMMIT inside a fetch loop for a cursor that has been opened FOR UPDATE.
3) Reexecute the statement after rebinding, then attempt to fetch again.
HTH,
Thierry
Edited by: Thierry H. on May 4, 2011 12:30 PM Reformatting