Answer / guest

Cause: the distributed transaction table was full because
too many distributed transactions were active.

Action: Run fewer transactions. If you are sure you don't
have too many concurrent distributed transactions, this
indicates an internal error and support should be notified.
Instance shutdown/restart would be a work-around.

Please add more information about this Error

ORA-39000: bad dump file specification

1 Answers   Oracle,

---

ORA-06259: NETNTT: cannot read from remote process

1 Answers  

---

ORA-22958: This operation is not allowed in check constraints or triggers

1 Answers  

---

TNS-02509: Authentication: invalid process state

1 Answers  

---

ORA-01216: thread string is expected to be disabled after CREATE CONTROLFILE

1 Answers  

---

---

ORA-01035: ORACLE only available to users with RESTRICTED SESSION privilege

1 Answers  

---

ORA-12091: cannot online redefine table "string"."string" with materialized views

1 Answers  

---

ORA-00119: invalid specification for system parameter string

1 Answers  

---

ORA-07826: sspscm: SYS$GETDVIW failure

1 Answers  

---

NNL-00895: Requests refused, processing disabled: number

1 Answers  

---

ORA-13409: null or invalid pyramidLevel parameter

1 Answers  

---

ORA-16402: ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support

1 Answers  

---