Answer / guest

Cause: The name of a type, attribute, or method cannot be
converted from the client character set in effect when OTT
was invoked to the compiler character set (typically ASCII
or EBCDIC).

Action: A name is translated first from the database
character set to the client character set, and then from the
client character set to the compiler character set. The
client character set is specified in a platform-dependent
manner (On UNIX platforms, the client character set is
specified by setting the NLS_LANG environment variable.) Use
a client character set that includes the character set of
the INTYPE file and can be translated to the compiler
character set. The database character set is one such
character set. Specify synonyms in the INTYPE file for any
names of database objects that cannot be successfully
translated to the client character set.

Please add more information about this Error

ORA-24341: bad mode specified

1 Answers  

---

RMAN-06904: backup of log thread number seq number lowscn string was cancelled

1 Answers  

---

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

1 Answers  

---

ORA-36258: (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.

1 Answers  

---

ORA-16519: the resource handle is invalid

1 Answers  

---

ORA-12853: insufficient memory for PX buffers: current stringK, max needed stringK

1 Answers  

---

ORA-36635: (XSDUNION03) The base dimension workspace object has an invalid datatype for use in a UNIQUE concat definition.

1 Answers  

---

ORA-03126: network driver does not support non-blocking operations

1 Answers  

---

IMP-00016: required character set conversion (type number to number) not supported

1 Answers  

---

ORA-13381: table:string not found in network:string

1 Answers  

---

ORA-37107: (XSVPART07) Attempt to write to non-existent partition of workspace object.

1 Answers  

---

ORA-29874: warning in the execution of ODCIINDEXALTER routine

1 Answers  

---