Answer / guest

Cause: The control program issued a request to an Oracle
Names server and the server did not understand the request.

Action: If the server and the control program have different
versions, they may be unable to communicate. Check your
documentation for version compatibility constraints. If the
server and control program are compatible, turn on tracing
for further details, and re-execute the failing operation.
If the error persists, contact Worldwide Customer Support.

Please add more information about this Error

ORA-07346: slnrm: normalized file name is too long

1 Answers  

---

ORA-16160: Cannot change protected standby database configuration

1 Answers  

---

ORA-12053: this is not a valid nested materialized view

1 Answers  

---

ORA-01553: MAXEXTENTS must be no smaller than the string extents currently allocated

1 Answers  

---

NZE-29246: the toolkit could not parse the tdu

1 Answers  

---

---

ORA-29524: wrong types of arguments in call to 'string'

1 Answers  

---

ORA-24080: unschedule_propagation pending for QUEUE string and DESTINATION string

1 Answers  

---

ORA-12985: tablespace 'string' is read only, cannot drop column

1 Answers  

---

DRG-10834: upper-case form of section name string too long

1 Answers  

---

ORA-25224: sender name must be specified for enqueue into secure queues

1 Answers  

---

PCC-02362: Host variable not declared within SQL DECLARE section

1 Answers  

---

ORA-24433: This statement has already been prepared using OCIStmtPrepare2.

1 Answers  

---