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.

Action: For (1), initialize the LOB locator by selecting
into the locator variable or by setting the LOB locator to
empty. For (2) and (3), 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

IMG-00831: boundary queue size exceeds expected size

1 Answers  

---

NNL-00542: restart [<server_list>] : restart one or more Names servers

1 Answers  

---

DRG-50924: PL/SQL inside PL/SQL not supported

1 Answers  

---

ORA-23341: user function required

1 Answers  

---

ORA-00438: %s Option not installed

1 Answers  

---

---

LFI-00149: Error on destroying hash table in function string

1 Answers  

---

LFI-00106: Path object holds more than one path.

1 Answers  

---

ORA-02488: Error encountered when accessing file [string] for trace conversion

1 Answers  

---

SQL*Loader-00555: unrecognized processing option

1 Answers  

---

ORA-00082: memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring

1 Answers  

---

ORA-29963: missing BINDING keyword

1 Answers  

---

LPX-00125: duplicate entity "~S" (ignored)

1 Answers  

---