Answer / guest

Cause: The operation failed because maximum active current
connections has been reached. It may not be a real error
when the Connection Pooling feature is enabled. It is
possible that the application later reissues the operation
and successfully grabs the connection pool slot and proceeds.

Action: This is an internal error. Enable tracing and
attempt to repeat the error. If it occurs again, contact
Oracle Customer Support.

Please add more information about this Error

ORA-36978: (XSRELGID01) workspace object must be a self-relation.

1 Answers  

---

DRG-12406: invalid CTX EXEC tag attribute (string)

1 Answers  

---

ORA-30186: '' must be followed by four hexdecimal characters or another ''

1 Answers  

---

ORA-01662: tablespace 'string' is non-empty and cannot be made temporary

1 Answers  

---

NZE-29152: SHA-1 self-test failure

1 Answers  

---

PCC-02367: This indicator variable must be declared as type short

1 Answers  

---

ORA-39028: cannot restart job from string state

1 Answers  

---

LSX-00024: unknown attribute group "~S"

1 Answers  

---

ORA-12448: policy string not applied to schema string

1 Answers  

---

ORA-29665: Java thread deadlock detected

1 Answers  

---

ORA-36669: (XSDPART07) string is not a legal LIST partition.

1 Answers  

---

ORA-04062: %s of string has been changed

1 Answers  

---