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

PLS-00216: NUMBER precision constraint must be in range (1 .. 38)

1 Answers  

---

ORA-19922: there is no parent row with id string and level string

1 Answers  

---

ORA-30334: illegal dimension level name

1 Answers  

---

ORA-33213: (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values.

1 Answers  

---

ORA-00307: requested INSTANCE_NUMBER out of range, maximum is string

1 Answers  

---

NZE-28842: Incorrect file permissions

1 Answers  

---

ORA-02302: invalid or missing type name

1 Answers  

---

ORA-01237: cannot extend datafile string

2 Answers  

---

NNL-00270: Current default domain is "string"

1 Answers  

---

ORA-26681: command type not supported

1 Answers  

---

NNF-01007: DCE long strings are not supported

1 Answers  

---

NCR-04007: NCRR: Invalid object handle

1 Answers  

---