fetch out of sequence

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.

출처: http://ora-01002.ora-code.com/

PL/SQL Automatic BULK

Bruce > >Can you tell if bulkification is performed without running the p/sql. >If PLSQL_OPTIMIZE_LEVEL is set to 2 the feature is activated. Furthermore plsql_debug must be false. K.B1D5

Oracle experts are disgusted with SQL Server User Group

On Thu 2 Dec 2004 15 50 17 -0500 Aragon Gabriel (GE Commercial Finance) <gabriel.aragon@(protected) > wrote > I 'm not very sure about the legal stuff but I agree about the moral and > ethical issu

fetch out of sequence

Guys I have a database and packages/procs I have recently inherited with little info. It runs successfully in another 9.2.0.4 database I setup on another host. Same database setup versio

[출처] ORA-01002: fetch out of sequence|작성자 형기