Answer / guest

Cause: A caller issued a name server modification request
and that request cannot be processed because it would
violate data type meta-data constraints.

Action: Not normally visible to the user, except when using
the name server control program. If the error occurs when
using the control program, examine the meta-data constraints
for the data type being operated upon and don't violate
them. Examples of typical constraint violations are attempts
to add a new data item to a name which already contains
alias information, or attempts to add alias information to a
name which already contains other data, or attempts to
replace a data item with another item that has the wrong
syntax. If the error occurs outside the control program,
turn on tracing and re-execute the failing operation. If the
error persists, contact Worldwide Customer Support.

Please add more information about this Error

ORA-26711: remote table does not contain a primary key constraint

1 Answers  

---

ORA-31651: communication error with master process - detaching job

1 Answers  

---

SQL*Loader-00957: Error shipping text string across 2-task

1 Answers  

---

ORA-29328: too many datafiles in this tablespace 'string'

1 Answers  

---

KUP-04014: invalid SLF parameter

1 Answers  

---

---

ORA-30201: Unable to load NLS data object

1 Answers  

---

TNS-01100: TNS returned error number when attempting to start the listener

1 Answers  

---

PLS-00398: wrong number of columns in UNION, INTERSECT, or MINUS expression

1 Answers  

---

ORA-02732: osnrnf: cannot find a matching database alias

1 Answers  

---

LSX-00265: attribute "~1S" value "~2S" is wrong (must be "~3S")

1 Answers  

---

SQL*Loader-00642: Relative start position > absolute field end position.

1 Answers  

---

RMAN-05008: SET NEWNAME TO NEW not allowed (datafile string)

1 Answers  

---