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

QSM-01567: equivalence, string, cannot support the query measure, string

1 Answers  

---

RMAN-06173: no set newname command has been issued for datafile string when restore auxiliary

1 Answers  

---

RMAN-08506: input filename=string

1 Answers  

---

ORA-39705: component 'string' not found in registry

1 Answers  

---

NZE-29037: No certificate is present

1 Answers  

---

NPL-00419: received ASN.1 object identifier with sub-identifier that is too large

1 Answers  

---

ORA-07507: scgcm: unexpected lock status condition

1 Answers  

---

PLS-01906: : raw variable length too long

1 Answers  

---

ORA-12833: Coordinator's instance not a member of parallel_instance_group

1 Answers  

---

ORA-13010: an invalid number of arguments has been specified

1 Answers  

---

DRG-10583: TRUNCATE INDEX failed: string

1 Answers  

---

ORA-26001: Index string specified in SORTED INDEXES does not exist on table string

1 Answers  

---