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

ORA-16061: Log file status has changed

1 Answers  

---

QSM-02137: agg(expr) requires correspondng STDDEV(expr) function

1 Answers  

---

ORA-29251: Index1 is greater than Index2 in call to dbms_sql.bind_array

1 Answers  

---

ORA-33100: (APABBR02) Value 'number' is not valid for the workspace object option.

1 Answers  

---

ORA-39117: Type needed to create table is not included in this operation. Failing sql is: string

1 Answers  

---

ORA-30446: valid workload queries not found

1 Answers  

---

ORA-14297: Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

1 Answers  

---

ORA-13756: Cannot update attribute "string".

1 Answers  

---

ORA-00354: corrupt redo log block header

1 Answers  

---

QSM-01040: match between the materialized view (string) and query join graphs failed

1 Answers  

---

ORA-28006: conflicting values for parameters string and string

1 Answers  

---

ORA-12988: cannot drop column from table owned by SYS

2 Answers   eSys,

---