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-02247: no option specified for ALTER SESSION

1 Answers  

---

ORA-29514: class name contains illegal character

1 Answers  

---

ORA-19645: datafile string: incremental-start SCN is prior to creation SCN string

1 Answers  

---

ORA-01644: tablespace 'string' is already read only

1 Answers  

---

RMAN-06182: archive log larger than MAXSETSIZE: thread string seq string string

1 Answers  

---

ORA-01083: value of parameter "string" is inconsistent with that of other instances

1 Answers  

---

ORA-07708: sksaprs: tape label name buffer too small

1 Answers  

---

ORA-36930: Cannot start a recursive call to Oracle OLAP because a ROLLBACK past an UPDATE to an attached analytic workspace has been performed.

1 Answers  

---

ORA-01409: NOSORT option may not be used; rows are not in ascending order

1 Answers  

---

DRG-12005: Please give name of file to save in:

1 Answers  

---

RMAN-08519: channel string: scanning datafilecopy string

1 Answers  

---

ORA-15026: disk 'string' is not an ASM disk

1 Answers  

---