Answer / guest

Cause: There are several causes: (1) the LOB locator was
never initialized; (2) the locator is for a BFILE and the
routine expects a BLOB/CLOB/NCLOB locator; (3) the locator
is for a BLOB/CLOB/NCLOB and the routine expects a BFILE
locator; (4) trying to update the LOB in a trigger body --
LOBs in trigger bodies are read only; (5) the locator is for
a BFILE/BLOB and the routine expects a CLOB/NCLOB locator;
(6) the locator is for a CLOB/NCLOB and the routine expects
a BFILE/BLOB locator;

Action: For (1), initialize the LOB locator by selecting
into the locator variable or by setting the LOB locator to
empty. For (2),(3), (5) and (6)pass the correct type of
locator into the routine. For (4), remove the trigger body
code that updates the LOB value.

Please add more information about this Error

PLS-01414: Use of qualified expression here

1 Answers  

---

PLS-00144: duplicate external CALLING STANDARD specification in subprogram expression

1 Answers  

---

RMAN-20033: controlfile sequence# too low

1 Answers  

---

NZE-29191: OID connection information not set

1 Answers  

---

TNS-01004: reload [<listener_name>] : reload the parameter files and SIDs

1 Answers  

---

---

ORA-15180: Could not open dynamic library string, error [string]

1 Answers  

---

ORA-12835: No instances are active in the GLOBAL_VIEW_ADMIN_GROUP

1 Answers  

---

QSM-02144: aggregate functions are present without a GROUP BY clause

1 Answers  

---

ORA-12533: TNS:illegal ADDRESS parameters

1 Answers  

---

ORA-01771: illegal option for a clustered table

1 Answers  

---

LFI-00116: Unable to close file in operation string.

1 Answers  

---

SQL*Loader-00292: ROWS parameter ignored when a LOB column is loaded

1 Answers  

---