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 can be translated to the
compiler character set. The compiler character set itself 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-38456: The attribute set "string" is in an inconsistent state.

1 Answers  

---

NZE-28816: No password provided for a PL/SQL function.

1 Answers  

---

ORA-06535: statement string in string is NULL or 0 length

1 Answers   RoboSoft,

---

LPX-00224: multiple occurrences of attribute "~S" found

1 Answers  

---

PCB-00236: Cannot use PIC N/G variable. NLS_NCHAR not set or set incorrectly.

1 Answers  

---

RMAN-06470: DEVICE TYPE is supported only when automatic channels are used

1 Answers  

---

ORA-27489: unable to process job "string.string" from job class "string"

1 Answers  

---

ORA-26024: SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable

0 Answers  

---

ORA-16644: apply instance not available

1 Answers  

---

ORA-39308: application/database upgrade internal error: "string"

1 Answers  

---

ORA-03245: Tablespace has to be dictionary managed, online and permanent to be able to migrate

1 Answers  

---

ORA-24043: destination string uses a reserved name, names with AQ$_ prefix are not valid

1 Answers  

---