Answer / guest

Cause: (1) For LOB write, the amount of data received is
different from the amount that was indicated would be sent.
(2) For LOB copy and loadfromfile, the end of the source
LOB/FILE value was reached before the specified input amount
was copied/loaded.

Action: (1) will happen when using OCI's piecewise mechanism
with polling or with a callback function. Modify the code
either to send the amount specified or to pass 0 as the
input amount so that any amount of data can be sent. (2)
will happen if the specified input amount is too large for
the source LOB/FILE given the starting source offset. Either
decrease the starting source offset, or decrease the amount
to copy/load.

Please add more information about this Error

AMD-00121: dimension #string: analytic workspace hierarchy not specified

1 Answers  

---

ORA-37040: (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.

1 Answers  

---

ORA-02080: database link is in use

1 Answers  

---

ORA-01203: wrong incarnation of this file - wrong creation SCN

1 Answers  

---

ORA-19017: Attributes can only be simple scalars

1 Answers  

---

---

ORA-01422: exact fetch returns more than requested number of rows

1 Answers  

---

ORA-29290: invalid offset specified for seek

1 Answers  

---

SQL*Loader-00122: Invalid skip_index_maintenance option

1 Answers  

---

ORA-01915: invalid auditing option for views

1 Answers  

---

LPX-00317: undefined decimal-format "~S"

1 Answers  

---

ORA-16191: Primary log shipping client not logged on standby

1 Answers  

---

ORA-16540: invalid argument

1 Answers  

---