|Oracle® OLAP DML Reference
10g Release 1 (10.1)
Part Number B10339-02
0 after a successful operation,
-1 after an error, or
100 after all requested rows have been fetched.
Oracle OLAP does not signal an error when SQLCODE becomes nonzero. Therefore, your program must test the value of SQLCODE and take the appropriate action. Since each SQL operation sets SQLCODE, you must test for errors after each operation to avoid missing an error condition.
You can write programs that look for a specific error code. For example, the most common warning code is
100, which indicates that the cursor reached the end of its table selection and the FETCH statement is complete.
After an error, the SQLERRM option typically contains an error message.
Example 22-20 Using SQLCODE When Fetching Data
The following program fragment includes a WHILE loop that tests for the value of SQLCODE and stops trying to fetch data when the end of the cursor's active set is reached.
WHILE SQLCODE EQ 0 SQL FETCH cursor1 INTO :employee, :title