Answer / guest

Cause: The connection between Client and Server process was
broken.

Action: There was a communication error that requires
further investigation. First, check for network problems and
review the SQL*Net setup. Also, look in the alert.log file
for any errors. Finally, test to see whether the server
process is dead and whether a trace file was generated at
failure time.

Please add more information about this Error

ORA-33449: (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.

1 Answers  

---

ORA-07204: sltln: name translation failed due to lack of output buffer space.

2 Answers  

---

ORA-30086: interval year-month result not allowed for datetime subtraction

1 Answers  

---

TNS-00121: Missing CMANAGER_NAME in INTCHG.ORA

1 Answers  

---

ORA-00972: identifier is too long

1 Answers  

---

ORA-24408: could not generate unique server group name

1 Answers  

---

DRG-10705: invalid value string for attribute string

1 Answers  

---

ORA-06261: NETNTT: nrange() failed

1 Answers  

---

PCC-00062: Must use option SQLCHECK=SEMANTICS(FULL) when there is embedded PL/SQL

1 Answers  

---

ORA-39050: parameter string is incompatible with parameter string

1 Answers  

---

ORA-29554: unhandled Java out of memory condition

1 Answers  

---

ORA-00320: cannot read file header from log string of thread string

1 Answers  

---