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-12462: undefined compartment string for policy string

1 Answers  

---

ORA-15068: maximum number of diskgroups string already mounted

1 Answers  

---

ORA-12225: TNS:destination host unreachable

1 Answers  

---

ORA-16132: An error occurred during activation of the standby.

1 Answers  

---

DRG-11726: phrase is not a preferred term

1 Answers  

---

ORA-02456: The HASH IS column specification must be NUMBER(*,0)

1 Answers  

---

ORA-33462: (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.

1 Answers  

---

PCC-02449: Cannot type equivalence a UCS2 type

1 Answers  

---

ORA-23430: argument "string" cannot be NULL or empty string

2 Answers  

---

ORA-19572: cannot process file string, file is being being resized

1 Answers  

---

ORA-25962: join index prevents multitable insert or merge

1 Answers  

---

PCC-00093: Invalid or obsolete option, ignored

1 Answers  

---