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

PCB-00903: Pro*COBOL is unable to initialize its parser function

1 Answers  

---

QSM-01091: cost based optimizer found query rewrite is more expensive

1 Answers  

---

NZE-29095: Index is not correct.

1 Answers  

---

SQL-02152: Invalid numeric variable for use in an array GET/SET statement

1 Answers  

---

QSM-02188: named view in FROM list not supported for this type MV

1 Answers  

---

---

ORA-16729: Validating the value of property string hits error string.

1 Answers  

---

NID-00139: Mismatched dbname for datafile string, expected string, found string

1 Answers  

---

ORA-06700: TLI Driver: incorrect message type from host

1 Answers  

---

ORA-15185: Could not close dynamic library string, error [string]

1 Answers  

---

ORA-19579: archivelog record for string not found

1 Answers  

---

CLSR-00504: Error number encountered when posting an EVM event

1 Answers  

---

ORA-02184: resource quotas are not allowed in REVOKE

1 Answers  

---