Answer / guest

Cause: Parsed schema components were in a simple-type
character set while the parsed instance document data was
not. A simple-type character set is single-byte, not shift
sensitive, and has no linguistic specials in use.

Action: Reinitialize the schema global context with
appropriate parser context settings, i.e. pass a parser
context with its output encoding set to be a multibyte or
Unicode character set.

Please add more information about this Error

DRG-50701: error in listener.get_cmd()

1 Answers  

---

ORA-32510: cannot create watchpoint on unreadable memory

1 Answers  

---

ORA-31634: job already exists

1 Answers  

---

EXP-00082: Invalid function name passed to procedural object support: string

1 Answers  

---

SQL*Loader-00116: Error prompting for password

1 Answers  

---

Recent I have migrated oracle9i to oracle10g(10.2.0.3). I have nested table that table used user define datatype. at a column. when i want to input the valoue at this column ,i cann't the input value.following the error messasge i have got: ORA-24328 illegal attribute value

1 Answers  

---

ORA-07849: sllfsk: $GET failure

1 Answers  

---

ORA-01568: cannot set space quota on PUBLIC

1 Answers  

---

SQL*Loader-00817: error dropping directory object string

1 Answers  

---

O2F-00307: Unable to read the INTYPE file

1 Answers  

---

ORA-16639: specified instance inactive or currently unavailable

1 Answers  

---

ORA-01030: SELECT ... INTO variable does not exist

1 Answers  

---