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-00711: new tablespace name is invalid

1 Answers  

---

DRG-12430: mandatory argument missing: string

1 Answers  

---

ORA-14518: partition contains rows corresponding to values being dropped

1 Answers  

---

ORA-12980: checkpoint option not allowed with SET UNUSED

1 Answers  

---

ORA-22322: error table "string"."string" has incorrect structure

1 Answers  

---

KUP-01007: at line number column number

1 Answers  

---

ORA-12591: TNS:event signal failure

1 Answers  

---

ORA-16033: parameter string destination cannot be the same as parameter string destination

1 Answers  

---

ORA-12583: TNS:no reader

1 Answers  

---

DRG-50949: too many SQEs

1 Answers  

---

KUP-04019: illegal length found for VAR record in file string

1 Answers  

---

RMAN-08017: channel string: starting archive log restore to default destination

1 Answers  

---