|Oracle® OLAP DML Reference
11g Release 2 (11.2)
Part Number E17122-05
0 after a successful operation,
-1 after an error, or
100 after all requested rows have been fetched.
Handling SQL Errors
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.
Tip:After an error, the SQLERRM option typically contains an error message.
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.