Answer / guest

Cause: This error occurs when a cursor-attribute ("%FOUND",
"%NOTFOUND", "%ROWS", "%IS_OPEN", etc.) appears following an
identifier that is not declared as a cursor or cursor
variable. It occurs, for example, if the variable name
my_cur in my_cur%FOUND was not properly declared as a cursor
or if the variable declaration was placed incorrectly in the
block structure.

Action: Check the spelling and declaration of the
identifier. Also confirm that the declaration is placed
correctly in the block structure.

Please add more information about this Error

ORA-16797: SPFILE is missing in the Data Guard broker environment

1 Answers  

---

SQL*Loader-00520: lfimknam failed for file (string)

1 Answers  

---

ORA-01576: The instance string is not enabled

1 Answers  

---

EXP-00025: dictionary shows no column for constraint string.number

1 Answers  

---

DRG-13303: value of wildcard offset must be in the range string..string, at line string

1 Answers  

---

NCR-01013: NCRS: Unvalid connection type.

1 Answers  

---

LFI-00007: NLSRTL's call failed. string.

1 Answers  

---

ORA-12676: Server received internal error from client

1 Answers  

---

DRG-50803: failed to define output

1 Answers  

---

ORA-30387: invalid rewrite mode for REWRITE_EQUIVALENCE API

1 Answers  

---

ORA-38766: cannot flashback data file string; file resized smaller

1 Answers  

---

ORA-31215: DBMS_LDAP: PL/SQL - Invalid LDAP mod value.

1 Answers  

---