SQL-02118: Invalid row for a WHERE CURRENT OF operation
- 1 Answers
- 2967 Views
- I also Faced
- E-Mail Answers
Answer / guest
Cause: An attempt was made to reference a nonexistent row
using the CURRENT OF clause in an UPDATE or DELETE
statement. This happens when no FETCH has been executed or
when FETCH returns a "no data found" error that the program
fails to trap.
Action: Check that the last cursor operation succeeded and
that the current row of the cursor is valid. The outcome of
a cursor operation can be checked in two ways: implicit
checking with the WHENEVER statement or explicit checking of
SQLCODE in the SQLCA.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
ORA-16409: Archive log switchover reference number mismatch
NMP-00003: bad SNMP variable value
ORA-14009: partition bound may not be specified for a LOCAL index partition
ORA-25297: The message options only make sense for buffered messages
ORA-29314: tablespace 'string' is not OFFLINE FOR RECOVER nor READ ONLY
RMAN-08026: channel string: copied archive log
ORA-31093: null or invalid value specified for parameter : string
TNS-04078: Unable to resume atleast one of the gateways.
ORA-14407: partitioned table contains subpartitions in a different tablespace
RMAN-08099: specifying standby controlfile for proxy backup
ORA-15012: ASM file 'string' does not exist
ORA-16028: new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
Oracle Errors 
