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

ORA-10565: Another test recovery session is active

1 Answers  

---

ORA-01088: cannot shut down ORACLE while active processes exist

1 Answers  

---

TNS-00537: Index into protocol adapter table is out of legal range

1 Answers  

---

ORA-28119: policy group does not exist

1 Answers  

---

ORA-28116: insufficient privileges to do direct path access

1 Answers  

---

ORA-29926: association already defined for the object

1 Answers  

---

ORA-12081: update operation not allowed on table "string"."string"

1 Answers  

---

PCC-02353: Semantic error at line number, column number, file string:

1 Answers  

---

ORA-30014: operation only supported in Automatic Undo Management mode

1 Answers  

---

NID-00321: Proceeding with operation

1 Answers  

---

NPL-00414: incoming ASN.1 type tag is greater than maximum of 16383

1 Answers  

---

NNO-00603: enabling all request processing

1 Answers  

---