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

ORA-00323: Current log of thread string not useable and all others need archiving

1 Answers  

---

IMG-00584: output format does not support the specified compressionQuality

1 Answers  

---

NID-00406: Reversion of database name failed.

1 Answers  

---

ORA-07633: smsdbp: illegal protection value

1 Answers  

---

QSM-02147: default date format is sensitive to session settings

1 Answers  

---

ORA-24057: cannot define subscriber with rule for queue string

1 Answers  

---

IMP-00042: CHARSET used, but the export file has specific character set

1 Answers  

---

DRG-51019: unable to open or illegal format for fuzzy match data file: string

1 Answers  

---

ORA-24762: server failed due to unspecified error

1 Answers  

---

TNS-01103: Protocol specific component of the address is incorrectly specified

1 Answers  

---

ORA-27487: invalid object privilege for a string

1 Answers  

---

ORA-23485: Column group "string" must consist of a single numeric column only

1 Answers  

---