+100 ROW NOT FOUND FOR FETCH, UPDATE OR DELETE, OR THE RESULT OF A QUERY IS AN EMPTY TABLE

Explanation

One of the following conditions occurred:
  • No row met the search conditions specified in an UPDATE or DELETE statement.
  • The result of a SELECT INTO statement was an empty table.
  • The result of the subselect of an INSERT statement is empty.
  • A FETCH statement was executed when the cursor was positioned after the last row of the result table.
  • No available rows qualified for return when SKIP LOCKED DATA was specified with isolation level CS or RS.
  • A FETCH statement that returns a rowset was issued, but there were not enough rows after the current cursor position to reposition the cursor on a full rowset. The cursor has been positioned on a partial rowset. If a target was specified, data was returned only for the number of rows that were actually fetched for the partial rowset. The number of rows that were returned is in field SQLERRD3 of the SQLCA.

When a SELECT statement is executed using SPUFI, this SQLCODE indicates normal completion.

This SQLCODE is also issued when LOB data cannot be returned. This situation can occur when an application is running with isolation level UR and another application has locked the LOB table space.

System action

No data was retrieved, updated, or deleted.

SQLSTATE

02000

Other SQLCODE values

The SQLCODE value is set by Db2 after each statement is executed, as shown in the following table.

SQLCODE value Meaning SQLCODE descriptions
SQLCODE = 0 Successful execution, if SQLWARN0 is blank.

If SQLWARN0 = 'W', successful execution with warning.

 000
SQLCODE = 100 No data was found. For example, a FETCH statement returned no data because the cursor was positioned after the last row of the result table. +100
SQLCODE > 0 and not = 100 Successful execution with a warning. +sqlcode-num
SQLCODE < 0 Execution was not successful. -sqlcode-num

For PDF format descriptions of the SQL codes that Db2 12 might issue, see PDF file icon Codes.