Answer / guest

Cause: An error occurred during the termination of a PL/SQL
rpc. This is usually caused by master site being unable to
close an opened cursor or if RepAPI cannot deallocate
internal memory.

Action: Fix any server side problems first, determine if the
RepAPI memory subsystem has been corrupted.

Please add more information about this Error

ORA-36614: (XSLMS02) string attempted to retrieve a nonexistent user message. (Message number number)

1 Answers  

---

O2F-00331: A syntactically illegal name was seen in the INTYPE file

1 Answers  

---

ORA-22814: attribute or element value is larger than specified in type

1 Answers  

---

QSM-02117: missing GROUPING_ID or GROUPING functions on GROUP BY column(s)

1 Answers  

---

ORA-26669: parameter string inconsistent with parameter string

1 Answers  

---

---

SQL*Loader-00417: SQL string (on column string) not allowed in direct path.

1 Answers  

---

SQL*Loader-00112: Invalid maximum bind array size

1 Answers  

---

ORA-30656: column type not supported on external organized table

1 Answers  

---

ORA-09815: File name buffer overflow

1 Answers  

---

ORA-13267: error reading data from layer table string

1 Answers  

---

ORA-28172: distinguished name not provided by proxy

1 Answers  

---

SQL-02126: Count of array elements cannot be negative (i.e. < 0)

1 Answers  

---